WDS capture - no text?!

[sparkeh]

So I just started to use WDS to roll out XP images. I have a problem when I come to capture the image of the prepared machine. Basically, when I get to the dialogue that asks you where to locally store the image before uploading to WDS server, all the text disappears from the windows and buttons so I can't see whats going on

I don't really know where to start with this one, any one seen anything like this?

Are there any minimum specs for using WDS? These machines only have 256mb RAM, could that be an issue?

[Michael]

It does sound like a graphics driver issue. I presume you're using the latest drivers? Do you have this problem with other models or just this specific model of computer?

[sparkeh]

This model is the first I have tried. I will prepare another model and see what happens.

The weird thing is, that the boot capture dialogue loads up fine, its only when I click the 'browse' button to open the save file dialogue that the text disappears.

[Michael]

What graphics chipset does this machine use?

[sparkeh]

Intel 82845G/GL/GE/PE/GV

[cgiuk]

Hey..sorry I don't have an answer for you but I'm having exactly the same problem. Works beautifully until I come to set the location for the image to be stored and then I lose all the text. The GUI basically falls apart. Looks like it may be a chipset issue. Our machines are using exactly the same ones as yours Sparkeh.

Anyone else got any suggestions?

[sparkeh]

Looks like it may be a chipset issue. Our machines are using exactly the same ones as yours Sparkeh.

Thanks for that, thats really interesting.
Haven't had a chance to investigate further though.

[clywedog]

WDS Requires 512mb when deploying images but I am not sure about the capture side. Did you run the sisprep tool from the same xp/vista CD that you created the image with?

Chris

[cgiuk]

Thanks Clywedog for the info. I'm gonna give up now. I had an hour spare so I thought I'd give WDS a go and I've only just learnt that the client's need 512Mb RAM. The room I want to image only have 256

Really fed up about that...the whole setup of WDS on the server worked like a dream. Knew it was too good to be true.

[ChrisH]

Hmm I wonder if thats why my one model with 512 meg ram and shared graphics gets an error before even loading up the wizard......

[gshaw]

Thanks Clywedog for the info. I'm gonna give up now. I had an hour spare so I thought I'd give WDS a go and I've only just learnt that the client's need 512Mb RAM. The room I want to image only have 256

Really fed up about that...the whole setup of WDS on the server worked like a dream. Knew it was too good to be true.

I feel for you having machines with only 256MB RAM ouch

[cgiuk]

Tell me about it GShaw. It's what you get for working in a small independent primary school. No money whatsoever! I've told them again and again we need to update stuff but will they listen? lol

[Gibbo]

I've noticed a similar problem with some desktops with not quite 512MB of RAM (8MB shared)

I can PXE boot, select "capture" and capture to the hard drive, but if I select the "upload to server" it does nothing for about five minutes before returning "cannot find server".

Although, thinking on, I wonder if it's more to do with the network card? I've not imaged these machines before and it uses an Infineon ADMtek NIC.

EDIT: Yes - tried to deploy an image to it an a box has appeared "WdsClient: a matching network card driver was not found in this image".

Bloody Fujitsu.