In a message dated 95-09-02 23:42:10 EDT, [log in to unmask] (Jeff Kell) writes: >Important point here -- during Win95 install you have an option to "backup >the >current configuration" (may be a default if you don't custom install). Also, >it will build a "bail-out disk" with a bootable Win95 kernel, scandisk, and >other utilities PLUS the UNINSTAL utility (or is in W95UNDO?). Anyway, my >point was... > >* The "backup" doesn't go on the floppy, it goes on your hard drive. The > bulk of it goes in a file in your root directory (W95UNDO.DAT?) that in > my case was nearly 10Mb. >* The "uninstall" thing worked here, on two occasions, when we hosed a LAN > card installation (and were installing from a Netware CD-ROM, and suddenly > couldn't get to it anymore!). > >Yes, it takes more disk, especially if you do a full installation. But a >good 8-10Mb of that is your backup file (a significant chunk). > >[\] Jeff Kell <[log in to unmask]> > > My point about disc space was more akin to Win95 eating disc space up after the installation. I am well aware that it would require much more space than WFWG but it just seem to eat more over the next few days after the install. Since I installed Win95 for dual-boot capability according to an article in PC Magazine, I was prepared to surrender a lot of disc space. But now: 1- Number of times, dual booting capability was used : 1 2- Number of applications not working on Win95 (so far) : 0 3- Amount of disc space to be returned after removal of old Win3.1 : 60 megs+ 4- Days before removing Win 3.1 : 1 I think that says it all. BTW, C/S to HP3000 seems to work very well. More tests on-going. (Next VB 4.0 and ODBC?, and MSOFFICE for Windows 95?) Kind regards, Denys. . .