Jump to content

OEMScan - Automated Multi Manufacture Pre-Activation Utility


xehqter
 Share

Recommended Posts

Or you could search for a string that appears in every BIOS.

[SM]
CMD=".\PromptForChange.exe"

Trying this on WinXP Home

I 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: SM

Running: PromptKey.vbs : Failed

I have tried to run a cmd file instead(test.cmd)...no go.

Why on :realmad: does it do that?

If I run PromptKey.vbs, it works.

In real life on a Dell pc it workes perfect.....

-----------------------------------------------------------------

Update

Sorry 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 by Floppy
Link to comment
Share on other sites


@Floppy

OEMSCAN 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"

Link to comment
Share on other sites

@Floppy

OEMSCAN 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 :wacko:

I tried this:

[SM]
CMD=".\test.cmd"

and test.cmd

Pause

No Go

Same error : Failed

Iam realy confused

Link to comment
Share on other sites

@Floppy

OEMSCAN 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 :wacko:

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.

Link to comment
Share on other sites

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 :hello:

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 : FAILED

This is my

test.cmd

Pause

Iam 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 by Floppy
Link to comment
Share on other sites

<<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 :whistle:

If I run;

oemscan.exe /d

I get ;

Matched: SM

Running: PromptKey.vbs : Failed

or with test.cmd in oemscan.ini;

Matched: SM

Running: test.cmd : Failed

Link to comment
Share on other sites

duh... :whistle:

remove the /d switch

The /d just makes oemscan show you what happens...right?

Or does it change how it works...... :}

Update

I tried it just running oemscan.exe...........success :thumbup

I have more grey hair now :blushing:

Thanks to the ones who helped me!!

Edited by Floppy
Link to comment
Share on other sites

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 em

TheUni

Link to comment
Share on other sites

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 em

TheUni

I have done Pro&Home on; DELL,HP,Compaq and FS--->No Problem :thumbup

Edited by Floppy
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...