We run a mixed XP and Windows 2000 desktop\laptop builds at the mo and the images are ghosted and then software injected via GP but one of my Dell Images for laptops has started randonly coming up with Boot Loader 3 errors any ideas

 

Image corrupt?

 

its not something win2k specific, its to do with your imaging software.

i'd say corrupt image too seen it happen LOADS

 

ok mini update

I think its a post sp4 sus update its getting killing that build just gotta fix a busted one and prove it now

 

Looking round the net some people have said it could be an issue if you are running pcmcia cards.

 

so the image goes on ok, THEN it goes tits up?

 

ps use WSUS not SUS... trust me, its the difference between a 1.1 fiesta pop plus and a Focus WRC car!

 

yep r images r FAT32 and then via sysprep convert to NTFS but on this build they convert early possible thats the problem

 

FAT32 belongs in history books and nowhere else

 

i know my next project is a brand new XP SP2 desktop but we merged and one company had XP1 (pants real bad build) and the other Windows 2000 SP4 (Image was kept FAT and then converted as easier to update with ghost explorer)

 

Ghost is a double edged sword... or it's like women: can't live with, can't live without.


I'm all out of analogies now

 

fat32is the way we build ours then convert to NTFS here

 

buy a version of ghost made after 1803 and it wont need fat32 images oh and you can get away with using ghostwalker instead of sysprep, it makes building the images in the 1st place much esier

 

ours are ntfs natively.. we use ghost as well

although the RBS build is all scripted using proper MS way of doing it.. so is Natwest..