I like to play with other operating systems…good geeky fun and useful in understanding computers in general and learning how the other side lives, etc.
OK…Modern Multibooting for 100, Alec…OS Loader gives me a list of possible Microsoft-flavored operating systems to boot from. I currently have a choice of NT or Win2K. Unfortunately, the pick list says I have a choice of NT or Win2K or Win NT Setup or Microsoft Windows or NT or Win NT Setup. Anyone know how I pull the obsolete and redundant items from the list?
Ummm…Ancient History for 200, please…I have Windows for Workgroups (3.11) and hey, guess what? It didn’t ship with TCP/IP as a networking protocol! (oops). OK, where the heck do I download a TCP stack for Windows 3.11?
c:\boot.ini (which will generally be a hidden system file) has all of your boot options. You’ll have to change the file permissions before you can edit it.
engineer_comp_geek, I have no such file at that location, invisible or otherwise.
xash, I downloaded Trumpet but it appears to be a PPP dialer. Does it also install a TCP stack? (I don’t need PPP, my TCP connection will be DHCP Ethernet).
Incidentally, the Trumpet installer just keeps reintroducing me to that brave Microsoft military hero, General Protection Fault
Hi, and thanks again to all the folks who have been helping me.
Note the tense.
I already had the drivers for the NIC but Win311 doesn’t want to install them except in conjunction with a protocol, so these need to be installed concurrently with TCP/IP. I now have the TCP/IP drivers for 3.11 from Microsoft’s site. The TCP drivers came as a self-extracting (exe) archive, so I first named a new directory and tossed the exe file in there and then ran it, extracting the component files to the same directory. Later, when the intall attempt yielded the error messages I’m about to describe, I copied all those files to a floppy instead of pointing the Network control panel dialog to the directory I’d created on the C drive. Same results either way
During the course of the dual install (NIC + TCP), the following error message appeared first:
This message was repeated for the following files as well, in this sequence:
Every one of the above-mentioned files were among those extracted from the self-extracting EXE archive, and were first located to a directory I’d created on the C drive and then were placed on the floppy (A drive). In both cases the OEMSETUP.INF file was in the folder along with these files.
At the conclusion of the install attempt, the following error message appeared:
OK, I’m going back under the hood to see if I can figure out how to install the NIC separately from the installation of the protocol, and then bring up this elusive Driver Type setting. But any advice would be appreciated in the mean time.
OK, ignore the first error message. I have fixed that problem. No more complaints about missing files.
I’m still unable to figure out how to modify or differently install the DEC NIC driver as a real mode rather than protected mode device. There is no button or dialog named “Driver Type”, and no obvious other place from which to make this distinction.
