[Domain blocklist, revised.]

Well a FYI to anyone that still is interested in this project... I have noticed that downloads from apple are blocked (ex: quicktime). apple.com and edgesuite.net should be removed to correct the issue.

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

@vpn-user: The original OEMBIOS.CAT file is backed up to SystemDrive when it validates the OEMBIOS files being copied over. If validation fails it restores the original .CAT file. The file should be deleted if validation passes. Something to fix in the next release.

Do you use the latest (1.3) version? it looks like your using 1.21

DOH! I'm sorry guys, I coulda swore I had the latest... I guess I'm just losing my mind, its been a long week...

Thanks

PS: any chance of a silent switch in a future revision?

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

I just activated a system with your OEMSCAN utility (which is a life saver) and I noticed that for some reason it makes a copy of the 'OEMBIOS.CAT' file in the root of the C: drive... anyone else notice this?

[Domain blocklist, revised.]

[Unofficial Cumulative SP 5.02.2195.17 for Microsoft(R) Windows(R) 2000]

...still a no go, could this be re-upped? or a mirror added?

[Unofficial Cumulative SP 5.02.2195.17 for Microsoft(R) Windows(R) 2000]

I as well can't download the file... it stops @ 172MB and says it is completed. Very fast downloads @ ~6000Mb/s... but corrupted upon extraction

[Drivers Instalation in Post-Install stage (New Method)]

I saw "CD/DVD/USB Autorun" in one of the menus...

U know that USB can not use an autorun.inf file unless you do a registry edit beforehand... right?!

Unless you know of a way around that

[Domain blocklist, revised.]

@BoardBabe - No updates in a couple months...

Is there any status update? or has the project been abandon for the time being?

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

@discountpc I think the script TheUni is making will be exactly what you want. At least that is what it sounds like to me.

I think so too, I just wanted to clarify for the people that didn't understand what I was requesting.

Thanks

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

>So, basicly if I would type in all the keys for Home and All the keys for Pro... and it would detect that is one or the other, and use the appropriate key

To install home & pro from the same disk, wouldn't you just use CDShell like everyone else? With two separate folders, there's nothing to detect. The Pro keys would live in the pro folder and the home keys would live in the home folder.

Seems like some ppl are missing my point...

I dont want 2 seperate scripts for when I compile my CD's. All the rest of the files that I use are universal... aka RyanVM Updates, BTS Driverpacks and can be used with Home AND Pro... why not the key script? I would rather have 1 big code to do so, rather than a seperate code for each version of windows... make sense to me, and would make it easier IMO

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

they're on my pc at home, i'll post when i get back.

I'm patiently waiting, it sounds exciting

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

it wouldnt have to prompt you at all. just quietly use whichever one works

good enough?

Yeah, as long as it works... but I have seen some key-changers that allow you to type anything (after windows is installed) and it will change it to an invalid key, but windows complains after the fact. that is the only thing that I am concirned about.

But if it works, it works. Sounds good to me

Maybe after the scripts are complete, could you be so kind as to share the wealth?

Thanks

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

the key isnt what changes the distro btw home and pro. They're different disks.

afiak you'd still have to use a home cd to install home and a pro to install pro. if you're wanting to do both, you should look into Powerpacker made by siginet.

I am very aware of this, the reason for my asking is that I use the same update packs, drivers, and addin software for both my Home & Pro distro's... and it would be nice to not have to modify the keys and software every time I want to compile a different vesion. So, basicly if I would type in all the keys for Home and All the keys for Pro... and it would detect that is one or the other, and use the appropriate key.

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

on another note...

I've already created a .vbs script that changes the key that takes a file (containing a key) as an argument. it works successfully in sp2 to change my key. For example:

cscript changekey.vbs "..\dell\serial.txt"

Does this detect the difference between Home & Pro? so it can be made universal

[Drivers Instalation in Post-Install stage (New Method)]

@MadBoy

I haven't had any free time over the last day or so to test the latest build, but as soon as I get some free time I will report back with results.

[Why I hate WinXP crap!]

Kelsenellenelvian - nice, thanks, but... but the directory still open with the default thumbnails view witch I try avoid. Now these thumbnails are just generated each time, so... not a solution. How to force the directory open with "list" and not with "thumbnails" view???

