Re: [Freedos-user] adding executable file to FreeDOS 1.1 installation image
Hi Martin, How are you doing? Well, i think you should try to boot your previous iso image loading the cd driver it should create a d:\ or so that would have your files, but once again, i`m not really sure that will work out... any suggestion, folks? Geraldo Netto Non dvcor, dvco = Sapere Aude São Paulo, Brasil, -3gmt site: http://exdev.sf.net/ On 25 June 2012 20:47, Martin T m4rtn...@gmail.com wrote: Geraldo, you are probably correct. If I use fdboot.img as a floppy drive image like this: qemu -fda /home/martin/FreeDOS/isolinux/fdboot.img -boot a -m 128m ..I end up on the very same A:\ prompt. So I should: A) mount the CD mount point on the A:\ prompt Is this possible at all? As much as I browsed Wikipedia List of MS-DOS commands and checked utilities available on the A:\ prompt, there was no possibility to mount or access files other than included into fdboot.img floppy image. B) add BIOS flashing tool and BIOS ROM files to fdboot.img New fdboot.img should be much larger than the original one because flash tool itself is ~2MB. I did this: 1) Created 10MB raw file: root@debian64:~# dd if=/dev/zero of=10MB bs=10M count=1 1+0 records in 1+0 records out 10485760 bytes (10 MB) copied, 0,02243 s, 467 MB/s root@debian64:~# 2) Created partition table to MBR using fdisk. Results are following: root@debian64:~# fdisk -lu 10MB You must set cylinders. You can do this from the extra functions menu. Disk 10MB: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders, total 0 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x3009589f Device Boot Start End Blocks Id System 10MB1 * 1 1606499 803249+ 6 FAT16 root@debian64:~# 3) Mounted this 10MB file with 32256 offset: root@debian64:~# echo 63*512 | bc -l 32256 root@debian64:~# losetup --offset 32256 /dev/loop1 10MB root@debian64:~# 4) Created FAT16 file system: root@debian64:~# mkdosfs -F 16 -v /dev/loop1 mkdosfs 3.0.9 (31 Jan 2010) Loop device does not match a floppy size, using default hd params /dev/loop1 has 64 heads and 32 sectors per track, logical sector size is 512, using 0xf8 media descriptor, with 20416 sectors; file system has 2 16-bit FATs and 4 sectors per cluster. FAT size is 20 sectors, and provides 5085 clusters. There are 4 reserved sectors. Root directory contains 512 slots and uses 32 sectors. Volume ID is e2c98373, no volume label. root@debian64:~# 5) Umounted 10MB image: root@debian64:~# losetup -d /dev/loop1 root@debian64:~# 6) Copied MBR boot code to 10MB disk image: root@debian64:~# dd if=/usr/lib/syslinux/mbr.bin of=10MB bs=1 count=440 conv=notrunc 440+0 records in 440+0 records out 440 bytes (440 B) copied, 0,000622907 s, 706 kB/s root@debian64:~# file -s 10MB 10MB: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 1, 1606499 sectors, code offset 0x31 root@debian64:~# 7) Installed syslinux to 10MB1 partition(that is the reason I used 32256 byte offset): root@debian64:~# syslinux --install --offset 32256 10MB root@debian64:~# 8) Mounted this 10MB1 partition: root@debian64:~# mount 10MB /media/10MBfiledir/ -o loop,offset=32256 root@debian64:~# 9) Copied files from fdboot.img floppy image and few additional ones: root@debian64:~# ls /media/10MBfiledir/ atiflash.exe CHOICE.EXE DEVLOAD.COM ELTORITO.SYS FDCONFIG.SYS fdisk.ini HD5870.rom KERNEL.SYS MDISKCHK.COM SHSUCDX.COM UIDE.SYS USB2 XMSSIZE.COM AUTOEXEC.BAT COMMAND.COM EDIT.EXE FDAPM.COM FDISK.EXE GETARGS.COM jemmex.exe ldlinux.sys SHSUCDHD.EXE TDSK.EXE UPDATE.BAT vmsmount.exe root@debian64:~# 10) Unmounted 10MB image: root@debian64:~# umount /media/10MBfiledir root@debian64:~# As much as I understand, everything is done- 440 byte boot code in MBR is present, partition table in MBR is present, syslinux is installed to first partition, FAT16 file system is created to first partition and finally all the files from floppy image are copied to this 10MB image. However, I'm not able to boot into DOS with qemu. If I execute qemu with qemu -hda 10MB -boot c -m 128m I end up with: Booting from Hard Disk... Missing Operating System. No bootable device. Image as well: http://i.imgur.com/G45gj.png Any suggestions? regards, martin 2012/6/25, Geraldo Netto geraldone...@gmail.com: Hi Martin, files are probably not on your a:\ but on your cd mount point (maybe d:\?) in order to add to your files on a:\ you will need to edit the img file which represents a virtual floppy disk as far as i know isolinux has the magic configuration which points out to the img file i said before... maybe Bern or Eric can give you more details... (or any other FreeDOS fellow, of course :P) Kind Regards and Best Wishes, Geraldo Netto Non dvcor, dvco
Re: [Freedos-user] fdupdate
I have been blissfully unaware of the packaging requirements for FreeDOS. I update mTCP a few times a year, and I know that is a lot of work to get right. Is there a FAQ or notes on how FreeDOS manages packages? If I can make the mTCP updates easier I will. Mike -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] adding executable file to FreeDOS 1.1 installation image
Geraldo, thanks, I'm fine. In case I boot the freedos.iso image with qemu -cdrom freedos.iso -boot d -m 128 and try to access any drive other than A:\, I get the Invalid drive error: http://i.imgur.com/7XjgG.png I'm afraid one can not access other files in A:\ mode than the ones on the floppy image. Any other ideas? regards, martin 2012/6/26, Geraldo Netto geraldone...@gmail.com: Hi Martin, How are you doing? Well, i think you should try to boot your previous iso image loading the cd driver it should create a d:\ or so that would have your files, but once again, i`m not really sure that will work out... any suggestion, folks? Geraldo Netto Non dvcor, dvco = Sapere Aude São Paulo, Brasil, -3gmt site: http://exdev.sf.net/ On 25 June 2012 20:47, Martin T m4rtn...@gmail.com wrote: Geraldo, you are probably correct. If I use fdboot.img as a floppy drive image like this: qemu -fda /home/martin/FreeDOS/isolinux/fdboot.img -boot a -m 128m ..I end up on the very same A:\ prompt. So I should: A) mount the CD mount point on the A:\ prompt Is this possible at all? As much as I browsed Wikipedia List of MS-DOS commands and checked utilities available on the A:\ prompt, there was no possibility to mount or access files other than included into fdboot.img floppy image. B) add BIOS flashing tool and BIOS ROM files to fdboot.img New fdboot.img should be much larger than the original one because flash tool itself is ~2MB. I did this: 1) Created 10MB raw file: root@debian64:~# dd if=/dev/zero of=10MB bs=10M count=1 1+0 records in 1+0 records out 10485760 bytes (10 MB) copied, 0,02243 s, 467 MB/s root@debian64:~# 2) Created partition table to MBR using fdisk. Results are following: root@debian64:~# fdisk -lu 10MB You must set cylinders. You can do this from the extra functions menu. Disk 10MB: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders, total 0 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x3009589f Device Boot Start End Blocks Id System 10MB1 * 1 1606499 803249+ 6 FAT16 root@debian64:~# 3) Mounted this 10MB file with 32256 offset: root@debian64:~# echo 63*512 | bc -l 32256 root@debian64:~# losetup --offset 32256 /dev/loop1 10MB root@debian64:~# 4) Created FAT16 file system: root@debian64:~# mkdosfs -F 16 -v /dev/loop1 mkdosfs 3.0.9 (31 Jan 2010) Loop device does not match a floppy size, using default hd params /dev/loop1 has 64 heads and 32 sectors per track, logical sector size is 512, using 0xf8 media descriptor, with 20416 sectors; file system has 2 16-bit FATs and 4 sectors per cluster. FAT size is 20 sectors, and provides 5085 clusters. There are 4 reserved sectors. Root directory contains 512 slots and uses 32 sectors. Volume ID is e2c98373, no volume label. root@debian64:~# 5) Umounted 10MB image: root@debian64:~# losetup -d /dev/loop1 root@debian64:~# 6) Copied MBR boot code to 10MB disk image: root@debian64:~# dd if=/usr/lib/syslinux/mbr.bin of=10MB bs=1 count=440 conv=notrunc 440+0 records in 440+0 records out 440 bytes (440 B) copied, 0,000622907 s, 706 kB/s root@debian64:~# file -s 10MB 10MB: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 1, 1606499 sectors, code offset 0x31 root@debian64:~# 7) Installed syslinux to 10MB1 partition(that is the reason I used 32256 byte offset): root@debian64:~# syslinux --install --offset 32256 10MB root@debian64:~# 8) Mounted this 10MB1 partition: root@debian64:~# mount 10MB /media/10MBfiledir/ -o loop,offset=32256 root@debian64:~# 9) Copied files from fdboot.img floppy image and few additional ones: root@debian64:~# ls /media/10MBfiledir/ atiflash.exe CHOICE.EXE DEVLOAD.COM ELTORITO.SYS FDCONFIG.SYS fdisk.iniHD5870.rom KERNEL.SYS MDISKCHK.COM SHSUCDX.COM UIDE.SYS USB2 XMSSIZE.COM AUTOEXEC.BAT COMMAND.COM EDIT.EXE FDAPM.COM FDISK.EXE GETARGS.COM jemmex.exe ldlinux.sys SHSUCDHD.EXE TDSK.EXE UPDATE.BAT vmsmount.exe root@debian64:~# 10) Unmounted 10MB image: root@debian64:~# umount /media/10MBfiledir root@debian64:~# As much as I understand, everything is done- 440 byte boot code in MBR is present, partition table in MBR is present, syslinux is installed to first partition, FAT16 file system is created to first partition and finally all the files from floppy image are copied to this 10MB image. However, I'm not able to boot into DOS with qemu. If I execute qemu with qemu -hda 10MB -boot c -m 128m I end up with: Booting from Hard Disk... Missing Operating System. No bootable device. Image as well: http://i.imgur.com/G45gj.png Any suggestions? regards, martin 2012/6/25, Geraldo Netto geraldone...@gmail.com: Hi Martin, files are probably not on your a:\ but on your cd mount
Re: [Freedos-user] adding executable file to FreeDOS 1.1 installation image
Op 26-6-2012 19:39, Martin T schreef: Geraldo, thanks, I'm fine. In case I boot the freedos.iso image with qemu -cdrom freedos.iso -boot d -m 128 and try to access any drive other than A:\, I get the Invalid drive error: @ECHO OFF echo Loading EL-TORITO ISO9660 non-emulation driver as FDCD0001 DEVLOAD ELTORITO.SYS /D:FDCD0001 echo Assigning driveletter X: to block device FDCD0001 SHSUCDX /D:FDCD0001,X DIR X: or: echo Loading ISA/PCI IDE/EIDE/ATA/SATA optical drive device driver DEVLOAD UIDE.SYS /D:FDCD0001 /N3 /B echo Assigning drive X: SHSUCDX /D:FDCD0001,X -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] adding executable file to FreeDOS 1.1
I do not know if this helps you but if you want to set up a bootable CD with FreeDOS let me explain how I do that using is a completely different approach: I use Bochs to install FreeDOS on a VMWare disk image from the FreeDOS distribution CD ISO image and then make a bootable CD from this disk image. When booting this CD ROM it will appear as the C: drive and FreeDOS scans all other disks and lets you access them as D:,E: etc. Of cause you can access all files on the C: drive which is the CD too. First I make an empty hard disk image with BXImage which comes with Bochs. This can be e.g. 60 MB, 400 MB etc. Then I boot from the FreeDOS ISO image and install FreeDOS 1.1 on this hard disk image. I observed here that I have to uncheck to install the isolinux files to make this hard disk image bootable. The entire install process is described in detail in the FreeDOS Wiki. Then I load VDK which lets me access this disk image from Windows XP explorer and transfer files to it. Bochs lets you test if all works as expected using the hard disk image before making a bootable CD. You can also test the created CD image without burning it to a real CD. Finally I use Nero to convert the disk image to a bootable CD image using the El Torito standard. All this is described in detail my Bochs tutorial chapter four. https://peter-bochs.googlecode.com/files/Bochs%20-%20a%20Guide%20and%20Tutorial%20for%20Windows%20II.pdf I have to add that my applications do not seem to work with FreeDOS 1.1 and I have to resort to Rugxulo's bare DOS distribution to make it work. I get page faults when using FreeDOS 1.1 with cwsdpmi. Georg -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
