23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
SignIn

CreateAccount

reboot.pro Bootmethods&tools BootfromUSB/Bootanywhere TheSyslinuxProject

Chainloading AUTOEXEC/COMMAND.COM?
Startedbydelicatepc,Jul23201005:08PM

Page1of2
Posted23July201005:08PM

delicatepc

HiFolks,
Delloffersseveraldiagnosticpackages(eachonesupportsadifferentsetofmachines).FormyquestionIwilluse
CWA1384A0thatcanbefoundhere:LINK(http://support.dell.com/support/downloads/download.aspx?
c=us&cs=555&l=en&s=biz&releaseid=R271134&SystemID=LAT_E6400&servicetag=&os=W732&osl=en&deviceid=3841&
devlib=0&typecnt=0&vercnt=4&catid=1&impid=1&formatcnt=0&libid=13&typeid=1&dateid=1&formatid=1&source=
1&fileid=400679)
Once"installed"theutilityoffersauseranoptiontoCreateISO,CreateHDD/Floppyimageofthediagnostics,andor
installittoaUSBstick.
TheHDD/FloppyimageworkswellwithMEMDISKonmostofthedellmachines.Howevercertainmodels(DellE6400for
example)hangwhenattemptingtoruntheDRMKkernelthattheDellDiagnosticsuse(BIOSisuptodateonthese
machines).UsingSyslinux4.01issuehasbeensincethesyslinux3.8xdaysmaybeevenbeforethen.
Somynextstepistousethe"InstalltoUSBstick"option.ThiscopiestheDelldiagnosticsfilestoaUSBstickanduses
AUTOEXEC.battokickoffthediagnostics.AUTOEXEC.batloadsallthediagnosticsintotheRAM.
AZIPPEDversionoftheUSBstickcontentscanbefoundhere(4MB):ZIPPEDLINK(http://www.mediafire.com/?
2l2vc949rp4ubn2)
WiththatbeingexplainedisitpossibletochainloadtheAUTOEXEC.bat(orisitCOMMAND.COMwewantto
chainload?)?
Thankyou,
dpc
Posted23July201006:15PM

WonkotheSane

delicatepc,onJul232010,07:08PM,said:
WiththatbeingexplainedisitpossibletochainloadtheAUTOEXEC.bat(orisitCOMMAND.COMwewanttochainload?)?

NO.
Youdon't"chainload"ANYfile,youonly"chainload"Systemfiles(orkernels),inthecaseofDOS,itisIO.SYS,
COMMAND.COMbeingtheCommandInterpreter,andAUTOEXEC.BATasimplebatchfilewhichisexecuted
autoamtically,aswellasCONFIG.SYSatboottime.
SowhatyouwantistohaveaMENUinsideAutoexec.batthatallowsyoutochoosetheparticularmachine(andthe
particularsetofcommandsyouneedonthatmachine),or,inotherwords,youhaveto"puttogether"thevarious
autoexec.bat's(andmaybeconfig.sys)ofthedifferentversionsoftheutilityfiles.
Youhaveonlyone:
IO.SYS
MSDOS:SYS
COMMAND.COM
andyourundifferentsetofcommandsdependingonthechoicesyoumakeinthemenu.

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

1/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
Someexamples:
http://www.shiningst...ulticonfig.html(http://www.shiningstar.net/geek/html/multiconfig.html)
http://www.mindsprin...iman/Bootup.htm(http://www.mindspring.com/~dmerriman/Bootup.htm)
http://httpserver.c...mcfet/menu.html(http://httpserver.carleton.ca/~dmcfet/menu.html)
http://www.symantec....dosmenusystem(http://www.symantec.com/connect/articles/simpledsdosmenusystem)
ThishasnothingtodowithSyslinuxandalottodowithDOS.
Youcanuseamenusystem,like:
http://surf.to/AccessDosMenu(http://surf.to/AccessDosMenu)
more:
http://www.bttrsoft...eesoft/menu.htm(http://www.bttrsoftware.de/freesoft/menu.htm)
Youcananywaytryusinggrub4dosinsteadofmemdisk,tomaptheimages,butIdoubtthatitwillworkwherememdisk
failed.

