yea i wanted to make sure that i tried everything possible before asking on the forum is it possible to just re-run the vlk-2-oemchanger again using other oembios files, or do i need a separate tool/method? p.s: haven't tried the repair/clean install method though
Mine?? you can run as many times as you want. It would have backed up the VLK for you had you done that first.. I dont know what is involved with the other ones (the background), if it changes the background, I do not know what else it does..Ya know?? Just grab my tool, and run it. When it activates, back it up. Then you can try the other OEMs, if you want, and always get back to where you are now...
Hey 911Medic, Don't know if I goofed on something or not, but it seems that the CAT file is not being copied by the script to the "Oembios Files" folder. I put all the uncompressed files in the uncompressed oembios folder, and then tried to run the program. I got a message that the oembios.cat file was missing. I opened the "Oembios Files" folder, and there were only 3 files there that had been copied over from the "Uncompressed Oembios Folder" I manually manually placed the CAT file into the "Oembios Files" folder and re-ran and it worked then. Can you please check? It should be noted that after running it, rebooting, it appears it worked (won't know till I get this repaired system online) but when I opened the "Oembios Files" folder the CAT file was still there, but the other 3 were gone. I guess not only was it not copying the file, but it also is not deleting it afterwords like the others? If you need more info or if I didn't explain clearly (I've been up for almost 24hours and am dead tired) let me know, and when I'm rested up I'll do what I can to help you debug/fix it! Update: The system I used the tool on was indeed activated properly, OEM SLP ftw! So no issues, just the script is not copying the CAT file and is not deleting it afterwords. Blah.
Did you use the latest version?? I have seen a few people have the same problem with various tools, I have not been able to reproduce the problem without intentionally moving the cat file or renaming it..I dont know why..Maybe some permissions thing?? I guess if you could drop me a PM and explain what happened, and if it is consistent for you or only in certain circumstances..It has worked for me 100% since I started with a simple script some months ago..I don't get it?? I will help any way I can...