• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About kDn

  1. I use few versions grub4dos at same time . Currently I testing my fbinst.cmd script for automatic and simple working with different boot-loaders. After some testing I publicate it to boot-land . Maybe it will be interesting some people. Additional info: http://forum.ru-board.com/topic.cgi?forum=...p;start=1640#20 (old version) http://forum.ru-board.com/topic.cgi?forum=...mp;start=2060#4 (new version) http://forum.ru-board.com/topic.cgi?forum=...p;start=2060#20 (update) Script using some ideas by COD11 & jaclaz http://www.boot-land.net/forums/index.php?...ost&p=86217
  2. @jaclaz This is very interesting question . I think () may change own type corresponding context of command grub4dos. Try this commands: map () (hd1) map --hook cat --hex --length=512 (hd0)+1 cat --hex --length=512 (hd1)+1 cat --hex --length=512 (hd0,0)+1 cat --hex --length=512 (hd1,0)+1 ls ()/ root () geometry (), geometry (hd0), geometry (hd0,0) And as I know grub4dos manual may be not correct sometimes... or do not have additional information about using commands. I also read chines forums, ChangeLog_GRUB4DOS.txt (new syntax "map"-command coming soon, current on testing stage). 2009-11-11 let PXE_BUF use BUFFERADDR. cancelled (hd+) support. added (hd) and (hd-N) support. http://nufans.net/grub4dos/tinybit/
  3. bluenix Try: @jaclaz is means: not root partition correct exchange: where () may be (fd0) or (hd0)
  4. Yes, I tested this method of install on VMWare many times.
  5. cdob Sorry for the late answer, I was too busy last days... Russian forums hard to translate becouse all forum posts filled with technical jargon. I don't test running recovery console from sorted iso yet, becouse I use isolated iso (~15Mb) with integrated mass storage drivers. title cmdcons.iso map --floppies=1 map --mem /boot/_ima/firadisk.gz (fd0) map --mem /boot/_iso/cmdcons.iso (0xFF) map --hook ls (fd0)/firadisk.sys chainloader (0xFF) This posts in forum not about using XP_Inst method, only general talk about making bootable CD whith grub4dos as boot loader.
  6. cdob Yes, you may ignore this strings I don't use ...\Inst\... path, as you can see earlier I use write --offset=0 (fd0)/setup/ISOimage.ini \\boot\\XP_RAM.ISO\n;\n;\n;. If follow script logic then can see: set ISO_file_search=\Inst\XP_RAM.ISO if exist ISOimage.ini for /f "eol=;" %%a in (ISOimage.ini) do if not %%a.==. set ISO_file_search=%%a if exist c:%ISO_file_search% set reassign=true if defined reassign if /I %SystemDrive%.==C:. set reassign= 1. Set default path 2. Read new path from ISOimage.ini 3. If exist c:\boot\XP_RAM.ISO then reassign=true (in my case) 4. If defined reassign and %SystemDrive%.==C: then reassign not needed When people testing yours method they feedback error in some cases when installing XP from USB-HDD or USB-Flash as HDD... First stage (txt-mode-setup) running absolutly correct, but after reboot they give error like: Needed file 'asms' on Windows XP Professional Service Pack 3 CD and after Shift+F10 and looking presetup.log we can see that USB device where placed XP_RAM.ISO not found... Error feedback: http://forum.ru-board.com/topic.cgi?forum=...p;start=1560#20 http://greenflash.su/forum/2-331-4647-16-1256148181 That's about unattended install? I not sure... As I think - correct some values outside ISO and IMA winnt.sif more simplest way. This solution founded when I tested wrong winnt.sif placed inside ISO and which give error like that: setup cannot copy the file: firadisk.sys ... and other from IMA Problem description: http://forum.ru-board.com/topic.cgi?forum=...mp;start=1640#7 http://forum.ru-board.com/topic.cgi?forum=...p;start=1700#15 http://forum.ru-board.com/topic.cgi?forum=...p;start=1720#16
  7. If you want to use multiple unattended-mode installation, you may do some simple steps: 1. Create file WINNT.SIF with 65536 space chars (0x20), and put it in the root of floppy image (XP_INST.IMA) 2. Use menu item like that:
  8. On some systems USB do not initialized properly, this can be fixed like that:
  9. cdob Another some little changes maded in setup script (SETUP.CMD) for more correct work, compare and confirm its please. SETUP.7z
  10. cdob All works pretty good. Thanks a lot for yours work.
  11. This an idea to construct menu entry on-the-fly... Look to the post #59 or #66
  12. cdob What you think about that? title Test generating menu #(fd1) optional, required at some BIOS #map --mem /Boot/XP_INST.gz (fd1) map --mem /Boot/XP_INST.gz (fd0) ls /Boot/XP_RAM.ISO || find --set-root /Boot/XP_RAM.ISO map /Boot/XP_RAM.ISO (0xFE) map (hd0) (hd1) map (hd1) (hd0) map --hook # EMPTY512.LST content 512 spaces write --offset=0x00 (fd0)/EMPTY512.LST default 0\n###### write --offset=0x10 (fd0)/EMPTY512.LST \ntimeout 0\n\n## write --offset=0x20 (fd0)/EMPTY512.LST \ntitle TOFF\n### write --offset=0x30 (fd0)/EMPTY512.LST \nmap --mem (0xFE) (0xFF)\n# write --offset=0x60 (fd0)/EMPTY512.LST \nmap --hook\n### write --offset=0x70 (fd0)/EMPTY512.LST \nmap --unmap=0xFE\n##### write --offset=0x88 (fd0)/EMPTY512.LST \nchainloader (0xFF)/I386/SETUPLDR.BIN\n# # RAMBOOT.TXT content like "+12345667" without quotes dd if=(0xfe)/RAMBOOT.TXT of=(fd0)/EMPTY512.LST seek=0x44 count=0x0A configfile (fd0)/EMPTY512.LST
  13. Maybe this can be usefull: cdob I dont know good solution, or universal way... But I try thinking about it
  14. very experimental version works fine