Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Spots who wrote (4179)	12/13/1998 2:38:00 PM
From: Nazbuster	Read Replies (1) \| Respond to of 14778

When you build a DOS bootable floppy, don't forget to create a CONFIG.SYS and AUTOEXEC.BAT which includes the DOS drivers for your CDROM drive: for CONFIG.SYS: device = a:\pathway\driver.sys /d:name (for your brand of CD --- NOTE A:\ ) for AUTOEXEC.BAT: a:\dos\mscdex.exe /d:name The "name" can be anything, but I've run into trouble calling it CDROM and MITSUMI. It seems that NT knows the device names returned from the devices by the PNP process and have set aside the names in memory somewhere. Using the same name as your device name causes the system to fail. It's best to have a 2nd physical drive on your system, even a smaller one, where you install MS-DOS and perhaps W95/W98 so you can boot to a real environment if your NT system gets trashed or the disk itself is damaged. Barring that, at least build 2 partitions so one can contain a bootable MS-DOS or W95/W98 environment. There are utilities which allow you to inspect and even change an NTFS disk from MS-DOS. Having enough of a system to get onto the internet to download drivers, ask for help, or seek counseling <GGG> can be pretty useful during a crisis.