ilko_t Posted January 20, 2012 Posted January 20, 2012 ...RUN batch can be downloaded from 1st pagehttp://bbs.wuyou.com/viewthread.php?tid=191301&extra=page%3D1&page=1and more screen shots...The art of grub4dos, part III...
laddanator Posted January 21, 2012 Posted January 21, 2012 RUN batch can be downloaded from 1st pagehttp://bbs.wuyou.com...page%3D1&page=1Will not let me download. Keeps taking me to a "sorry can't download and something about translated forum.
wimb Posted January 21, 2012 Posted January 21, 2012 (edited) Download 0119 RUN.zip - http://bbs.wuyou.com/attachment.php?aid=136156and grub4dos-0.4.5c-2012-01-17.7z from http://code.google.com/p/grub4dos-chenall/downloads/list Edited January 21, 2012 by wimb
laddanator Posted January 21, 2012 Posted January 21, 2012 (edited) Download 0119 RUN.zip - http://bbs.wuyou.com....php?aid=136156Thanks, wimb, but still cannot download. Below is the exact error I am gettingI'm sorry, please do not download from external link attachments in this forum. I got the new grub4dos. I check that site once a week. Them new grldr rolling out faster these day's. Edited January 21, 2012 by laddanator
wimb Posted January 21, 2012 Posted January 21, 2012 (edited) Thanks, wimb, but still cannot download. Below is the exact error I am gettingThen use R-mouse to copy the link from my post (your quote link is wrong and has ......) and put as address (outside MSFN) in your browser .....For me it is working, it is a direct download link.Otherwise wait few days, next week I will add it to IMG_XP package ....http://www.911cd.net/forums//index.php?showtopic=23553 Edited January 21, 2012 by wimb
laddanator Posted January 21, 2012 Posted January 21, 2012 Ok finally got it to work. Was using FireFox and had to use IE9 (weird). Extracted the file and the RUN has no file extension.
maanu Posted January 21, 2012 Posted January 21, 2012 (edited) make sure RUN is in BOOT/GRUB directory path.boot from grub4dos. press C for command line, type RUN , enter you will be in RUN mode. it is a batch , right click it , and open with notepad2 or notepad ++or you can use the following to set its path,.my menu.lst sample for my NativePE.debug offcheckrange 0x21 read 0x8280 && pxe keepgraphicsmode -1 640terminal --font-spacing=0:3color normal=31 highlight=0x75 helptext=0x1D heading=0x0A standard=0x0F border=0x00splashimage /SRNP/GRUB/SNOW.GZset com=/SRNP/GRUB/cat --length=0 %?_BOOT%%com%RUN && set root=%?_BOOT% ! cat --length=0 %@root%%com%RUN && set root=%@root% ! find --set-root %com%RUNset com= && set root= && command --set-path=%root%%com%default 03title User Menu By Maanu \ncleartitle [01] intoXicator's NativePEmap /SRNP/NATIVE.ISO (0xff)map --hookchainloader (0xff) || chainloader (0xff)/I386/SETUPLDR.BINtitle [02] Boot Into NT6x command RUN /bootmgrtitle [03] Boot Into NT5x command RUN /ntldr Edited January 21, 2012 by maanu
maanu Posted January 21, 2012 Posted January 21, 2012 (edited) @ cdob is it possible , that even though setupORG.exe is copied OK to system32 , and renamed to Setup.exe by your setup.cmd . but still it is complaining ,at gui mode , " setupORG.exe not found "i dont understand how it could happen. i booted from PE. and checked the system32 ,there is setup.exe there (as renamed by your batch during setup ) here is presetup.log presetup log Sun 01/22/2012 2:46:38.28 search ISO file "C:\Inst\XP_RAM.ISO"search ISO file "D:\Inst\XP_RAM.ISO"search ISO file "E:\Inst\XP_RAM.ISO"search ISO file "F:\Inst\XP_RAM.ISO"search ISO file "G:\Inst\XP_RAM.ISO"search ISO file "H:\Inst\XP_RAM.ISO"found ISOfile H:\Inst\XP_RAM.ISOmount ISOfile H:\Inst\XP_RAM.ISO Volume in drive V is CRMEVOL_EN Volume Serial Number is 9FC6-5DF7 Directory of V:\10/29/2011 12:00 PM <DIR> $OEM$10/29/2011 12:00 PM <DIR> I38610/29/2011 12:00 PM 10 WIN5110/29/2011 12:00 PM 10 WIN51IA10/29/2011 12:00 PM 10 WIN51IA.SP2 3 File(s) 30 bytes 2 Dir(s) 0 bytes freeadjust $winnt$.inf: sourcepath = "\device\ImDisk0\" rename $winnt$.inf Volume in drive I has no label. Volume Serial Number is ECED-2A0C Directory of I:\WINDOWS\system3209/05/2009 01:46 PM 6,144 setup.exe01/24/2010 05:05 AM 28,672 setuporg.exe 2 File(s) 34,816 bytes 0 Dir(s) 50,152,587,264 bytes freecall presetup.cmd end presetup.cmd run setup CmdLine: setup -newsetup - Sun 01/22/2012 2:46:44.04edit :disregard above message , i was in "sleep" mode when selecting the WRONG setup.exe .just saw the real setup.ex_ , after extracting ,in version , it saysWindows NT Setup Executablewhich means , it is real deal. on a side note.is it possible to add both setupORG.EXE ( XP and 2K3 ) in same FLOPPY IMAGE ?like Having 2 folder XP /setupORG.EXE 2k3/setupORG.EXEthis way , we can have one floppy image for both ISO's. ? Edited January 21, 2012 by maanu
laddanator Posted January 22, 2012 Posted January 22, 2012 (edited) I been test installing XP ISO using the menu below with path tweaks and suchtitle Setup Windows XP from ISO : \nBoot once from USBset myISO=/images/XP_PRO_HP_OEM.iso#ilko_t http://www.msfn.org/...post__p__988093/boot/shifthd.batfind --set-root --devices=h %myISO%map %myISO% (222)map --mem /images/FIRADISK.IMG (fd0)#map --mem /images/FIRADISK.IMG (fd1)map --rehook#chenall's ntbootcat --locate=###### --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error..set offset=%?%set fira.opt=cdrom,vmem=find:%myISO%;write --offset=%offset% (fd0)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\ncat --skip=%offset% --locate=/ --replace=\\ (fd0)/TXTSETUP.OEMcat (fd0)/TXTSETUP.OEMpause press a keyroot (222)chainloader (222)/I386/SETUPLDR.BINAnd yesterday I started getting this errorUploaded with ImageShack.usWhat I did was make two fresh HOME.ISO and TPC.ISO because I had altered my other Home and TPC so much trying to get this and that to work with firadisk (slipstream the friadisk drivers with nlite but was not needed so instead I made fresh ISO). I slipstream latest updates and DriverPacks as usually. Install both through VM no problem, then made sure neither were fragmented after copying to USB drive. The error in the pic is usually a bad burn or CD Drive. So after I got the error, I burned both ISO to separate DVD RW and both installed fine and no errors. I always use UltraISO to make my ISO. Not sure if the firadisk emulation is getting corrupt some how. I did finally get the HOME.ISO to install with just firadisk but not sure what I did to do so. The TPC.ISO is still giving me the error in the pic but will install fine any other way including cdobs, IMA v05UPDATESo today I am able to load my TPC.ISO with no errors using just firadisk. I really think all the testing and mapping stuff to memory causes this error. Maybe some left over stuff stored in memory and until the memory is cleared, you may hit random errors Edited January 22, 2012 by laddanator
cdob Posted January 22, 2012 Author Posted January 22, 2012 is it possible to add both setupORG.EXE ( XP and 2K3 ) in same FLOPPY IMAGE ?It's prepared already. Txtsetup.oem contains alreadyse03_32 = "2003 setup files x86", \txtsetup.oem, \setup\I386_03\dll = setup32, setuporg.exeAdd a 2003 setup.exe as \setup\I386_03\setupORG.exeExamle: floppy image mounted in RAM as fd0 and fd1:#patch txtsetup.oem, use 2003 setuporg.execat --locate=setuporg.exe --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error..set /a offset=%?% - 9write --offset=%offset% (fd0)/TXTSETUP.OEM se03_32dd if=(fd0)/TXTSETUP.OEM of=(fd1)/TXTSETUP.OEMcat (fd1)/TXTSETUP.OEMpause press a keyThank's for the RUN batch by Sratif, it's overwhelming. Grub4dos at max features.Did you solve missing floppy drive at 2003 install? Did you edited the ISO file? What about adding firadisk to ISO file? A floppy image is obsolete that way.The TPC.ISO is still giving me the error in the pic but will install fine any other way including cdobs, IMA v05So today I am able to load my TPC.ISO with no errors using just firadisk.Missing asms indicates (virtual) CD drive is missing.Could be a timing problem. USB drive has to be available first. Without a available USB drive, there is no ISO file. Firadisk can't find a ISO file. Different hardware, different USB port, file location, BIOS may get timing difficulties.IMA v05 used two drivers and automatic CriticalDeviceDatabase fix. The log file would be nice.I'm about IMA v06 at firadisk only and automatic CriticalDeviceDatabase fix. However no special hardware to test.
laddanator Posted January 22, 2012 Posted January 22, 2012 (edited) Thank's for the RUN batch by Sratif, it's overwhelming. Grub4dos at max features.Tried to open RUN batch with Notepad++ and noting is readable, that's why I was wondering if I downloaded the right thing or if the download was brokenI'm about IMA v06 at firadisk only and automatic CriticalDeviceDatabase fix. However no special hardware to test. What do you need in order to test, may can help?Could be a timing problem. USB drive has to be available first. Without a available USB drive, there is no ISO file. Firadisk can't find a ISO file.Different hardware, different USB port, file location, BIOS may get timing difficulties.Would you say using IMA V5 with firadisk is "safer" than just using firadisk?What about adding firadisk to ISO file? A floppy image is obsolete that way.Like this idea and have tried this but how would XP load from txtsetup.oem if it's not in a 'floppy"Do you mean the actually ISO or creating a small ISO with firadisk stuff?I slipstream the firadisk drivers into my XP source but could never get registry entry to find ISO on reboot to work. Edited January 22, 2012 by laddanator
cdob Posted January 22, 2012 Author Posted January 22, 2012 Tried to open RUN batch with7-zip to expand the gzipped file. Grub4dos does read gz compressed files.What do you need in order to test, may can help?A strange USB BIOS. Certain Dell are famous. Can you list used hardware?Would you say using IMA V5 with firadisk is "safer" than just using firadisk?False question. I've no idea about a "safer" approach. A additional code may cause a additional errors.A plain approach may be "safer", but fail at some machines.Plain firaddisk single USB boot will fail at half broken BIOS. These machines are seldom.Or the other way round: plain firaddisk single USB boot works at almost all machines.
laddanator Posted January 22, 2012 Posted January 22, 2012 (edited) Can you list used hardware?When I get to work tomorrow, I will post what Dell Machines we havePlain firaddisk single USB boot will fail at half broken BIOS. These machines are seldom.Or the other way round: plain firaddisk single USB boot works at almost all machines. I do like the idea of using one drive and I kinda threw this together for testing to delete firadisk drivers at first login. Very simple but has worked so far(echo. &echo XPSetup Log %date% %time% &echo.)>> %systemdrive%\XPSetup.logif not exist %WinDir%\system32\drivers\firadisk.sys goto Barn;(echo. Firadisk Driver Found.)>> %systemdrive%\XPSetup.log ;devcon remove *\firadisk;IF %ERRORLEVEL% == 0 (echo. Firadisk Driver Removed 1)>> %systemdrive%\XPSetup.log ;del %WinDir%\system32\drivers\firadi*.sys;IF %ERRORLEVEL% == 0 (echo. Firadisk Driver Removed 2)>> %systemdrive%\XPSetup.log ;REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Firadisk" /VA /f ;IF %ERRORLEVEL% == 0 (echo. Firadisk Value "services" was Deleted)>> %systemdrive%\XPSetup.log;REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk" /VA /f;IF %ERRORLEVEL% == 0 (echo. Firadisk Value "Control" was Deleted)>> %systemdrive%\XPSetup.log;RD /S /Q %WinDir%\OemDir;(echo. OemDir Removed)>> %systemdrive%\XPSetup.log But I like the idea of not having to map a floppy but haven't figured a way around this? How to get XP to find the txtsetup.oem file is the issue7-zip to expand the gzipped file. Grub4dos does read gz compressed files.Didn't realize this was a gz file...no file extension and by the way I notice the new 7zip doesn't do gz compression anymore Edited January 22, 2012 by laddanator
cdob Posted January 23, 2012 Author Posted January 23, 2012 But I like the idea of not having to map a floppyThere are different approaches. Use nlite to integrarte firadisk.Or use Or use another approach:Copy firadisk.sys and firadisk.inf to directory \I386\Edit \I386\TXTSETUP.SIF[SourceDisksFiles]firadisk.sys = 1,,,,,,,4,0,0firadisk.inf = 1,,,,,,,20,0,0;firadisk.inf edited: CopyFiles excluded:;[FiraDiskDevice.NTx86];;CopyFiles=CopyFilesFiraDisk_x86[BootBusExtenders.Load]firadisk = firadisk.sys[BootBusExtenders]FiraDisk = "FiraDisk Virtual Disk",files.none,firadiskAdd a \I386\MIGRATE.INF[Version]Signature = "$Windows NT$"[Addreg];search ISO imageHKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso";####################################################################################Edit \I386\HIVESYS.INF [AddReg];search ISO imageHKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso";####################################################################################menu.lsttitle Setup Windows XP from ISO: \nfiradisk integrated in ISO imageset myISO=/images/winsetup.iso#ilko_t http://www.msfn.org/board/topic/149675-install-xp-from-a-iso-file/page__view__findpost__p__988093/boot/shifthd.batfind --set-root --devices=h %myISO%map %myISO% (222)map --hookroot (222)chainloader (222)/I386/SETUPLDR.BINThis assumes a USB boot friendly BIOS. At a strange BIOS feel free to include USB settings from Post #58
maanu Posted January 24, 2012 Posted January 24, 2012 It's prepared already. Txtsetup.oem contains alreadyse03_32 = "2003 setup files x86", \txtsetup.oem, \setup\I386_03\dll = setup32, setuporg.exeAdd a 2003 setup.exe as \setup\I386_03\setupORG.exeExamle: floppy image mounted in RAM as fd0 and fd1:#patch txtsetup.oem, use 2003 setuporg.execat --locate=setuporg.exe --number=1 (fd0)/TXTSETUP.OEM > nul || call :error firadisk.img file error..set /a offset=%?% - 9write --offset=%offset% (fd0)/TXTSETUP.OEM se03_32dd if=(fd0)/TXTSETUP.OEM of=(fd1)/TXTSETUP.OEMcat (fd1)/TXTSETUP.OEMpause press a keymeans i will simply add a folder i386_03 in IMA file beside I386 folder, and txtsetup will look in I386_03 folder ? i suppose there is no way to do this without using your above TSTSETUP Patch ?because now i use your IMA file with RUN . and this way , i am afraid i will have to use another IMA file for 2003 ISO. Did you solve missing floppy drive at 2003 install? Did you edited the ISO file? What about adding firadisk to ISO file? A floppy image is obsolete that way. i used following entry , and firadisk copy error gone.map --mem (md)0x800+4 (99)map --mem /Inst/XP_INST.IMA (fd1)map --mem (md)0x6000+800 (fd0)map /Inst/XP_RAM.ISO (222)map --hookdd if=(fd1) of=(fd0) count=1write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO ;\n\0rootnoverify (222)chainloader (222)/I386/SETUPLDR.BINi prefer NOT to edit the iso. and everything from IMA menu.lst as you prefer i suppose.by the way , copy error also not appear with RUN file. my usage of RUN ,with your default ISO path./title RUN of SRATIF with CDOB IMAset usrpath=/INST/command /INST/RUN --fira:XP_INST.IMA iso=XP_RAM.ISOif i want to change iso path , i should only edit the isoimage.ini file ?i strongly recommend to use RUN in your next IMA.
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