Hey all:
We've been using Ghost for years with no problems. Because so many of our users require unique software builds, we Ghost each machine after we've gotten it all squeaky clean and running perfectly. Then we give it to the user and wait for them to destroy it. When they do, we load the image back on it (after saving what we can of their work files) and redeploy. One hour job instead of a whole day.
This scenario worked well on every make/model machine we used, until we migrated from W98 to W2K. Now we have a problem but only on the Gateway Solo 5300 laptops. After building a 5300 with W2KPro from scratch and formatting NTFS everything works great. We get an image without a problem. But when we try to put that image back on a hard drive and put that hard drive back in the same machine, it won't boot. I can boot to floppy or CD without a problem. I can see the data on the drive by mounting it in another machine with W2K and viewing it there. But booting to the hard drive will go through POST to where it should start loading W2K and the cursor will just flash in the upper left hand corner.
Get this: I can put that same exact hard drive in a Gateway Solo 5350 and it *will* boot! But it won't boot in any 5300. I can take an old Ghost image for a 5300 that was built with W98, restore that to the hard drive in question and it will boot just fine.
I've upgraded the BIOS to the latest version available on Gateway's site. I gotta think it's something with NTFS and how it's handled by those models, but can't find any help from Symantec, Microsoft, Gateway or the rest of the 'net. Other W2K/NTFS images work perfectly on other models. And if I build a 5300 from scratch, format NTFS, it works fine. Just not after a Ghost.
Oh, yeah...we're running Ghost 7.5 Corporate Edition. I don't want to focus too much on the fact that it is a Solo 5300--its just that that's the only one we have that fails. Has anyone seen this on any other make/model? Actually, we used Solo 2550's prior to that and they may exhibit the same thing...I don't know. I haven't tested them enough to know for sure. Anything we have prior to that we haven't tried putting W2K on so wouldn't know for sure. But any subsequent model (5350, 450, etc) works fine.
Sorry this is so long...just wanted to get all the info out there. Probably still missed something. It's just so wierd and haven't seen anyone else with the same kind of problems.
Ohh...speaking of forgetting to include all the info...we ran GDISK /MBR and restoring the image with the -fdsp switch.
Thanks in advance for any help/suggestions.
We've been using Ghost for years with no problems. Because so many of our users require unique software builds, we Ghost each machine after we've gotten it all squeaky clean and running perfectly. Then we give it to the user and wait for them to destroy it. When they do, we load the image back on it (after saving what we can of their work files) and redeploy. One hour job instead of a whole day.
This scenario worked well on every make/model machine we used, until we migrated from W98 to W2K. Now we have a problem but only on the Gateway Solo 5300 laptops. After building a 5300 with W2KPro from scratch and formatting NTFS everything works great. We get an image without a problem. But when we try to put that image back on a hard drive and put that hard drive back in the same machine, it won't boot. I can boot to floppy or CD without a problem. I can see the data on the drive by mounting it in another machine with W2K and viewing it there. But booting to the hard drive will go through POST to where it should start loading W2K and the cursor will just flash in the upper left hand corner.
Get this: I can put that same exact hard drive in a Gateway Solo 5350 and it *will* boot! But it won't boot in any 5300. I can take an old Ghost image for a 5300 that was built with W98, restore that to the hard drive in question and it will boot just fine.
I've upgraded the BIOS to the latest version available on Gateway's site. I gotta think it's something with NTFS and how it's handled by those models, but can't find any help from Symantec, Microsoft, Gateway or the rest of the 'net. Other W2K/NTFS images work perfectly on other models. And if I build a 5300 from scratch, format NTFS, it works fine. Just not after a Ghost.
Oh, yeah...we're running Ghost 7.5 Corporate Edition. I don't want to focus too much on the fact that it is a Solo 5300--its just that that's the only one we have that fails. Has anyone seen this on any other make/model? Actually, we used Solo 2550's prior to that and they may exhibit the same thing...I don't know. I haven't tested them enough to know for sure. Anything we have prior to that we haven't tried putting W2K on so wouldn't know for sure. But any subsequent model (5350, 450, etc) works fine.
Sorry this is so long...just wanted to get all the info out there. Probably still missed something. It's just so wierd and haven't seen anyone else with the same kind of problems.
Ohh...speaking of forgetting to include all the info...we ran GDISK /MBR and restoring the image with the -fdsp switch.
Thanks in advance for any help/suggestions.
