Comments for slim jims

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 15:00:15 +0000

Ok ive tried adding the drivers to the appropriate folder in the $OEM$ folder but no luck.

Comment on Single XP Image for WDS by slim jim

slim jim — Thu, 12 May 2011 13:12:27 +0000

I would have thought it possible to add MSD drivers as you have stated, without having to rebuild the image. If this doesn’t work however, maybe try building the image on the A200 to start with so it has all the right drivers for that.

Keep in touch as interested to know how you get on.

Cheers,

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 13:08:37 +0000

No, its a very basic BIOS.
I think it may need specific Mass Storage Drivers added. is there anyway to add these to the image without haveing to re-capture it?
Can i put them into the $OEM$ folder and point the sysprep file to the location?
Or is it failing too early in the boot sequence to do that?

Thanks for all your help by the way

Comment on Single XP Image for WDS by slim jim

slim jim — Thu, 12 May 2011 13:00:09 +0000

Is it possible that the A200′s have some kind of RAID thingy-majiggy setup in the BIOS. On some machines you can go into the BIOS and tell it to emulate a PATA drive – I wonder if you can do this and then send the image again to see what happens?

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 12:53:19 +0000

ok, have setup WDS and it works fine on all my machines apart from these blinkin A200′s

Through WDS im getting the same error as before.

Gets to the XP logo and then blue screens with the same error code.

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 08:34:30 +0000

ok, I’ll have ago this morning and let you know how I get on!
just got to wait for the Vista image to download so I can get the wim

Comment on Single XP Image for WDS by slim jim

slim jim — Thu, 12 May 2011 08:25:30 +0000

It sounds like it could be something to do with Mass Storage Device drivers then. In part 2 of the video, it is about setting up the correct folder structure on the WDS server. I believe when I was researching this I stumbled upon something that said the local sysprep is somehow lost/ignored and that’s why in part 2 we set up a structure on the server to send it back out.

I think your problems will be overcome if you switch to WDS (which it sounds like it might be in the pipeline for you). Unfortunately I don’t know a lot about Ghost so can’t really offer any further advice. Why not quickly try installing WDS and see how you get on?

Sorry I can’t be of more help.

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 08:20:02 +0000

strange as the address is correct…

Anyway, here’s the problem.
I created and sysprep’d the image fine. I then captured the image in ghost (dont have WDS setup yet).

I then pushed the image out to the laptop as i usually would using ghost. On the first boot, when it should be going through the setup I get as far as the Win XP logo and then get the BSOD.

Nothing really helpfull on it though just the standard BSOD with the error code

0x0000007B (0xF7a58528, 0XC0000034, 0×00000000, 0×00000000)

thats as far as it gets and then it just gets stuck in the reboot loop. On the other machine I tried the image works fine, boots into windows, sets up ok, loads the drivers runs the scripts and restarts ready for the user.

Comment on Single XP Image for WDS by slim jim

slim jim — Thu, 12 May 2011 07:13:57 +0000

Just whatever address was attached to your comment. Just asked where exactly you get the error i.e. is it during the transfer of the image, is it after the image has transferred and on the first boot, or does it allow you to boot up and do a few things before it fails etc.

Comment on Single XP Image for WDS by Ben

Ben — Thu, 12 May 2011 07:09:19 +0000

To my email address?
I didnt get it?