twig123

@MadBoy: Check your PM's.... (Edit) ... now a 2nd PM, and a further in-depth incite... If you want you can either post or pm a reply... doesn't matter to me, but let me know either way. ~Dave

Check out my debug report file attached... here is what I gathered from it [23:10:26] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: Total Files Listed: [23:10:26] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: 0 File(s) 0 bytes [23:10:26] - DEBUG in REGISTRYDEVICEPATH FUNCTION 0: 158 Dir(s) 8,992,768 bytes free I gather that it hasn't detected ANY of the inf's that I have in the All_Drivers folder... shouldn't it have found the files in each of the folders and reported a size??? also, still with the new 5.5 version, when the program starts it changes the "devicepath" key from "%systemroot%\inf;" to blank... then back to the systemroot after closing... with all 3 registry options (Begin, End & None). the full debug is attached to this post if u need a further look. hardware.log.txt

Well your release was ~11am from your post... I downloaded the 'latest' copy ~2hrs before my last post... so ~10hrs after your 5.4 re-release, is when i downloaded it... I will re-test with the latest v5.5

I was looking in the registry when the 'None' option is used... and the "DevicePath" key changes to blank when the program runs. Shouldn't this be set to the Driver source path? cause I assumed that the 'None' switch was just used to not look in the current systemroot\inf folder, but still use the new variable path...

I checked and the 01 code changes are working now. also, if I choose Begin or End... it still finds the existing INF first, and asks for the missing files. However, if I choose None, it will search the CD and will overlook the existing INF's like it is supposed to. I was also wondering, after the devices are re-detected, I have to walk windows through the new hardware wizard. Can this be made automated? or is that already planned for a future release? Here is my INI file if needed: [INFO] Start=Automatic Mode=Standard Drivers_drive=CDROM Drivers_dir=\All_Drivers Device_manager=Off Method=RegistryDevicePath Logging_to_file=Yes Logging_option=Advanced Drivers_Packed=No Copy_drivers=No Copy_where=C:\Drivers Delete_drivers=Yes Create_backup=No Leave_registry_entries=No Debug=No [ADVANCED] Registry_path=None Problem_Ids=01,10,18,28,37,39

one Quick observance... the single diget code issues (ex: Code 1) is not removed when specified like in your settings. for it to work correctly, your software sees this as a ProblemID 01 (Code 01)... aka must be stated as a 2 digit code for it to be removed properly. more reporting after further tests.

Usually Code 10 is incorrect drivers... In my case I had working sound drivers from 2002, i removed the driver to test and a the system tried to reinstall the driver from the inf that is installed... but failed trying to find an additional file on the system. (not related to your software, just some extra testing). When your software removed the unknown device it would just attempt to reinstall the old 2002 driver, instead of the new 2006 provided on my driver cd. I can vouch that the 2006 driver work if i point windows to the folder where they are though. ... but thanks for the software update, I will test the new release shortly and report my findings.

As long as the computers all have the same version provided from dell (ex: home or pro) with the dell logo on the product key, there is no difference between the cd's. As a matter of fact, do a search on the internet for product key viewers and check the systems (hint: they are already ALL going to be loaded with the same keys). so there should be no issues there. second, you are close with the WPA file... but the only way to transfer pre-activation is from the OEMBIOS files. you can do a windows search for OEMBIOS and backup those files... but usually those are included on the system install CD's that dell provides, so if you use that as your source media then you shouldn't have to worry about pre-activation.

7zip packed drivers are now working correctly. However, I have a sound card that has a "Problem ID 10" which the software says that it is removing unknown hardware, but directly after that it says that there was no devices removed... Sometimes when the program runs it tries to reinstall the old malfunctioning drivers that are already on the computer, instead of the new driver provided in BTS DriverPacks. Any incite on this issue?

How would one change it to 800x600?

nm, patches were just released

Run MGADiag and copy the results to the clipboard, the report will show the first 4 SLP strings. (The GUI doesn't show the strings.) Thanks. Also just wanted to report this: Emachine W2060 results: Manufacturer: System Manufacturer Model: Product Name 53797374 656D204D 616E7566 61637475 726572 However, it activates with the same oem files as the other Emachines that have been reported.

Just wondering... isn't today Patch Tuesday for Microsoft? ...and no patches?!? ..... Weird!

Sry guys, but i'm working off of short term memory right now... can someone refresh me how to grab the SLP BIOS string like this: (Dell System,Dell Computer,Dell System,Dell System) or similar. I seem to remember a batch file... but I can't remember for the life of me... Thanks

Bad hard drive. ^^ Exactly To test for sure go to another computer search online for DFT (Drive Fitness Test, By Hitachi), Burn it to a CD, Run the advanced test and it will tell you if the drive is bad or not.

Sounds cool, I can't wait!

How can this be changed to include the previous version on 7zip? because the newest seems to be causing an issue with un-compressing the 7z files.

Universal wasn't quite what I ment... I have Dell, Gateway, HP etc.... Thanks for the quick reply though

Ok, the issue is... I am trying to make a universal disk, but I dont have access to all the system to get that info ATM. Is there a way they can be converted from CRC32 to Hex? (doubt it, but doesn't hurt to ask)

Also, does it make a strange sound (much like a high-pitched squealing or whine) when it turns off? If so, the shutoff was due to something shorting out and activating the overload protection of the PSU. Your Power Supply Is Faulty!!! That is where the high pitched sound is coming from! Replace it ASAP, or it could fry your mainboard! ...also, since the power supply is faulty, check the Capaciters in the upper left by the processor to make sure none of them are bulging/swollen or look like battery acid coming out. If there is, then you need a new mainboard as well.

Question, I have some OEMBIOS files that have the CRC32 names... is there a way to convert them to Hex, so that they are compatible with Bezalel's Activation scripts?

no, it can't damage your motherboard. if it could, the motherboard would have to have loose diodes or whatever already, and you'd know about that. Actually, if it was air from a compressor if can, because there may be moisture in the air....

I was wondering if anyone has thought of making a addon pack that would install all of the detection tools to identify the system models. Ex: HP has a button on their site to "Detect Devices", which installs a IE Plugin in order for that feature to work. Also, Dell, Gateway etc. This would be nice to be able to just use the feature, instead of having to try to refresh the page after the tool installs.... Just wondering what you all thought about something like this, and if somebody wanted to take the liberty to create these since I am short on free time...

This is usually part of the AOL Safety & Security center... I actually recieved the exact same error today (installing AOL) re-download it. should solve the problem.

... this doesn't make since... Why would it work with no interaction on a Vanilla OEM disk, but on a Slipstreamed disk it prompts for drivers instead of auto-installing the "HID-Complient Mouse" drivers like the vanilla copy did?!???