World Australia | Europe | North America | Singapore Europe Austria | Birmingham | Budapest | France | Italy | London | TeamOS/2 (Germany) North America Berkeley | Chattanooga | Minnesota | Nova Scotia | Ontario | Pennsylvania | TeamOS/2Last update: 6th November, 1995
This doesn't occur when Warp has been shut down & rebooted with CTL-ALT-DEL but will occur even if the monitor has been powered on in advance for several minutes.
I had a great deal of difficulty with this particular part of my hardware during installation... including the APARed symptom of being unable to run seamless windows sessions. That problem was cured simply by returning the seamless windows startup parameters back to their default values. I haven't had the courage to go back and try optimizing them as recommended in the Warp online help files.
Among the solutions posted for WD90C33 problems is to use the WD90C31 drivers. I was unable to achieve any positive result with this workaround.
I have installed the FixPak 5 update but the startup problem remains.
The above solution was arrived at after much trial and error and after discovering that the Warp desktop would boot readily into 60Hz refresh mode (Bleah!) in any resolution. From the 60Hz Warp desktop, I could start a full-screen windows session whose AUTOEXEC.BAT file contained the SVGA configuration changes necessary to switch Windows into 72Hz mode. Exiting from the Windows full-screen session dropped me back into the Warp desktop while still in 72Hz mode.
I have no logical explanation for why this symptom only occurs on cold bootup. IBM technical support suggested I call Western Digital. The Western Digital tech spoke of a problem with some Paradise cards not retaining their refresh rate settings and promised to send a new BIOS. Several weeks later another Usenet correspondent called Western Digital with the same request and was told that WD's policy was never to send out replacements. Go Figure.