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 (7471)	5/14/1999 11:01:00 PM
From: Clarence Dodge	Read Replies (1) \| Respond to of 14778

Spots my only remaining idea is that partition 2 is too high on the drive. Partition (1) is 2 gig and Partition (2) is an exact copy so its 2 gig also. Do you not have an NT setup (which was supposed to be the backup, right?) bootable from IDE2? One that you know will actually boot, I mean. Try putting that one in the boot.ini file on IDE1. At least if there's a problem you know it isn't from the bios. With an rdisk(1) nto booted fine from IDE 1. So no Bios problem, at least. This is the boot.ini I'm attempting to use for the backup NT dual boot. Just wanted you to see it in case there's a mistake I'm not seeing. [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Workstation Version 4.00" multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation Version 4.00" Its looking like I can only boot to first partitions on a disk. Fussy Fussy eh... The fact that Partition 2 is not active has been ruled out as a consideration, right? Let me ask you this, Spots. You said that you had your backup OS on the same disk as your primary and could chose it instead of your primary during bootup. So how does your disk configuration differ from mine to allow that to be possible? Are you using separate partitions for your primary and backup? If all else fails and I am actually limited to first partitions, my only option would be to replace the boot partition on the scsi with this backup of C:. But thats a different drive. Clarence

To: Spots who wrote (7471)	5/16/1999 3:08:00 PM
From: Clarence Dodge	Read Replies (1) \| Respond to of 14778

Spots I failed trying to boot both new Celeron machines from partitions larger than 4 GB This may help. Its from the PQ site. (Begin quoted material) SO HOW CAN WE GET ABOVE 4GB ON AN NT BOOT PARTITION? Method 1: Before beginning the NT setup process, pre-format the target disk space as an NTFS partition no larger than 7.8GB (see instructions below). Then when prompted during the NT install, choose: Leave the current file system intact (no changes) The NT setup process will not have any problem installing into the pre-formatted partition. There is a catch, however. It takes some work to get the NTFS partition pre-formatted in the first place. The difficulty arises because we need NT to be running in order to format an NTFS partition on which to install NT (chicken and egg). This can be overcome in one of the following ways: Place the target hard drive in another NT workstation as a slave drive. Boot the master NT and format the slave as NTFS (not to exceed 7.8GB). Return the slave drive to its home workstation as master. Then proceed with a normal NT install and choose ‘Leave the current file system intact.' Install a skeletal NT to your drive. Boot into the skeletal NT install long enough to format the remainder of the drive as NTFS. Install NT to the newly formatted NTFS drive. Delete the minimal install and use PartitionMagic to expand the NTFS drive as large as 7.8GB. For both of the above cases, the user will have to copy the following files to the new partition in order for it to be bootable: ntldr, ntdetect.com, boot.ini, and for SCSI systems also include ntbootdd.sys. Method 2: Use Drive Image to create an image of a fully configured, bootable NTFS partition of any size less than 7.8GB. Then use Drive Image to restore the image to as many hard drives as desired. Drive Image can resize the partition as it copies it to the target. It will not resize it above 7.8GB. A resize on image restore of a bootable NT partition will also invalidate the NTFS journal file. However, since the partition is bootable, NT will repair the journal file on the next reboot.