SI
SI
discoversearch

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 (3495)11/12/1998 10:23:00 PM
From: pae  Read Replies (2) | Respond to of 14778
 
ZP,

My understanding is C,E,F,G on the 7.6 and then D,H on the 3.2G.

Right you are! Looks like the rule is to put the boot-able partitions first, then the extensions in associated boot-able order. I'll have to think about the implications to shortcuts implied.

My NT exploration looks to be taking a back seat to getting this machine operational under Win98 and then overclocked. Perhaps I'll be better prepared as well. (I'm not giving up, but want to beat some value out of this expenditure before rejoining battle with NT.)

Thanks,
Paul



To: Zeuspaul who wrote (3495)11/13/1998 10:29:00 AM
From: Spots  Respond to of 14778
 
>> I don't know what NT
uses for the basis of drive mapping..boot sequence as reported by the
mobo bios or primary/slave drive position.

The NT loader is loaded by the bios, which is according to the
boot sequence negotiated between the bios and the MB. Usually
the first active primary partition on the master disk of the
primary controller (subject to the MB and bios capabilities
to alter this sequence). The point is, it's the same for
all OSs. In this respect, boot monitors such as OS2 boot
monitor should be thought of as OSs.

Once the OS (or boot monitor) boots, it can determine for
itself where the actual OS boots from. In NT's case,
the drive mapping is applied to get at the NT system
partition. The drive mapping is kept in the registry.

The net of this is, for NT you "boot" nt loader (ntldr)
without the drive mapping, but the mapping is applied early in
NT's OS-specific booting process.

It is NOT a good idea to map the partition with NT
on it to a letter different from the one the bios
would assign.

Spots