Floppy Posted November 4, 2006 Posted November 4, 2006 (edited) Or you could search for a string that appears in every BIOS.[SM]CMD=".\PromptForChange.exe"Trying this on WinXP HomeI have PromptKey.vbs in the same place as oemscan.exe/ini. (1.3.1)I have this in oemscan.ini[SM]CMD=".\PromptKey.vbs"Written at the end of oemscan.ini.When I test it it say's;Matched: SMRunning: PromptKey.vbs : FailedI have tried to run a cmd file instead(test.cmd)...no go.Why on does it do that?If I run PromptKey.vbs, it works.In real life on a Dell pc it workes perfect.....-----------------------------------------------------------------UpdateSorry about this. The problem seems to be more complexed.The CMD="" thing does not work at all, it worked like a charm earlier today, but not now.I copied the hole oemscan directory over to another PC and tested there, but it does not work.Same error : Failed.Any ideas? Edited November 4, 2006 by Floppy
xehqter Posted November 5, 2006 Author Posted November 5, 2006 @FloppyOEMSCAN uses the CreateProcess API to execute whatever is in the string. PromptKey.vbs isn't an executable file, it’s a script. You need to run the interpreter wscript which will parse/run the script.[SM]CMD="wscript PromptKey.vbs"
Floppy Posted November 5, 2006 Posted November 5, 2006 @FloppyOEMSCAN uses the CreateProcess API to execute whatever is in the string. PromptKey.vbs isn't an executable file, it’s a script. You need to run the interpreter wscript which will parse/run the script.[SM]CMD="wscript PromptKey.vbs"No Go I tried this:[SM]CMD=".\test.cmd"and test.cmdPauseNo GoSame error : FailedIam realy confused
RogueSpear Posted November 5, 2006 Posted November 5, 2006 @FloppyOEMSCAN uses the CreateProcess API to execute whatever is in the string. PromptKey.vbs isn't an executable file, it’s a script. You need to run the interpreter wscript which will parse/run the script.[SM]CMD="wscript PromptKey.vbs"No Go I'm not sure when you're running PromptKey.vbs, but if it's during Windows setup you'll need to use cscript as wscript is not available yet.
Floppy Posted November 5, 2006 Posted November 5, 2006 (edited) The tihing is that nothing will run if I write like this;[SM]CMD=".\test.cmd"It just fails Iam trying to prompt for changing the XP key if there is no match. Edited November 5, 2006 by Floppy
xehqter Posted November 6, 2006 Author Posted November 6, 2006 Don’t know what to tell you, during what part of setup are you running oemscan.exe and secondly does it also fail if you run oemscan after the install is finished?
Floppy Posted November 6, 2006 Posted November 6, 2006 (edited) Don’t know what to tell you, during what part of setup are you running oemscan.exe and secondly does it also fail if you run oemscan after the install is finished?Ok, I will try to show you! Thank you for your respond This is my oemscan.ini;; Fujitsu Siemens OEMBIOS Files; SLP = Fujitsu Siemens;[FUJITSU SIEMENS]PATH=".\FUJITSU\"RANGE=""MATCHARG=""CMD=".\FUJITSU\OEMCOPY.CMD";; ASUS_FLASH OEMBIOS Files; SLP = ASUS_FLASH;[ASUS_FLASH]PATH=".\ASUS_FLASH\"RANGE=""MATCHARG=""CMD=".\ASUS_FLASH\OEMCOPY.CMD"[SM]CMD=".\cscript PromptKey.vbs";CMD=".\test.cmd"This is my cmdlines.txt[COMMANDS]"useraccounts.cmd" "RunOnceEx.cmd""./HomePreaktiver/oemscan.exe"I have used this on sevral diff. PC's, but not with this part;[SM]CMD=".\cscript PromptKey.vbs"I wanted to test it firts on Microsoft Virtual PC, and the [sM] trigs OK but the <<CMD=".\cscript PromptKey.vbs">> goes : FAILED.It does not matter if I run the oemscan.exe durin install (cmdlines.txt) or from the desktop, after instal.If I change <<CMD=".\cscript PromptKey.vbs">>To CMD=".\test.cmd"The result is the same : FAILEDThis is my test.cmdPauseIam trying to prompt for changing the XP key if there is no match. Is there another way tho promt the user to change the XP key, if oemscan doesen't do it's "thing"? Edited November 8, 2006 by Floppy
FreeStyler Posted November 6, 2006 Posted November 6, 2006 (edited) <<CMD=".\cscript PromptKey.vbs">>To CMD=".\test.cmd"commands are ok, have you placed promptkey.vbs and test.cmd in the right place? (same dir as oemscan.exe) Edited November 6, 2006 by FreeStyler
Floppy Posted November 6, 2006 Posted November 6, 2006 <<CMD=".\cscript PromptKey.vbs">>To CMD=".\test.cmd"commands are ok, have you placed promptkey.vbs and test.cmd in the right place? (same dir as oemscan.exe)Yes, i have If I run;oemscan.exe /dI get ;Matched: SMRunning: PromptKey.vbs : Failedor with test.cmd in oemscan.ini;Matched: SMRunning: test.cmd : Failed
Floppy Posted November 6, 2006 Posted November 6, 2006 (edited) duh... remove the /d switchThe /d just makes oemscan show you what happens...right?Or does it change how it works...... UpdateI tried it just running oemscan.exe...........success I have more grey hair now Thanks to the ones who helped me!! Edited November 10, 2006 by Floppy
vpn-user Posted November 6, 2006 Posted November 6, 2006 You want dry-run but still run the script? Weird, isn' t it?
Floppy Posted November 6, 2006 Posted November 6, 2006 You want dry-run but still run the script? Weird, isn' t it?I did a mistake...ok..??
TheUni Posted November 12, 2006 Posted November 12, 2006 Haven't really checked on this thread since i wrote those (modified the official microsoft) scripts...What's the consensus? do they work? If so, i'll do a little more work and get some basic error checking and looping in emTheUni
Floppy Posted November 13, 2006 Posted November 13, 2006 (edited) Haven't really checked on this thread since i wrote those (modified the official microsoft) scripts...What's the consensus? do they work? If so, i'll do a little more work and get some basic error checking and looping in emTheUniI have done Pro&Home on; DELL,HP,Compaq and FS--->No Problem Edited November 13, 2006 by Floppy
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now