Wonko
Posted23July201008:19PM

delicatepc

ThankyouforthereplyWonko.Ithinkitmayhavewent*woosh*overmyhead*
Iwillbehonestitdoesn'tseemmakesensetomeatthemoment.Justnotclickinginmyhead.
Hereismylogic.
1.CreateMenuentryinsyslinuxforacertainDellDiagversion:
LABEL
MENULABELDellDiagnosticsCW1384A0ExtractedVersion

COM32/boot/syslinux/chain.c32

APPENDfsntldr=/cw1384A0/IO.SYS

2.CHAIN.C32loadstheDOS??environment.LoadsupCommand.com/config.sysandthengoestoAUTOEXEC.batto
execute....
3.AUTOEXEC.batisprettysimpleitjustsendsallthefilesintoRAM(noneedformenu/machineselectionhaveonlyone
setofinstructionsIwantittorunnamelythedelldiagnostic).
4.TheDellDiagnosticsappear.
IAmguessing.....itappearstheDellusesacustomversionofIO.SYS?calledDellRMK.BINorDellBIO.bin...seethe
attachedziparchivethereisnoIO.SYSthere.....
Doesthismakesense?
thankyou,
dpc
Posted23July201010:34PM

Icecube

Didyoutrytoadd'raw','bigraw'or'int'totheAPPENDline?
IpartlysucceededinbootingDELLBIO.BINfromSYSLINUX:
LABELchain_DELLBIO
MENULABELBootDELLBIO.BINwithchain.c32
COM32chain.c32
APPENDfreedos=/DELLBIO.BIN

Youcanalsouse:

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

2/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
APPENDmsdos=/DELLBIO.BIN

Butitwillhangatthisstage:
LoadingDRMXV8.00...

Can&#39tloadkernelfile

ProbablyDELLBIO.BINexpectstheDELLRMK.BINfileatacertainlocationintheFATtable,butinstallingSYSLINUXto
thisdiskimage,willmovesomefilesaroundintheFATtable.
Tryingtochainloadthepartitionbootsector(C:\Dell\Drivers\R271134\BOOT\DRMK12.BS)whichnormallyloads
DELLBIO.BIN,failswhenSyslinuxisinstalled:==>returns'DISKerror'
Posted24July201012:02PM

WonkotheSane

Well,the.isoworksallrightingrub4dosunderQemu.

Quote
titleDellR271134iso
mapmem(hd0,0)/dell/drivers/R271134/diags.iso(hd32)
maphook
root(hd32)
chainloader(hd32)

Aswellthediskimage:
Quote
titleDellR271134img
mapmem(hd0,0)/dell/drivers/R271134/diags.img(hd1)
maphook
root(hd1,0)
chainloader+1

Wonko
Posted24July201001:26PM

Icecube

@WonkotheSane
ItworkswithMEMDISKtooinqemu.
Itonlyseemstofailonsomemodels.
Posted24July201001:44PM

WonkotheSane

Icecube,onJul242010,03:26PM,said:
@WonkotheSane
ItworkswithMEMDISKtooinqemu.
Itonlyseemstofailonsomemodels.

Sure.
IjustpostedwhatworksonthewhateverIcantestitin.
Ialsopreviouslyposted:
WonkotheSane,onJul232010,08:15PM,said:
Youcananywaytryusinggrub4dosinsteadofmemdisk,tomaptheimages,butIdoubtthatitwillworkwherememdiskfailed.

Ialsoalreadypostedasuggestionaboutapossibleworkaroundtousemultipleversionsoftheutilitiesonthesame"flat"

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

3/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
bootableUSBstick,(butit"wooshed"overtheheadoftheOP

).

Thusthoughtthatmaybegivingexplicitlythepossiblegrub4dosentriesmaynot"whooshover"(butofcoursecannotsayif
itwillwork).
What

isthepoint?

Wonko
Posted27July201002:51PM

delicatepc

