Depending on how you copied your HyperLink disk, or how you built it, the boot sector the 128 uses to autostart disks may have been destroyed. To rebuild the 128 boot sector, enter 128 mode, insert the HyperLink disk and type RUN"BOOT128 INSTALL",UD where D is your disk drive (example: RUN"BOOT128 INSTALL",U9). This will overwrite any data you have in track 1 sector 0 -- make sure you have no files in this area.
If you cannot install the boot sector, you can still start HyperLink manually in 128 mode by typing RUN"BOOT128",UD where D is your disk drive (example: RUN"BOOT128",U9).
Please note the current 128 bootloader cannot boot from a CMD RAMLink. You must switch to 64 mode to boot from a RAMLink.
Have you registered your copy yet?
The inline images referenced on the disk aren't present. Make sure the right disk is in the disk drive. (Alternatively, make sure that inline images aren't disabled -- press CTRL-I to toggle inline images on and off.)
If you have turned off active content with CTRL-K, certain system access functions are disabled which the script might depend on (if so, you'll see <Active> displayed). Press CTRL-K until the border flashes green, and then press CTRL-R to reload the document and try again. Alternatively, this could be a bug in the script.
Have you registered your copy yet?
You selected 'Offline' in the Configure program, so HyperLink thinks you aren't using a modem. Re-run Configure and properly set up your system.
Make sure HyperLink knows where to find your modem or null-modem connection: use SwiftLink or compatible if you are connecting with a Turbo232, SwiftLink or other ACIA cartridge, and verify that port speed and I/O address are correct (re-run Configure if necessary). Check all the connections to your modem or null-modem. Next, verify that your interface is connected properly (you might have to turn your computer off to reseat a jiggly ACIA cartridge). Then, if your modem has lights on it, watch the RD/SD lights as you type. If you see nothing, your modem or hardware may be faulty. If you see lights blink, but nothing displays, your modem might not be set to echo back to HyperLink. Consult your hardware manual.
Your modem might require the command to be in upper or lower case only. Also, your modem might be in data mode. Consult your modem's manual.
HyperLink has built-in software flow control during image/page and file transfers, but depends on hardware flow control in terminal mode. If your modem or null-modem connection supports RTS/CTS flow control, make sure it is turned on. Consult your hardware device's manual.
Make sure you wait at least thirty seconds, as HLPP may simply be waiting for the server to send a response (and the server might be down). Break the connection with CTRL-COMMODORE and try reloading with CTRL-R. However, if nothing still happens after waiting at least 30 seconds, something may have happened to kill HLPP on the server side, or you were disconnected from your server. Press CTRL-COMMODORE, press F4 to enter terminal mode, and try to restart HLPP.
It has been reported that under rare circumstances, some servers may "hiccup" and ignore HyperLink's built-in flow control, spewing packets faster than HL can keep up and causing HL and the server to go out of synchronisation. This is often due to a defective terminal server. Press CTRL-COMMODORE to terminate the connection, and try to reload the image or page.
Repeated corrupt data packets are occurring. There is probably significant line noise present. Try enabling hardware error correction if your modem supports it, or disconnecting and reconnecting to your ISP to get a better connection. This problem is most common with slower or older modems and interfaces.
If you are running at a slow connect speed, this is unfortunately unavoidable. If, however, you are connected at high speed and transfers run slowly, you might be connecting through too many hosts and the network delay is slowing transmission. If you Telnet to another shell account, try using one more local to you instead if one is available, most preferably the one you immediately dial-in to.
One other cause for this problem is users with a SwiftLink choosing 57.6kbps as their port speed. This is only supported on the Turbo232, and HyperLink's ACIA library will default to 2400bps instead. Re-run Configure to correct this.
Something happened to cause the transmission to terminate early. Press CTRL-R to try to reload the page.
More recent versions of HLPP try by default to intelligently pick which images seem to be salient based on their ALT text, and if they do anything if you click on them. Other images are simply silently discarded. If you still want all images regardless, go to <HLPP settings> and change your image settings.
Your shell account does not support the program needed to display this picture. Click on <File options> to see if this is the case. You might wish to download the picture and look at it offline instead.
The picture either does not exist or there is some problem converting it. Click on <File options> to see if this is the case. If the picture does indeed exist, you might wish to download it and look at it offline to see if the image is corrupt.