Prev: Guess the scam
Next: SP95E10 in France - Heads up.
From: Brownz on 10 Dec 2008 06:59 So I have a batch file that runs perfectly under dos (it applies a set of bios defaults to an AMI bios mainboard). SET PWFILE=PWD1.KEY amiscew.exe /i p6base.cfg<%PWFILE% If not errorlevel 1 goto pass I need to run it under WinPE so converted it to a .cmd file and tweaked : SET PWFILE=PWD1.KEY amiscew.exe /i p6base.cfg<"%PWFILE%" If not errorlevel 1 goto pass All files are present and correct, it works under DOS and pipes in the password that is in PWD1.KEY But under WINPE, the target app (amiscew) doesn't receive the password. I've also tried just piping the text in under WinPE - e.g. amiscew.exe /i p6base.cfg < xx That doesn't work either - do cmd files under WinPE not like piping ?
From: ginge on 10 Dec 2008 07:28 On Wed, 10 Dec 2008 03:59:37 -0800 (PST), Brownz <admin(a)brownz.org> wrote: >So I have a batch file that runs perfectly under dos (it applies a set >of bios defaults to an AMI bios mainboard). > >SET PWFILE=PWD1.KEY >amiscew.exe /i p6base.cfg<%PWFILE% >If not errorlevel 1 goto pass > >I need to run it under WinPE so converted it to a .cmd file and >tweaked : > >SET PWFILE=PWD1.KEY >amiscew.exe /i p6base.cfg<"%PWFILE%" >If not errorlevel 1 goto pass > >All files are present and correct, it works under DOS and pipes in the >password that is in PWD1.KEY > >But under WINPE, the target app (amiscew) doesn't receive the >password. > >I've also tried just piping the text in under WinPE - e.g. >amiscew.exe /i p6base.cfg < xx > >That doesn't work either - do cmd files under WinPE not like piping ? It's something more fundemental than that, Windows PE does not include the �Windows on Windows 32� (WOW32), �Windows on Windows 64� (WOW64), Virtual DOS Machine (VDM), OS/2 or POSIX subsystems... and your dos command would need VDM to run. See if there's a native Windows App that does the same thing as AMISCREW.
From: Brownz on 10 Dec 2008 07:47 On 10 Dec, 12:28, ginge <the.gingeREM...(a)THISgmail.com> wrote: > On Wed, 10 Dec 2008 03:59:37 -0800 (PST), Brownz <ad...(a)brownz.org> > wrote: > > > > > > >So I have a batch file that runs perfectly under dos (it applies a set > >of bios defaults to an AMI bios mainboard). > > >SET PWFILE=PWD1.KEY > >amiscew.exe /i p6base.cfg<%PWFILE% > >If not errorlevel 1 goto pass > > >I need to run it under WinPE so converted it to a .cmd file and > >tweaked : > > >SET PWFILE=PWD1.KEY > >amiscew.exe /i p6base.cfg<"%PWFILE%" > >If not errorlevel 1 goto pass > > >All files are present and correct, it works under DOS and pipes in the > >password that is in PWD1.KEY > > >But under WINPE, the target app (amiscew) doesn't receive the > >password. > > >I've also tried just piping the text in under WinPE - e.g. > >amiscew.exe /i p6base.cfg < xx > > >That doesn't work either - do cmd files under WinPE not like piping ? > > It's something more fundemental than that, Windows PE does not include > the Windows on Windows 32 (WOW32), Windows on Windows 64 (WOW64), > Virtual DOS Machine (VDM), OS/2 or POSIX subsystems... and your dos > command would need VDM to run. > > See if there's a native Windows App that does the same thing as > AMISCREW.- Hide quoted text - > > - Show quoted text - AMISCEW is the windows version..... AMISCE is the DOS version..... doh !
From: fragmented on 10 Dec 2008 15:51 'ginge' wrote...> > On Wed, 10 Dec 2008 03:59:37 -0800 (PST), Brownz <admin(a)brownz.org> > wrote: > > >So I have a batch file that runs perfectly under dos (it applies a set > >of bios defaults to an AMI bios mainboard). > > > >SET PWFILE=PWD1.KEY > >amiscew.exe /i p6base.cfg<%PWFILE% > >If not errorlevel 1 goto pass > > > >I need to run it under WinPE so converted it to a .cmd file and > >tweaked : > > > >SET PWFILE=PWD1.KEY > >amiscew.exe /i p6base.cfg<"%PWFILE%" > >If not errorlevel 1 goto pass > > > >All files are present and correct, it works under DOS and pipes in the > >password that is in PWD1.KEY > > > >But under WINPE, the target app (amiscew) doesn't receive the > >password. > > > >I've also tried just piping the text in under WinPE - e.g. > >amiscew.exe /i p6base.cfg < xx > > > >That doesn't work either - do cmd files under WinPE not like piping ? > > It's something more fundemental than that, Windows PE does not include > the ?Windows on Windows 32? (WOW32), ?Windows on Windows 64? (WOW64), > Virtual DOS Machine (VDM), OS/2 or POSIX subsystems... and your dos > command would need VDM to run. > > See if there's a native Windows App that does the same thing as > AMISCREW. What about BartPE? Can't you tweek the BartPE image so it includes WOW32? -- fragmented
From: Brownz on 11 Dec 2008 09:14
On 10 Dec, 20:51, fragmented <ne...(a)ukrm.co.uk> wrote: > 'ginge' wrote...> > > On Wed, 10 Dec 2008 03:59:37 -0800 (PST), Brownz <ad...(a)brownz.org> > > wrote: > > > >So I have a batch file that runs perfectly under dos (it applies a set > > >of bios defaults to an AMI bios mainboard). > > > >SET PWFILE=PWD1.KEY > > >amiscew.exe /i p6base.cfg<%PWFILE% > > >If not errorlevel 1 goto pass > > > >I need to run it under WinPE so converted it to a .cmd file and > > >tweaked : > > > >SET PWFILE=PWD1.KEY > > >amiscew.exe /i p6base.cfg<"%PWFILE%" > > >If not errorlevel 1 goto pass > > > >All files are present and correct, it works under DOS and pipes in the > > >password that is in PWD1.KEY > > > >But under WINPE, the target app (amiscew) doesn't receive the > > >password. > > > >I've also tried just piping the text in under WinPE - e.g. > > >amiscew.exe /i p6base.cfg < xx > > > >That doesn't work either - do cmd files under WinPE not like piping ? > > > It's something more fundemental than that, Windows PE does not include > > the ?Windows on Windows 32? (WOW32), ?Windows on Windows 64? (WOW64), > > Virtual DOS Machine (VDM), OS/2 or POSIX subsystems... and your dos > > command would need VDM to run. > > > See if there's a native Windows App that does the same thing as > > AMISCREW. > > What about BartPE? Can't you tweek the BartPE image so it includes > WOW32? > > -- > fragmented- Hide quoted text - > > - Show quoted text - Tis WinPE, and the tool is a WinPE version from AMI. It appears WinPE cannot handle console i/o redirects like DOS can. |