FreeStyler Posted January 3, 2007 Posted January 3, 2007 hi! sorry for the bother, i think i got it: would it be the following files: oembios.bin, oembios.cat, oembios.dat, oembios.sig? thanks! Yes, that are the files needed (together with a OEM SLP key)
FreeStyler Posted January 3, 2007 Posted January 3, 2007 (edited) I was worried the method I use to disable SFC in XP wouldn’t work in W2K3 however when I tested it with W2K3 R2 Standard Edition Service Pack 2 (Volume) it passed with flying colors. The method I use disables SFC for exactly 1 minute on specific files. Is it possible more then 1 minute elapsed between copying over the files and importing the .CAT file?Could you test it on more systems and get back to me if you run into SFC errors? Perhaps I should import the .CAT file first.Think it had something to do with the fact it elapsed the 1 minute boundry,Reinstalled the Virtual PC exactly the same as yesterday,only this time without the error (running oemscan and grabbing the oembios files over a VM shared folder)I'm also doing a test install on Virtual Server 2005 right now, results will folow laterUPDATE: Installed just fine as wellAlso with OEMScan integrated into setup...using CMDLINES.TXT setup succeeded Edited January 3, 2007 by FreeStyler
Bilou_Gateux Posted January 3, 2007 Posted January 3, 2007 Done some check under my favourite virtualization software:http://www.msfn.org/board/index.php?s=&...st&p=597316launching @T39%dospath%\$oem$\oemscan /dOEMBIOS Scanner v1.4.0 by Jeremy (xehqter)Reading BIOS MemoryMatched: FUJITSU SIEMENSChecking Authenticity of OEMBIOS filesi get a blinking cursor and oemscan never finish copying oembios.* files.The same method with a XP install works flawlessy.
FreeStyler Posted January 3, 2007 Posted January 3, 2007 %dospath%\$oem$\oemscan /dDid you wait long enough for the files to be copied....sometimes it can take a whileI asume you are aware the /d switch forces oemscan to do a dry run (running it without actually copy the files)
Kiki Burgh Posted January 4, 2007 Posted January 4, 2007 Yes, that are the files needed (together with a OEM SLP key)thanks for the confirmation FreeStyler! another inquiry though, would Siginet's app: [Release] OEMScan v1.3 RVM Integrator Addons be the same as this one ... although it shows here OEMScan v1.4.0 already? it shows too in the initial thread the changes made from v1.3 up? thanks again!
FreeStyler Posted January 4, 2007 Posted January 4, 2007 another inquiry though, would Siginet's app: [Release] OEMScan v1.3 RVM Integrator Addons be the same as this one ... although it shows here OEMScan v1.4.0 already? it shows too in the initial thread the changes made from v1.3 up? thanks again! Yup, the OEMScan RVM Integrator Addons can be used together with OEMSCAN 1.4.If you use RVM Integrator you can use these (but don't ask suport for it here!)If you don't use RVM Integrator, just go to www.oembios.net and download oembios file sets separetely and read instructions in the OEMSCAN1.4 zip package on how to include them.
Bilou_Gateux Posted January 4, 2007 Posted January 4, 2007 %dospath%\$oem$\oemscan /dDid you wait long enough for the files to be copied....sometimes it can take a whileI asume you are aware the /d switch forces oemscan to do a dry run (running it without actually copy the files)Yes, 10 mn in VMware guest. Not checked on real hardware.Yes, i use 2 commands in my cmd script::: OEMScan%dospath%\$oem$\OEMScan.exe /d >%systemroot%\temp\oemscan.log%dospath%\$oem$\OEMScan.exeUsing this method, i have a log file to debug issues.
FreeStyler Posted January 4, 2007 Posted January 4, 2007 Yes, 10 mn in VMware guest. Not checked on real hardware.Yes, i use 2 commands in my cmd script::: OEMScan%dospath%\$oem$\OEMScan.exe /d >%systemroot%\temp\oemscan.log%dospath%\$oem$\OEMScan.exeUsing this method, i have a log file to debug issues.strangeI've succesfully used a slightly different approach (using CMDLINES.TXT @t13/t12) without problems$OEM$\CMDLINES.TXT[commands]"oemscan.exe"
Bilou_Gateux Posted January 4, 2007 Posted January 4, 2007 strangeI've succesfully used a slightly different approach (using CMDLINES.TXT @t13/t12) without problems@T12 cmdlines.txtit worksOEMBIOS Scanner v1.4.0 by Jeremy (xehqter)Reading BIOS MemoryMatched: FUJITSU SIEMENSChecking Authenticity of OEMBIOS filesOEMBIOS files pass ValidationCopying d:\$oem$\FUJ\OEMBIOS.BIN : SuccessfulCopying C:\WINDOWS\system32\DllCache\OEMBIOS.BIN : SuccessfulCopying d:\$oem$\FUJ\OEMBIOS.SIG : SuccessfulCopying C:\WINDOWS\system32\DllCache\OEMBIOS.SIG : SuccessfulCopying d:\$oem$\FUJ\OEMBIOS.DAT : SuccessfulCopying C:\WINDOWS\system32\DllCache\OEMBIOS.DAT : SuccessfulImporting d:\$oem$\FUJ\OEMBIOS.CAT : Successful
xehqter Posted January 4, 2007 Author Posted January 4, 2007 (edited) launching @T39%dospath%\$oem$\oemscan /d Perhaps windows can't validate against .CAT files @ T39??Released a new version, nothing special, its a minor update Edited January 4, 2007 by xehqter
FreeStyler Posted January 6, 2007 Posted January 6, 2007 (edited) thx for the update... /D actually did copy files afterall ? @xehqter BTW, the latest release is still tagged as beta release...OEMBIOS Scanner v1.4.1 beta by Jeremy (xehqter)Reading BIOS Memory... Edited January 6, 2007 by FreeStyler
xehqter Posted January 6, 2007 Author Posted January 6, 2007 thx for the update... /D actually did copy files afterall ? @xehqter BTW, the latest release is still tagged as beta release...OEMBIOS Scanner v1.4.1 beta by Jeremy (xehqter)Reading BIOS Memory...Good catch, forgot to remove that.. fixed and reuploaded. Yeah, odd, at some point I commented out the check for dry-run when copying files. doh.. coding while tired, bad idea.
Bilou_Gateux Posted January 6, 2007 Posted January 6, 2007 May 1.4.1 fix the issue mentionned in previous post:not been able to complete @T39.
xehqter Posted January 6, 2007 Author Posted January 6, 2007 May 1.4.1 fix the issue mentionned in previous post:not been able to complete @T39.I doubt it but do me a fav and give me a dump with 1.4.1.
Kilyin Posted January 9, 2007 Posted January 9, 2007 (edited) My CD has been working fine on all OEM systems I've tried it with, except for Dells. I know I have the Dell folder setup correctly, I got the product keys directly from a winnt.sif on actual Dell CDs. Anyway, on a Dell everything works according to my log, except the setkey.cmd fails for some reason. If I manually type the same exact key in, Windows setup accepts it and no activation is required. I'm not sure where to begin troubleshooting this. It seems as if everything should in fact work seamlessly, but for some reason Dell's just don't want to cooperate. I don't have the logs in front of me, but on both Dells that failed, everything was successful minus the setkey.cmd, which FAILED. Like I said, other OEM brands, everything works great. The really strange thing about that is I'm using the Dell key for every brand, but the Dells won't take their own key.Setkey.cmd@ECHO OFF for %%i in (C: D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: W: X: Y: Z:) do if exist %%i\WIN51 set CDROM=%%i%CDROM%\OEM\NirCmd.exe inisetval %SystemRoot%\SYSTEM32\$WINNT$.INF "UserData" "ProductKey" "~qXXXXX-XXXXX-XXXXX-XXXXX-XXXXX~q"exitAnyone have any ideas/suggestions on what I can do to debug this? Edited January 9, 2007 by Kilyin
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