maiden4life wrote:What a pain.
Windows NT 3.5
Release date: September 21, 1994
Current version: 3.5 (Build 807: Service Pack 3) (June 21, 1995; 16 years ago
maiden4life wrote:Old machine works fine. Boots fine with the old HDD. I will mention the vm solution to them, but funds are dry. I used partition commander and created a partition to 2gb and set it to active. copied the partion over and still sits at the black screen. What a pain.
P5-133XL wrote:You can change the boot.ini but it is a pain because you need to do so from some other machine that will boot with that drive in it because as it is you don't have to access to any tools to edit the drive.
ludi wrote:P5-133XL wrote:You can change the boot.ini but it is a pain because you need to do so from some other machine that will boot with that drive in it because as it is you don't have to access to any tools to edit the drive.
Wait...did NT 3.5 have a bootable install CD with a "repair" option, like NT4 did? I remember using that a few times on a dual-boot 95/NT4 system after Win9x reinstalls took over the boot sector.
maiden4life wrote:I will mention the vm solution to them, but funds are dry.
P5-133XL wrote:Sorry, but you can not move a Windows NT boot drive drive from IDE to SATA and still successfully boot without manually modifying the boot.ini. Those are different HD controllers and the boot.ini specifies which controller to boot from in the syntax. Unless xxclone automatically modifies the boot.ini to match when it clones the drive (and that is very unlikely), you'll be screwed... You can not change the controller, the drive order, the partition order, or which partition is the active one when you clone your drive without modifying the boot.ini on the drive to match the change.
Forge wrote:Also, they need to drop that program YESTERDAY. Having any important component of your business being that fragile means it will get expensive very fast.
Users browsing this forum: No registered users and 6 guests