Search options (Page 37 of 213)

any more feedback on this?

working on it

Implemented with latest test ver

Implemented in test version

I am implementing this in our test version now

run Disk Managment...

LOL
Perhaps i could change it but no one ever mentioned it was annoying before

Provide the DL link to the driver and the HWIDs ...
CDOB hopefully will know what to do, he is a BartPE master

cool...
XP or 2k3 what SP level?
DriverPacks = LAN, MASS, WLAN and Graphics?

stock BartPE from bart website = Vanilla

here is a no brainer way to find out

http://downloads.vmware.com/d/details/p … hkYmRwKg==

That app is provided by vmware so users can easily determine if a machine is eligible to run a 64 bit version of an OS (be it windows, linux or other). Run it and you have your answer.

Can't make it any easier than that

PS are you going to try the 2k3 workstation route if you do in fact have a 64 bit machine? I would if you aren't interested in going with Win7. Vista and XP64 are garbage.

PSS It's entirely ok if you don't personally like NT6, you are certainly entitled to have an opinion. It's your machine after all. That was why I gave you several viable options and also offering the option of trying to help you fix / force the xp64 driver (though not recomended... lead a horse to water ). Even after I said that my experience is that xp64 is not worth the trouble ;P.

you are getting close now.

that nvidia problem was reported by another user you should be able to search our forum for that fix.

yes if you use SAD from a network location you will need the mass chipset and LAN drivers included with autoimage. if you can get autoimage to work then don't sweat the SAD method . Although SAD over the network will work great for updating a running machine if you are serviceing a unit . you may also find that it will take less total time to deploy by adding mass lan and chipset with AI, then calling SAD over the network for the remaining drivers, this would also avoid the 4 gig limit issue you fixed above (well done)

Check out the universal imageing forum  http://forum.driverpacks.net/viewforum.php?id=30  for some ideas about how to attack this issue there are several really good methods to choose from... the first one is very similar to your attempted KTD method BUT it calls the DriverPacks Finisher which makes a day and night difference for success. It also removes all the unneeded drivers from the machine after the deplyment . other posts explore SAD. SAD is also outlined in the FAQs.

if you have AutoImage working then you have the best solution for your needs in place... no need to over think it from there. I just tossed some other alternate options as an FYI in case you don't feel AI is the right fit for you.

No matter what you will need AutoImage to at least kick start your deployment.

Looking forward to seeing how this turns out...
Please let us know how you're progressing!
you may save many other people countless hours of work!

HINT: you wont need to reinstall driverpacks (except mass storage) after you get this working. You can simply substitute packs to update them .

no that solution will not be a universal image...
It will not install a huge number of the included drivers.
It might work on a very small number of machines at best and only of you don't include all the drivers.
and it will burn about 3gig of disk space for no reason.

Yes you MUST follow the instructions discussed in this forum... Years of trial and error by many experts in this method of deployment on thousands of machines have yeilded the results we have stickied as valid solutions. That is why they are there. PS this question has been asked answered many time before