#WIN95 & Ani Pro
4 messages in this thread
You should be able to load the mouse driver at bootup by creating and using
a CONFIG.SYS file. If the mouse driver has a .SYS version, you can specify it
directly there with DEVICE= or DEVICEHIGH=. If not, you will need to load the
.COM or .EXE with INSTALL= or INSTALLHIGH=, assuming the driver allows that.
Contrary to what Microsoft would have you believe, Windows95 is still based
on MS-DOS. They just try to hide it. CONFIG.SYS still exists.
As for running it directly from Win95, have you included PHARLAP.386 in the
SYSTEM.INI file? Are such modules supported in Win95? Or does the Win95 DPMI
implement the full DPMI 1.0 that Phar Lap wants (and OS/2 has supplied since
OS/2 2.0!), or only the DPMI 0.9 that Windows 3.1 and Windows NT have (which is
why 3DS won't work at all under WinNT or without PHARLAP.386 on Win3.1 or WfWg
3.11)? PHARLAP.386 supplies the "_REALBREAK" DPMI 1.0 call which is missing in
DPMI 0.9 but that Phar Lap 386|DOS-Extender requires.
Thanks for the info on Win95 and our products.
All I have to do is wait until WIN95 shows up on our desk!
Hi Nik,
->"All I have to do is wait until WIN95 shows up on our desk!"
Savor these days until it does eventually land. Win95 is a crock, and a brewing
tech support nightmare for all users and vendors involved. Between my own
personal observations of many installations, reading online posts, and browsing
numerous books on Win95, there's little or no benefit in going to Win95 unless
you're dying to run your 16-bit apps slower or not at all. 🙂
I really feel sorry for the people who have to support Windows apps under
Win95, as well as developers who are migrating their apps. Microsoft owes you a
huge debt.
-Heinz.
Thanks for the heads up. (" Microsoft owes you a huge debt.") We occasionally
get support calls from Microsoft staff using 3DS – I'll be sure to barter for
support!