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: Zeuspaul who wrote (4174)	12/12/1998 1:22:00 PM
From: Clarence Dodge	Read Replies (3) \| Respond to of 14778

Hey ZP This option is resident inside NT I was confused as to whether or not NT DOS required a separate DOS installation. I thought Spots was indicating it did. But I was misunderstanding him. If your intent is to fix NT using DOS you will need a separate REAL DOS installation. The pseudo NT DOS will not make it. Yes.. this would hypothetically be my primary usage....together with BIOS updates which I take it is not possible in NT DOS. So I will need a separate DOS installation, eventually. I say eventually because Jon Mitchiner is ( or has already) installing Win NT. I am not certain, but I believe my opportunity to install real DOS before NT has passed. I will have to learn more about the other methods SPots and yourself mentioned ie DOS resident on a floppy or the separate OS boot option via a boot manager. Unless I am convinced otherwise the DOS on floppy seems appropriate. Do you or anyone else know where I could look for explicit instructions for building a bootable DOS floppy? Clarence

To: Zeuspaul who wrote (4174)	12/13/1998 2:31:00 PM
From: Spots	Respond to of 14778

>>I don't have a handle on NTFS DOS yet except it is a way around the harddrive formatting issue. As an idea, NTFSDos is simple (as opposed to its implementation, which, according to the authors at least, is highly sophisticated <g>). It's just a DOS device driver. As such it makes it's "devices" (NTFS partitions) visible in the dos environment, just as MSCDEX makes CD devices visible. Incidentally, if you run Win 3.1 (or 3.11) on top of DOS running NTFSDos, the NTFS devices are visible there, too. I find File Manager easier to work with than Dos, myself. The NTFSDOS package also includes a virtual device driver for Win 95 which you can install from a Win 95 autoexec.bat during win 95 boot up. I have a conditional in my win 95 autoexec.bat that let's me choose whether I want NTFSDos or not. BTW, I should have included NTFSDos on my list of Must Have items on a bootable DOS floppy. Spots