| Frequently Asked Questions |
|
|
| Frequently Asked Questions |
|
FAQs related to all systems...
|
I have problems transfering data between the HP and the HPShell.
Check if the port where you have connected the wire between the HP and the PC is the same as switched inside the HPShell. Usuallay you have your mouse on COM1 port so that you HP wire uses COM2. This is the reason why COM2 is the default setting. If still nothing happens check the settings on your HP48. Use the TOOLS | HP-Setup Dialog to check the settings. Check if the wire is ok. If you use a soundcard in your system it is possible that there are problems with the used IRQ. You should reconfigure your soundcard.
The mouse stops working, mostly after a transmission.
| There are two possiblities:
If the text inside an editor window is longer than the window, the
text can't be scrolled.
| This will only happen if the automatic word wrapping is switched on. Use the OPTIONS | Editor dialog to switch this feature off. This is a known bug of this HPShell version.
HP-directory-variables do not work propperly.
| It´s not nice to say but this is most likely your fault. At least one of the included files have a wrong syntax. Check all you files very closly.
While transfering data the program crashes.
| Well, this can happen while the program swaps itself out of the memory. By default the HPShell uses the EMS memory. If this is not possible it uses the XMS memory and if this also fails the HPShell swaps itself in a file on your harddisk.
In some cases the default setting can cause a crash. You can force
the HPShell to use one specific kind of memory in the HPSHELL.INI file:
If you use SWAPTO=ALL you can change the order the HPShell tries to use the memory. [Memory] SWAPTO=ALL USEFIRST=yyywhere yyy is a placeholder for EMS or XMS.
If I switch to the MONOCHROME mode the program crashes.
| This will happen if you have loaded some drivers in the higher memory area of the monochrome display. To fix the problem make sure not loading any drivers in the memory area from B000 to B100.
The system crashes while loading binary files into an editor window.
| Well this is not nice, but a binary file is nothing you have to edit with a text editor !
I have trouble setting up an external protocol.
| There is a known bug at this point. When adding an external protocol in the OPTIONS | TRANSFER | Protocol dialog the HPShell tries to find the protocol. Unfortunately it don´t looks into the HPShell directory. To fix this problem, copy your external protocol in an extra directory and add this directoy to the PATH statement of your AUTOEXEC.BAT.
The fast-menu feature is realy nice, but with an opened dialog it is not
useful to open a menu by pressing the ALT key.
| You are definately right ! This is a known bug in the current verison. |
FAQs related to Windows...
The Author will definately not write any Windows version but
is willing to share the sources of the program with anybody who
wants to port the program to Windows. The HPShell is entirely written
in Borland Pascal 7.0 / Turbo Vision.
There are a number of possible reasons. One thing you can try is to
start the HPShell with the paramter /V.
If this doesn't work try the following: Reduce the EMS and XMS memory for
the HPShell-DOS-Box to zero. You'll find these settings in the properties dialog
for the HPShell-DOS-Box. This will slow down the HPShell a little bit but in order to
make the HPShell work this should be ok, right ?
Will there be any Windows Version (31/95/NT) of the HPShell available ?
I can´t start the HPShell under Windows 95.
HPSHELL /V
This will skip the Virus Self Check. By starting the HPShell with the paramter
/? you will get a list of all possible start parameters.