Other than that it the point must stay.

Simple,

Click View, select "List"

If you want every folder to do the same as this and open in list view, after doing the above go to Tools and select "Folder Options...", Click the "View" tab, and then click the "Apply to All Folders" button.

Poof, magicly (and sooo complicated I might add) all of your explorer windows will now open in List view and will not create any new thumbnail thumbnail files... cause, well, you're not in thumbnail view anymore

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

Actually Randy I was going to play around with the same thing. I think maybe xehqter could allow a special string to be specified in the cmd= key that way if his tool sees that string then it knows to send the bios string that is found to the cmd. For instance:

CMD=".\keychange.exe" @Bios

Could return:

CMD=".\keychange.exe" Compaq

Then keychange.exe could be a tool that will change your key according to the manufacturer code sent to it. If a manufacturer code is not found then it can open a box asking for a valid key on first boot.

I can make the keychange.exe if needed.

Sounds great to me!

Is there a way to add detection for what version of XP is being used? maybe another switch on that that would insert a different key that is provided depending on if it is HOME or PRO or MCE... for those of us who like to be legit?

[Drivers Instalation in Post-Install stage (New Method)]

there is 'h' in one and 'H' in other

I've tested and REMOVABLE & CDROM seem to be FULLY working now!!!

...Who would have thought that would be the issue.... a cap. letter

Now all we gotta figure out is how to detect when the devices are all installed to close the program

~Dave

[Drivers Instalation in Post-Install stage (New Method)]

Sweet! another fast release! I like waking up to a new release

I'm gunna be @ work for another 4hrs, but I will test once I get home and let you know

[Drivers Instalation in Post-Install stage (New Method)]

Hmm... Still a no go...

Attached are my logs tested with the REMOVABLE switch that is not working, and I also tested manually setting H as the drive letter in the ini file that does work.

When REMOVABLE is specified, it still is not writing to DevicePath in registry, but does work beautifully if the drive is specified. I have attached my hardware log & hardware ini. maybe they will help.

I give you props on the fast new-releases though

REMOVABLE_hardware_NOT.ini

REMOVABLE_hardware_NOT.log.txt

H_hardware_Working.ini

H_hardware_Working.log.txt

[Drivers Instalation in Post-Install stage (New Method)]

I'm confused... now its not working for me again...

can you double check it again for me?

(edit) check PM

[Drivers Instalation in Post-Install stage (New Method)]

I'm doing some more testing now.

... strange I can't get REMOVABLE to work now either :-|

I'm going to delete all my files and re-create all the settings files again to eliminate the issue being on my end. Also I'm going to test on a 2nd system just to make sure.

[Drivers Instalation in Post-Install stage (New Method)]

*EDIT*

Fixed the issue with CDROM/REMOVABLE. DiscountPc test please

Sweet, the REMOVABLE switch seems to work now , however, CDROM is still M.I.A

(i'm off to my G-rents) bbl 2day for more testing...

[Drivers Instalation in Post-Install stage (New Method)]

seems like i missed one thing in program that was related to bug in 0.5.5. Users that were using CDROM or REMOVABLE for drivers_drive wouldn't get DevicePath into registry

Should fix the issue now discountpc Tnx again

Just downloaded & tested 0.5.6 ... and issue still seems to remain that the drive is not registered as a variable and thus not stored in the registry... I haven't had time to debug it yet and I have only tested with the CDROM tag at the momemnt... but still no path is entered

...also would it be possible to detect the class of the device (audio, video, network) and have it search specific folders before it starts searching the entire Drivers DIR? ... to kinda make Bashrat The Sneeky's Driver packs more usefull... like this structure: a sound device will search the X:\All_Drivers\S (S for sound) first. or X:\All_Drivers\G (for Graphics). I think this would dramaticly cut down on the install times specifcly when using Bashrats driverpacks. Just a suggestion

~Dave

[Drivers Instalation in Post-Install stage (New Method)]

Thanks for the quick fix

I'm a code junkie usually, but this program is like Chinese to me

I just got to work, so I will test if I get a sec... otherwise I'll test once I get home.

~Dave