wavesys.html

The Wave System Requirements
The Wave requires GEOS/Wheels and a SuperCPU with SuperRAM, 1 meg can still be used, but just barely. Telnet will work OK, but the browser will only be able to handle small pages. I'd recommend not using anything but 4 megs or more.

16 megs will work the best when the software is fully developed since a lot of caching will be able to happen in memory instead of caching to disk. The extra memory will speed up the "back" button better.

There are two versions, Wave64 and Wave128. They are pretty much identical except for screen resolution. The 128 version runs on the 80 column screen in graphic mode while the 64 version uses the graphic mode of the VICII. They require Wheels 64/Wheels 128 as the OS.

Occasionally I seem to get extra keypresses when using the telnet terminal in The Wave. In other words "tthis" might happen. I'm tending to blame it partly on maybe holding a key down too long, but it appears as though it's a slight timing problem and maybe a conflict of interrupts while data is going in and out of the modem while at the same time the keyboard is being read by the OS.

I've managed to correct the problem by loading up the DetailShop and adjusting the "key repeat" values a little. If you're having the same problem, try doing the same. Here's the settings I made that work pretty good while still giving me a good keyboard feel while running other applications:

I've heard that some ISP's modems won't allow a connect if some of the compression methods are configured in the modem the user is using.

Try AT&F to reset the factory defaults and then AT&W0 to save them. See if that works. If not, then the factory defaults have a problem and I'll have to see if I can look up what settings might be affecting it.

Also, AT&S0 is important in ALL modems connected to our systems. The SwiftLinks and T232s won't receive properly with any other setting, unless another setting also causes the modem to act the same. This affects the DSR line.

DSR must ALWAYS be active. Also, in The Wave, the carrier detect line is monitored. The CD line must act in a normal way. The correct setting for this is AT&C1. By normal, I mean it can't always be on or always be off. It must reflect the state of the carrier. It can be opposite, that's OK. But it must CHANGE when the actual carrier changes.

If you see that the current setting is &C0, then that could be the problem.

        Wave64 (the main application)
        System64        (Wave system routines)
        FontList64      (font configuration file)
        Default64       (default font)
        DefaultISO64    (upper default font)
        Headline64      (headline font)
        HeadlineISO64   (upper headline font)
        Courier64       (monospaced font)
        CourierISO64    (upper monospaced font)
        T64.NarrowTall (terminal font)
        T64.WideTall    (terminal font)
        T64.NarrowShort (terminal font)
        T64.WideShort   (terminal font)
        START64.HTML    (your personal start file)
        wr.quickstart   (quick start docs in geowrite format)
        quickstart.html (quick start docs viewable in the browser)

Plus, don't forget that The Wave for the 64 comes with new mouse drivers and a New Toolbox. It will crash if you don't use one of the new mouse drivers.

        Wave128 (the main application)
        System128       (Wave system routines)
        FontList128     (font configuration file)
        Default128      (default font)
        DefaultISO128   (upper default font)
        Headline128     (headline font)
        HeadlineISO128 (upper headline font)
        Courier128      (monospaced font)
        CourierISO128   (upper monospaced font)
        Term128.tall    (terminal font)
        Term128.short   (terminal font)
        START128.HTML   (your personal start file)
        wr.quickstart   (quick start docs in geoWrite format)
        quickstart.html (quick start docs viewable in the browser)