WonkotheSane,onJul242010,01:44PM,said:
Ialsoalreadypostedasuggestionaboutapossibleworkaroundtousemultipleversionsoftheutilitiesonthesame"flat"bootableUSBstick,(butit
"wooshed"overtheheadoftheOP

Iseewhatyoumeannow.CreateaNonsyslinuxUSBstickandthencreateamenusystemtoaccessvariousdell
diagnosticsinnativeform.Allthingsconsiderednotabadideabutthatmeanstwousbsticks

>

Thatiscorrectitfailstoloadoncertainmodelmachinesonly(DellE6400forexamplehassomeissues).
Icecube:Ihavealsohadjustaboutthesameluck.endupwith"CannotlocateKernelfile"ora"Cannotdividebyzero"and
similarerrorwhetherrawbigrawisoorint.
Mightneedadellbiospecifichackinsyslinuxtomakeitworkproperly....
thankyou,
dpc
Posted27July201003:12PM

Icecube

@delicatepc
CanyoutellonwhichexactPCswithwhichBIOSversionstheimagedoesn'twork?
TrywiththelastMEMDISKversion(4.02).
Tryallentriesinthesyslinux.cfgandalsotrytoboottheimagewithgrub4dosandtellmewhatworks/doesn'twork.
Contentsofsyslinux.cfg:
UImenu.c32

LABELdelldiag1
MENULABELDELLDiagnostics&#40normal&#41
LINUXmemdisk
INITRDdiags.img

LABELdelldiag2
MENULABELDELLDiagnostics&#40raw&#41
LINUXmemdisk
INITRDdiags.img
APPENDraw

LABELdelldiag3
MENULABELDELLDiagnostics&#40bigraw&#41
LINUXmemdisk

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

4/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
INITRDdiags.img
APPENDbigraw

LABELdelldiag4
MENULABELDELLDiagnostics&#40int&#41
LINUXmemdisk
INITRDdiags.img
APPENDint

LABELgrub4dos
MENULABELBootgrub4dos
COM32chain.c32
APPENDfsgrldr=grldr

Contentsofmenu.lst:
titleDELLDiagnostics
map&#40hd0&#41&#40hd1&#41
mapmem/diags.img&#40hd0&#41
maphook
root&#40hd0,0&#41
chainloader&#40&#41+1

Posted27July201003:15PM

delicatepc

IwilltrywhenIgetachancebutitmaybeawhileigetachanceeveryonceinawhile.
thankyou,
dpc
Posted27July201003:32PM

WonkotheSane

delicatepc,onJul272010,04:51PM,said:
Iseewhatyoumeannow.CreateaNonsyslinuxUSBstickandthencreateamenusystemtoaccessvariousdelldiagnosticsinnativeform.Allthings
considerednotabadideabutthatmeanstwousbsticks

>

Whytwo?
Syslinuxorgrub4doscanlivetogetherwiththe"DOSbased"menusystem.

Wonko
Posted27July201003:34PM

delicatepc

Howdoyouloadoneortheother?Iassumesyslinux/grubwouldbethebootloadercorrect?Sothenyouwouldhavean
entrysaying"DOSMode"?
Thankyou,
dpc
WonkotheSane

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

Posted27July201003:46PM

5/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
delicatepc,onJul272010,05:34PM,said:
Sothenyouwouldhaveanentrysaying"DOSMode"?

Yep.
That'sexactlytheideaofabootloader/bootmanager,allowtoloadandbootseveraldifferentOperatingSystems.
WhatyouwillhavetotryisifitispossibletodirectlychainloadtheDELL.sysfileorifyouwillneedan"intermediate"
bootsector,buttheDellutilityalreadyhasthem"extracted"soitwillbeeasytomakeoneforyourstickinsertingthe
specificDATA.

Wonko
Posted27July201003:49PM

delicatepc

Icecube,onJul232010,10:34PM,said:
IpartlysucceededinbootingDELLBIO.BINfromSYSLINUX:

LABELchain_DELLBIO
MENULABELBootDELLBIO.BINwithchain.c32
COM32chain.c32
APPENDfreedos=/DELLBIO.BIN
Youcanalsouse:

APPENDmsdos=/DELLBIO.BIN
Butitwillhangatthisstage:

LoadingDRMXV8.00...

Can&#39tloadkernelfile
ProbablyDELLBIO.BINexpectstheDELLRMK.BINfileatacertainlocationintheFATtable,butinstallingSYSLINUXtothisdiskimage,willmove
somefilesaroundintheFATtable.
Tryingtochainloadthepartitionbootsector(C:\Dell\Drivers\R271134\BOOT\DRMK12.BS)whichnormallyloadsDELLBIO.BIN,failswhen
Syslinuxisinstalled:==>returns'DISKerror'

ItlookslikeIcecubeattemptedthisapproachbuttheDell.sysfilewasnotplayingnice.Likelysomeoddhackedaround
solutioninthedell.sysfile....
thankyou,
dpc
Posted27July201004:41PM

WonkotheSane

Yep,butthetestsshouldbemadeontheactualDELLmachines,ifbothsyslinux/memdiskandgrub4dospostedmethods
fail,thenyoucanchainloadthebootsector.
Easy:
installtoaUSBstick
createabackupcopythebootsectorofthestick,say"dosstick.bss"
installsyslinux(orgrub4dos,orboth)

Addanentryinsyslinux.cfg:
Quote
labelDELLDOSMode
kerneldosstick.bss

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

6/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
oringrub4dos.lst
Quote
titleDELLDOSMode
chainloaderdosstick.bss

Wonko
Posted27July201004:59PM

Icecube

LABELchain_DELLBIO
MENULABELBootDELLBIO.BINwithchain.c32
COM32chain.c32
APPENDfreedos=/DELLBIO.BIN

ForthisapproachIinstalledSyslinux4.02totheoriginalDELLDiagnosticsimage(diags.img).diags.imgisaharddisk
image,withaFAT16formattedpartition(AFAIremember).DELLBIO.BINcontainsthestringD
DELLBIO.BINcontainsthefollowingstrings(deletedsomestringsthatarecompletelyinrelevant):
Quote
RealModeKernel
CONB
AUXT
PRN
CLOCK$
COM1
COM2
LPT1
UnlabeledFAT12W2
Insertdiskettefordrive
:andstrikeanykeywhenready...
Divisionbyzeroat????:????
LoadingDRMKV8.00...
<carry>setreadingMBRondisk
status=
Systemhalted
PROTMAN$
DELLRMKBIN#
A:/P
VDISK3.3
CONFIG.SYS
COUNTRY
SHELL
LASTDRIVE
HILASTDRIVE
BREAK
BUFFERS
HIBUFFERS
FCBS
HIFCBS
FILES
HIFILES
STACKS
HISTACKS
FASTOPEN
DRIVPARM
HISTORY
INSTALL
HIINSTALL
INSTALLLAST
HIINSTALLLAST
DOSDATA
DPBS
XBDA
SWITCHES
DEVICE
HIDEVICE
CHAIN
GOTO
GOSUB

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

7/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
RETURN
CPOS
TIMEOUT
SWITCH
ONERROR
ECHO
EXIT
ERROR
GETKEY
YESCHAR
DEBLOCK
NUMLOCK
BOOTNEXT
QUIET
($)?$
$/L:
SIZE
HIGH
NOUMB
InvalidcommandinCONFIG.SYSfile$
Badormissingfile$
InvalidSHELLfilename$
InvalidLASTDRIVEcharacter(useA..Z)$
InvalidBREAKswitch(useONorOFF)$
InvalidQUIETswitch(useONorOFF)$
Invalidnumberofbuffers$
Invalidnumberoffiles(use5..255)
InvalidnumberofFCBS
InvalidnumberofFASTOPENentries(use128..32768)
InvalidormissingDRIVPARMparameters,usage:
DRIVPARM=/D:d[/C][/F:f][/H:h][/N][/S:s][/T:t]
InvalidHISTORYparameters,usage:
HISTORY=ON|OFF[,nnn[,ON|OFF]]
Invalidcountrycode$
Badormissingcommandinterpreter
Pleaseenteravalidfilename
Can'tloadkernelfile
DRMK
A:\COMMAND.COM

Posted27July201005:51PM

WonkotheSane

Yes,itseemslikesomecheckisperformedontheactualbootsectororfilesystem.
Anyway,againinQEMU,ifISYSaDOS7.1thetestprogramseemslikerunningnormallyusing"chainloader/io.sys".
Onthesamemodifiedimagechainloadingthebootsectorcopyfails.
BUTonlyreplacingthebootsectorfromtheSYSedimageonthe"untouchedone"itworkschainloadingthe(original)
savedbootsectorcopy.
So,thebootsectorapproachshouldwork,unlesssyslinuxchangessomethingelse(Iamnotfamiliarwithit)duringinstall.
Intheworstcaseonecaninstallgrub4dostotheMBR(+hiddensectors),leavingthebootsectorandsystemfilesplacement
untouched.

Wonko
Posted27July201006:59PM

Icecube

ItriedwiththeFreeDOSkernel(kernel.sys)before,butitdidn'twork,becauseIforgottoreplacecommand.comwiththe
FreeDOSversiontoo.
InLinux,youcancreatethisimagewiththefollowingcommands:
Youcansavethepartitionbootsectorofthediags.imgdiskimageifyouwant
ddif=/dellsyslinux/diagssyslinux.imgof=/dellsyslinux/diags.bsskip=63bs=512count=1

InstallSyslinuxtothefirstparitioninsidethediags.imgharddiskimage:

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

8/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
./syslinux4.02/mtools/syslinuxinstalloffset32256./dellsyslinux/diagssyslinux.img

Createoreditthefile.mtoolsrcformanipulatingtheharddiskimagewithmtools:
drivex&#58file=&#34/home/icecube/dellsyslinux/diagssyslinux.img&#34partition=1

YoucancreateaFreeDOSbasedfloppyoraMSDOSbasedfloppy.
Createthesyslinux.cfgfile(FreeDOSbasedfloppy):
DEFAULTdelldiags

LABELdelldiags
COM32chain.c32
APPENDswapfreedos=/kernel.sys

Createthesyslinux.cfgfile(MSDOSbasedfloppy):
DEFAULTdelldiags

LABELdelldiags
COM32chain.c32
APPENDswapmsdos=/io.sys

GetthenecessaryFreeDOSfiles:kernel.sys,command.comandmaybehimem.sys.
Copyallneededfiles(chain.c32,syslinux.cfg,kernel.sys,command.comandmaybehimem.sys)insidethedisk
imagewithmtools:
mcopy./syslinux4.02/com32/modules/chain.c32x&#58
mcopy./dellsyslinux/syslinux.cfgx&#58
mcopy./dellsyslinux/kernel.sysx&#58
mcopy./dellsyslinux/command.comx&#58
mcopy./dellsyslinux/himem.sysx&#58

GetnecessaryMSDOSfiles:io.sys,maybecommand.comandmaybehimem.sys
Copyallneededfiles(chain.c32,syslinux.cfg,io.sys,maybecommand.comandmaybehimem.sys)insidethedisk
imagewithmtools:
mcopy./syslinux4.02/com32/modules/chain.c32x&#58
mcopy./dellsyslinux/syslinux.cfgx&#58
mcopy./dellsyslinux/io.sysx&#58
mcopy./dellsyslinux/command.comx&#58
mcopy./dellsyslinux/himem.sysx&#58

Forboth:
Youcanremovetheunneededdellbio.binfile,ifyouwant:
mdelx&#58dellbio.bin

YoucanalsoaddaSyslinuxMBRtotheimage(notnecessary):
ddif=./syslinux4.02/mbr/mbr.binof=./dellsyslinux/diagssyslinux.imgconv=notrunc

ItshouldbepossibletocombinetheFreeDOS,MSDOSandDELLBIOimages.

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

9/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
Quote
NotethatFreeDOScanusec:\fdconfig.sysandc:\yourfreedosdirectory\fdauto.batinsteadofc:\config.sysandc:\autoexec.batthisismeanttomake
iteasiertoinstallFreeDOSandotherDOSversionsonthesameC:,lettingeachofthetwohaveaseparateconfiguration.FreeDOSwilllookfor
fdconfig.sysfirstandwillonlyuseconfig.sysiffdconfig.sysisnotpresent!TheSHELLlineinyourconfigfileiswherealternativebatchfilesinsteadof
autoexec.batcanbelinked.

http://sourceforge.n...#Known_problems(http://sourceforge.net/apps/mediawiki/freedos/index.php?
title=Install#Known_problems)
Soifyoucopyautoexec.battofdauto.batandconfig.systofdconfig.sysandmodifythemabit,youcangetaroundthe
problemoftheneedof2differentcommand.comfiles(youcanputtheFreeDOSoneinitsowndirectory).
Posted28July201004:28PM

geneC

@Icecube
@delicatepc
I'vegotbothaDellLatitudeE6400andaDellOptiPlex760that,whenIusedtheCDmadefromanISO(madeby
CW1384A0.exe)itworksbutusingSYSLINUX4.02toaharddiskimage(madebythesame),itseemstohardlockwhen
workingwiththeRAMDRIVEsetup.
I'mgoingtotryafewexperiments.
Posted28July201005:26PM

