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 (935)	6/1/1998 12:31:00 AM
From: LTBH	Respond to of 14778

ZP Each of these has its own set of circumstances and parameters. NT; RAID; YOUR particular SCSI controller and drivers and partition magic. What one does isn't necessarily translatable to another set of circumstances, SW or HW. So when you are experimenting you need to keep each case study, its settings and observations separate. You may find a common thread but I don't think so. Each goes about its tasks differently. SCSI and RAID both doing their magic in an OS transparent manner. Partition Magic and some drivers by SW manipulation. As to C Drive, this is normally the active partition by definition. Active in terms of disk format for DOS/WIN. Additional logical partitions are all based on the first active partition. I can't address other file system schemes. Networm

To: Zeuspaul who wrote (935)	6/1/1998 10:45:00 AM
From: Spots	Respond to of 14778

I don't want you to give up; I want you to succeed and tell me how <GGG>. My point was simply that for DOS to "reletter" the drives, they have to be presented to the software in a different physical address sequence. This could be done by the bios or by a controller. In the case of your MO drive, whichever order scsi addresses are scanned (and I think I've seen it happen both ways, I guess it depends on the bios), you inserted the MO drive at an earlier address in the scan sequence so it got a lower drive letter. You could always exchange drive letters by exchanging two SCSI addresses, for example. As you note, both 95 and NT allow you to reassign drive letters (95 only allows for dismountable media but NT can do it for anything). However, this is a post-boot operation. These drive mappings are in the registry for both OSs. That is, you have to boot with the sequence DOS would assign, or in NT's case, you boot from a drive number/controller number. The BIOS and controllers (and controller bios) can clearly affect this assignment but registry entries cannot--the OS has to boot up first, at least to a point where it can find and read the registry. This, incidentally, is why my configuration is a bit unstable; my boot partition letter isn't the letter it would get from DOS, so anything that clobbers that part of the registry (SYSTEM key) can keep me from booting because NT doesn't assign its own partition the correct drive letter without the registry entries. One of these days I'm going to fix that <G>. BTW, when I say DOS letter assignment sequence I'm being a little sloppy. NT assigns letters to more partitions than DOS will (NTFS partitions specifically), but it still uses the DOS-type algorithm for the boot-level assignments, first active primary partition on first disk address is C: first on second disk is D:, etc. Well, I guess I don't know if it thinks C, D, etc internally during booting, but the effect is as if it did anyhow. As to my cloned NT, I've tried it two ways. I copied my Win NT directory G:\Winnt to G:\Winnt0 and altered the boot.ini file to point to Winnt0. No soap (blue soap). I also tried copying G:\Winnt to C:\Winnt and pointing boot.ini there. Also no luck. Perhaps I missed something, but when I INSTALL the second system rather than COPYING the second system, everything works. Same boot.ini entries.