#WIN32S anyone?
4 messages in this thread
I have just installed the one that came with the Abekas driver, and it works
fine (win3.1+Dos5.0), but only after creating a permanent swap file (I have 32
Mb ram)
Regards,
Vanny.
Please, what did it say before you made a permanent swap file? Did it say
something about DOS ERROR 21? Until we can get to the bottom of this, we're
holding off full scale effort behind the Abekas driver (which is completely
done at this point and waiting to be sold).
I said no error message. Only that it needed virtual memory to work, adn
aborted the installation. I made the permanent swap file and installed
successfully.
Regards,
Vanny
After much effort, we have tracked down this problem and in short, Microsoft
should be ashamed of themselves. The root of the problem turned out to be a
corrupted win32s master disk. (1) Any "professional" system would have a means
of detecting and flagging a bad file copy. (2) Any "professional" installation
system would not allow bogus information to be passed on. That no checksum
information is kept or checked by Microsoft's installation system is simply
lame.
To sum up, thanks for everyone's help – you were much more help than Microsoft
which didn't respond at all. And, problem fixed – expect our Abekas driver to
begin shipments next week. Again, thank you all.