Bâshrat the Sneaky

You might want to disable the default monitor driver, so your driver gets installed. Please use the search function to find more about it. (don't forget to set it to 'Any date'!)

Are you sure about that? The 3C940 drivers ARE supported (look in the folder DP/L/3/3)

So far changed in V5.01.2: to do: add asus 3com drivers thingie (got to figure it out), add new via drivers. P.S.: swgreed's remark about the path is fixed too.

LOL like that expression

The only problem for this is that people would think I made it, so they would start asking questions about it. (like Why isn't there support for this or that?) So I think you understand I don't like that... Please be patient, these DriverPacks WILL come! (and the coming 3 weeks I have more time, so )

I have no spam at all . Not thanks to Thunderbird, but thanks to my ISP . (www.telenet.be )

Indeed. And the fix you suggested would be great! (but in general it works great!)

1. You have to UPDATE MANUALLY! I don't release a new DriverPacks BASE with every update, only when there's a bug in the update system. The current version is Update_V015.cmd (as stated in the overview topic), I gues you still have 11 or something... 2. It's explained in the method 1 and method 2 instructions (htm) files. You only have to edit the dosnet.inf file when you're using a multi-boot cd/dvd, WinPE or when you're starting setup through winnt32.exe.

It's single -A Here's a small tutorial

I know, I know, didn't take it that way It's just for myself, to keep the overview (which is already very difficult atm ) I'll have more time the coming week, so I guess I can update DP LAN and Sound, and add some improvements to the method batch files, and starting on DP Graphics.

Hi, I guess I've found a very odd WPI bug... I'm installing the applications iTunes and iTunes Art Importer, as well as many other apps. But for some reason, WPI always places those two at the end of the config file (so when I use the config option, those are at the bottom instead of between the H and the J...) I've attached my WPI configuration. Any clues? P.S.: I DID move them up again, where they should be, but they were automatically moved to the end of config.js after using the config option... config.js

I think adding the ability to chose which config you'd like to use might be very useful. (e.g.: home pc's, IBM workstations, Dell workstations, ...) How it should work? Very easy (well, it sounds very easy ): a main config file in which there are links to other config files: wpi-wpiscripts -config.js -myconfig.js -IBMconfig.js -Dellconfig.js What else would we need? Of course the required changes in the other js files (I can't explain that precisely, because I don't know JS) I guess you could simply add another button (choose config), a new windows appears and you can choose between the config files listed in the main config file (config.js) Sorry if this has been posted before, didn't want to read the entire topic/forum... P.S.: Superb program! Congratulations

Thanks to all of you!!!! I really am surprised I didn't notice this topic at first (if I would, I'd have replied to this one first, of course ) THANK YOU!!! ^^

It doesn't work for some IS setups... But that's a minority! Unfortunately it seems that this one is one of that minority

Please clarify... Did you use my DriverPacks or just a driverpack of yourself?

wow I could search months for the cause of an error like this, but I would never have thought of this... Thanks

Let's check an example. As you know, if I'd put all drivers in one (or multiple, doesn't matter) cab file, I'd have to place all inf files in the INF folder. It's not simply moving the inf file in the INF folder and voila, done, no not at all! In the following example the Source Disks Files are in the same folder as the inf file. (the other possiblity: all Source Disks Files are placed in subfolders (so next to the inf file there are these subfolders)) original driver's inf file [version] CatalogFile = BTS.cat signature ="$CHICAGO$" [Manufacturer] %BTS%=BashratTheSneaky [SourceDisksNames] 17="Devicename",,0 [SourceDisksFiles] abc.sys =17,foldername def.sys = 17,anotherfoldername should become: [version] CatalogFile = BTS.cat signature ="$CHICAGO$" [Manufacturer] %BTS%=BashratTheSneaky [SourceDisksNames] 17="Devicename",,0 [SourceDisksFiles] abc.sys def.sys Where abc.sys and def.sys should be placed in a cab file and editing layout.inf, adding abc.sys and def.sys under the section [sourceDisksFiles.x86]. All of this *could* be automated, but it would be VERY complicated. If everything goes well, I'll try to automate it in the next vacation I have (duration 1 week, within 2 weeks)

I guess it is, and I think it's not useful unless the inf-file editing can be automatized... BUT: what about that "Driver Compressor" in the 'device drivers' forum? Applying it on the driver packs will also save some MB's OR you could compress/'makecabs' all files within the DP's that are not .inf or .cat Indeed, it would save ALOT of space. I will try to implement this ASAP! (this time first some beta testing )

Indeed! In the specific VIA Hyperion case, all OemPnpDriverPaths are specified in the inf file, which is placed in that one folder... Another note: why would he be pointing to Chipset\VIA anyway, if you wouldn't have to specify any subfolder?

Hmm... What drivers did you include? I prefer to do these things myself, so I can know what I did.

Please do a search in these forums, there are several topics about it!

No you didn't say so, but I feel guilty for every problem with my DriverPacks, even if it's not at all my mistake... Don't ! You do a great job and everyone here agrees on it ... It's not that... It's just that I do everything to get it errorless, I check everything and so on and then these things show up... not my mistake... And if things are my mistake, well... I just start shouting at myself B)

No you didn't say so, but I feel guilty for every problem with my DriverPacks, even if it's not at all my mistake... I think the 'driver-situation' is very, very sad, complex and not standardized (enough)... I hope we can fix these issues asap...

You can create an AutoIt script for it to close it automatically!

Indeed, that's why I'm not sure.... EDIT: Problem solved, topic closed.