geneC

@delicatepc
Sofaritappearsthatsafeint(thedefault)inEDDornonEDDmodeisbrokenbuteverythingelseseemsOK.I'vetested
raw,bigraw,andint(withnoedd/noeddoptionstoforceiteitherway)andalliswell.
@icecube
Nowtotrythechainloading....:D
Posted28July201011:36PM

geneC

gCumm,onJul282010,06:26PM,said:
@icecube
Nowtotrythechainloading....:D

I'malmostcertainthatatthistimeusingtheDRMK(DellRealModeKernel)willrequireauniquechain.c32optionas
thereisalotmoredatapreloadedintotheregisterswhenenteringDELLBIO.BINonanormalDellDiagdisk(at0x700).
Forinstance,thelengthofDELLBIO.BINisinthere.
Posted28July201011:56PM

geneC

@delicatepc
@Icecube
Success(sortof).Ifyousavetheoriginalbootsectorfirstasa.bssandthenloadthe.bssfileasakerneltoSYSLINUX,it
works.
It'snotchainloadingbutit'sbetterthannothing(fornow).
Posted29July201006:32AM

Icecube

gCumm,onJul292010,01:56AM,said:
Success(sortof).Ifyousavetheoriginalbootsectorfirstasa.bssandthenloadthe.bssfileasakerneltoSYSLINUX,itworks.
It'snotchainloadingbutit'sbetterthannothing(fornow).

