I've got a fairly universal RIPREP image I use through SMS OSD. As long as you've got an ACPI (old or new version) HAL, then I can handle it.

You'll also need to deal with HAL issues - booting an ACPI HAL on a Standard PC HAL system will cause it to just black screen before it does anything. Vista's images are HAL independent, I am not sure how it will deal with mass storage issues which is also key.

I've had no luck with swapping motherboards under XP - I've always had to do a repair (which works pretty well).

It looks different for sure, but when I ran it and looked in %TEMP%\IPMx2\All all of the usual files appeared to be there?

29

(15 replies, posted in DriverPack LAN)

This is getting off topic but to be honest, I've got to disagree. We are a small group of testers, just because we are not aware of any bugs in existing drivers it doesn't mean they aren't there. You've got a point in that new drivers can contain issues but on the whole every newer driver I install is almost always without issue. They could improve performance for example. Without fail drivers do improve over time.

So does that mean we are now going to test every single driver (if the HWIDs remain the same) and then if it is "better" (some magic method that if we like it, then it goes) then it gets put in?

Just my 2p anyway. smile

30

(3 replies, posted in Other)

Awesome stuff. smile

I've found Vista's driver support to be actually quite poor.

I'd be interested in making (a 3rd party if necessary) driverpacks for Vista, if no-one else is!

I do this, it is quite possible. You need to copy the drivers locally, and ensure the sysprep oempnpdriverspath points to EVERY folder with a .inf file in it. Watch for the limit of 4096 characters here.

Then just delete these files once the mini-setup is complete.

I wouldn't call Parallels a big player, I believe VMWare has 80% or so of the virtualisation market. smile

The needed file extensions will depend on the drivers involved, there is no set rule for this.

I would suspect if you created a XP CD with the Driverpacks integrated, all of your systems would come up with the correct drivers anyway!

Easy post to deal with then. smile

1. USB. I've not got this working, so I can't really help. You need to add a plugin for USB into the plugin directory, and then any files it requires. I could never ever get it to enable let alone anything else!

2. Win2003 SP1. Specifically a slightly newer driver base to start with, and my favorite reason is that I can boot the BartPE ISO image into RAM using a RIS server. This makes it very quick. I wouldn't expect any problems, but if you've got XP SP1 working then you may be ok. Perhaps a potential for a fair few security issues with SP1 though.

I wasn't aware of any sound DRM in XP actually, even with this patch.

Vista of course, is a whole different matter!

http://www.viaarena.com/default.aspx?Pa … CatID=1070

Been released today!

LittlBUGer's server is very nice, I normally use it for autopatcher's downloads if I don't use bit-torrent. smile

I'll chip some money in anyway!

Post your output from this:

http://www.driverpacks.net/Downloads/save_hwids.exe

You literally just dump them in the folder, when you run BartPE to create the ISO it will process everything it finds in those directories. I recall specifically a lot of trouble with Nvidia's NICs, so you may wish to leave them out. You can see it in the logged output from BartPE anyway.

BartPE doesn't support USB either, so you'll need a plugin for that. I've tried a bit to get it to work, but the ISO wouldn't generate so I didn't bother!

I'd recommend Win2003 SP1 as the source if possible also!

Also as Bâshrat the Sneaky said, this is a manual process only, it isn't supported by DriverPacks BASE itself.

Where you install BartPE you'll have a drivers directory, and in that you've got Net & SCSI Adapters folders. Simply dump all of the necessary network/mass storage drivers from the driver packs into those directories. Some will fail mind, but a majority work. Or just pull the ones you need from the driver packs and you'll be good.

I don't use chipset drivers, don't think they are really needed for this!

43

(10 replies, posted in Software)

I never thought of that.... roll it updated the Nvidia graphics driver but nowt else.

It all depends on if said companies can be bothered working with Microsoft to get their driver. I mean, today I've already seen ATi, Nvidia & Realtek all release newer Vista drivers.

44

(10 replies, posted in Software)

Do we have any plans for Vista DriverPacks yet?

The reason I asked is that the first system I installed Vista on was missing two drivers - the Sigmatel audio & probably Intel chipset drivers. Not a great start!

Whilst BASE would be some time off I would imagine, is there any reason why we couldn't start collecting the drivers together now?

Cheers!

Here it is:

http://downloadfinder.intel.com/scripts … p;lang=eng

If they all have the same hardware, you could just "cherry pick" the drivers you require and delete the rest.

Personally, I install them all as you never know when they'll add a new graphics/sound/etc card!

This thread is helpful:

http://forum.driverpacks.net/viewtopic.php?id=1117

It would seem as if you are not the only person with this issue, however the cause is currently not known!

48

(5 replies, posted in DriverPack Graphics)

Some of the mobility cards have funny HWIDs, which mean you need a specific driver which ATi do not provide. The same is true with my iMac, which has a ATi X1600 mobility in it!

For:

RTL8100B(L)/RTL8100C(L)/RTL8101L/RTL8139C(L)
RTL8139C(L)+/RTL8139D(L)/RTL8100(L)
RTL8130/RTL8139B(L)

http://www.realtek.com.tw/downloads/dow … RTL8139B(L

If no-one else updates 'em, I'll do it when I'm back at work! And I'll write a little bit more in the hope that the SPAM filter won't ban me again. tongue

Just checking - nothing related to the issue mentioned here is it?

http://forum.driverpacks.net/viewtopic.php?id=1103