26

(2 replies, posted in Universal Imaging)

even i cannot ask such questions with so low level of information. tongue

27

(36 replies, posted in DriverPack Sound)

hilander999 wrote:

@MR. OverFlow

At long last, and with lowly incontestability to the foresight, throughput, and contention to retain information, no matter how flawed the theory may be, you sir, still amaze me on a daily basis when you launch personal attacks on the lower level life forms that scamper at your feet, simply because your too damn lazy to fold time back a notch and allow this poor sole the chance to catch up.

~hilander999 out.

Bravo, hilander999, i never could have said it better. No offence, overflow! smile

28

(32 replies, posted in Other)

yeah...now i finally begin to have a clue, what is this hard work all about. I am indeed at the beginning of the road - exactly the right words. I thought, why several driver searching programs choose you the wrong driver. They search by HWID´s generally (i think), but if there a more than 1 driver in the database with the same HWID support, then its exactly as you said. IE i got a touchscreen mouse driver for my laptop, but i had a simple Logitech USB mouse. The result - mouse didnt work. How could it..theres no point touching LCD and hope it moves the mouse. LOL. Em..could there be a chance, that the driver program thought my touchpad is a mouse? It was a Iobit Advanced Systemcare component.

Thank you, Overflow! That answer helped me a lot. Is there a sticky or tutorial about the basics of the driverpacks development or the conflict situations? Maybe it is worth to create such, if it doesnt exist, so everyone with some common sense can understand or even get some clue, what smart guys are talking about. smile I dont mean the driverpacks base tutorial, but...something more general about making the packs. I think, i dont know the right keywords to search google and there may be no good information about it.

Edit...found sticky for 3rd party packs

29

(32 replies, posted in Other)

i understand. So..WHQL is crap and maybe i should nlite the install media, so that drivers will be unsigned and then put the tweak, that unsigned drivers will be installed without prompt. Can i ask...where do you get all the needed hardware to test on? And the knowledge about HWID´s it is ment for...comes from manufacturer? Or is it the HWID Tool? I thought that gives you knowledge about the current machines HWID´s it is run.

I have the suspicion, that if a manufacturer makes a new driver, then it is especially ment to support the newest piece of hardware. If the older hardware fails, then you have to put the most recent driver into package, that supported the oldest hardware and make another folder for the newer equipment. How does windows setup program know, which driver it should install? Guess both of the drivers are ment for same HWID or not?

30

(10 replies, posted in Other)

mr_smartepants wrote:

In your situation, a volume license may actually be better.  Expensive, but easier.
But if you're willing to do the research, the OEM SLP method would be the cheapest method if you're installing the OS that's listed on the COA sticker on each machine.  Perfectly legal and it's M$ preferred method.

Actually, thinking about it, you may not be able to purchase an XP volume license because M$ dropped it from active support.  If you're lucky, you may still be able to purchase a TechNet subscription to include XP.  But you might have better luck migrating your fleet to Win7 since it's so awesome.

Yes, the problem is that i have no use for volume licence. I want to do such install source (IE RIS) with which i am able to install OEM licence XP on every single machine with its respective COA code pre-activated. So...thats a demand that is hard to fulfill, i guess.

31

(32 replies, posted in Other)

I am a total noob, so please dont hit the asker´s mouth. Still, i want to get smarter, wanna learn, if i´m capable of course tongue. I understand something about the inf and sif files from which that driverpacks can be called.

Em..ok, let me get it straight from wood and painted red. WHAT is this 'stability'? As i understand from this topic here...if a new driver version is being release, you have to delete previous & copy the newer version files to the respective folder of the respective driver pack. My questions are...does the new driver have to be tested by WHQL when the manufacturer has already tested it? Do the manufacturers make crap with their drivers or is there something about the way drivers are found by the system or... Yeah, what do i guess here, what do i know about it sad

I may be replying to myself now, but does the new driver if it´s found have to be tested for every single piece of electronic board, it is ment for? There are hundreds of different models maybe, that a single driver would run. Do i understand it correctly?

Hi! I´m sry if that was answered before, but... Why did u choose to remove the 3rd party driverpacks option from method 1. Yes, it can be selected, but it wont integrate. The 3rd party driverpacks option is also removed from update checker. I understand the limitation of 4096 symbols, but maybe i want to integrate some of the 3rd party driverpacks in place of a "mainstream" driverpack IE Sound, WLAN etc.

33

(10 replies, posted in Other)

mr_smartepants. I appreciate very much, that you made that OEMSCAN addon, but unfortunately there are such oembios-es with which the addon wont work. Yeah...maybe i am unable to find the right oembios files. www.oembios.net doesnt give the right files for every available machine. IE Compal and none of my local manufacturers. Of course you cant know them all. So...guess there´s nothing to do...unless there are registry codes available and the files.

34

(1 replies, posted in Software)

Hi! Didnt find anything particular about this in the forum. I integrated sound drivers with method 2. When the install process begun to identify PNP devices, i got the following error. Asioreg cannot be run in dos mode, terminate the program? I can be mistaken with the exact message, because it was a while ago. I think i can reproduce it.

my question seems to be somehow related to this thread.

Does the driverpacks finisher remove also unneeded drivers by the system or are all the useless drivers integrated into system, taking up space?

36

(10 replies, posted in Software)

Yeah, i know that i´m not smart on this, but if you cant question the right questions, then how will the search help you? I´m very sorry. I really didnt mean to insult anyone´s intelligence or anything like that. You know there´s such expression - "a fool can ask more than ten geniuses can answer". So please dont be mad at me, trying to get smarter.

37

(10 replies, posted in Software)

I see ... sad Yes, that experiment can get pretty nasty setbacks or how should i say that...

One thing though, you do not always need all the DriverPacks, so you might stay under the 4096 limit.

Yes, thats right. The main "symbol-eater" is of course WLAN, but its highly reccomended to laptops for example.

I think, i should explain a little, why did i join to discuss the matter. I´m trying to develop a windows install server, so people can boot over the LAN and install windows x86 with their own OEM license codes and optional software. Thats not driverpacks matter of course. But...if i could get the install script bundle the needed driverpacks files, unpack them and install only needed drivers. Thats the case here.

I need to integrate mass-storage text-mode and LAN anyways, so the install script is able to connect to the server to download the needed packs etc. For that we could open another topic.

38

(10 replies, posted in Software)

OK! Thank you for the great explanation, Jaak. Btw, i have the same name irl as your nickname here. I understand the very big maintenance problem, but i have a new thought/proposal for it. The packs can be exactly the way they are. But...during the integration of packs could be a script, that has the capability to "explode" the folder stucture the way you described. I dont mean to put the folders of all driverpacks into one root folder, if possible, only the folders of the current pack. I´m working on the script right now.

I´m very sorry, if you think so, Overflow. I just try to solve problems, why it wont work. If there´s absolutely no reasonable and not-bone-breaking way, how the problem can be solved, then i agree with you.

39

(10 replies, posted in Software)

hi! I´ve been looking over the internet and found a 3rd method for integrating the driverpacks. Drivers are called via winnt.sif directly from cd at T-39. Should be worth a try to put the option into driverpacks base. The problem is that drivers w/o inf file cannot be integrated with this method, but are there any such?

Could i suggest that if the oempnpdriverspath is limited to 4096 symbols then why isnt it possible to try to shrink the folder structure? I mean the driver folders (contents of folders), that have no common/same filename in it with other folders, could be all in one root folder. Isnt it so?

I´m open for feedback.