Itriedthatbeforewithchain.c32tooanditworked:

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

10/11

23/4/2016

ChainloadingAUTOEXEC/COMMAND.COM?TheSyslinuxProjectreboot.pro
ddif=/dellsyslinux/diagssyslinux.imgof=/dellsyslinux/diags.bsskip=63bs=512count=1

LABELdelldiagsbootsector
COM32chain.c32
APPENDhd0,1file=/diags.bs

Posted29July201007:48AM

WonkotheSane

gCumm,onJul292010,01:56AM,said:
@delicatepc
@Icecube
Success(sortof).Ifyousavetheoriginalbootsectorfirstasa.bssandthenloadthe.bssfileasakerneltoSYSLINUX,itworks.
It'snotchainloadingbutit'sbetterthannothing(fornow).

Really?
WonkotheSane,onJul272010,07:51PM,said:
BUTonlyreplacingthebootsectorfromtheSYSedimageonthe"untouchedone"itworkschainloadingthe(original)savedbootsector
copy.
So,thebootsectorapproachshouldwork,unlesssyslinuxchangessomethingelse(Iamnotfamiliarwithit)duringinstall.

Wonko
Posted29July201012:20PM

geneC

WonkotheSane,onJul292010,08:48AM,said:
Really?

Wonko

Ooops,musthavemissedthatinmyreading....

Page1of2

BacktoTheSyslinuxProject

reboot.pro Bootmethods&tools BootfromUSB/Bootanywhere TheSyslinuxProject

http://reboot.pro/topic/12052chainloadingautoexeccommandcom/

11/11