Re: [Freedos-user] crash with balder
Eric Auer wrote: > Hi again, > > >>> Now for the 1.0 ISO I am absolutely sure that it does have a >>> menu with several choices - more than just pressing return. >>> > > >> www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdbasecd.iso >> doesn't. >> > > >> I ran balder in dosbox and it worked but I can't burn it to cd because >> k3b says it is invalid (maybe because it is a floppy image. >> > > I downloaded the ISO myself and got the md5sum: > c9bfcf2d08dbe8bdb1fe95fb339e0b2b fdbasecd.iso (812 bytes) > > I have also tested it with k3b: You select "Extras -> CD -> > Burn CD Image file". This is k3b version 0.11, I am sure your > version of k3b has even more functions :-). > > >> The exact menu options are: >> 1. continue booting from CD >> 2. boot from the first hard drive >> 3. boot from floppy >> 4. skip CD and try first boot device >> > > Yes and after you select "booting from CD" you get the NEXT menu > which should give you several options again. The next menu may > have a shorter timeout and select some default by itself if you > do not press a key on time, but the next menu does exist :-). > > Eric > > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > I bought a floppy and I had to remove 2 PCI cards to put it in and now it boots. I updated the BIOS while I had the cards out. The same CD that didn't work before. It was very weird. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Hi again, > > Now for the 1.0 ISO I am absolutely sure that it does have a > > menu with several choices - more than just pressing return. > www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdbasecd.iso > doesn't. > I ran balder in dosbox and it worked but I can't burn it to cd because > k3b says it is invalid (maybe because it is a floppy image. I downloaded the ISO myself and got the md5sum: c9bfcf2d08dbe8bdb1fe95fb339e0b2b fdbasecd.iso (812 bytes) I have also tested it with k3b: You select "Extras -> CD -> Burn CD Image file". This is k3b version 0.11, I am sure your version of k3b has even more functions :-). > The exact menu options are: > 1. continue booting from CD > 2. boot from the first hard drive > 3. boot from floppy > 4. skip CD and try first boot device Yes and after you select "booting from CD" you get the NEXT menu which should give you several options again. The next menu may have a shorter timeout and select some default by itself if you do not press a key on time, but the next menu does exist :-). Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Hi James, > When I boot balder10.img from dosbox, it says > "PCI BIOS Invalid; XDMA not loaded!". > I'd flash my bios from dosbox but I doubt that is a good idea. > I put a screen capture of dos box: > http://lockie.ca/test/boot_000.png Dosbox has nothing to do with your real hardware at all. Much worse than dosemu. So you will not even be able to flash from there. It may indeed be the case that there is Linux software for flashing your BIOS directly, but you should NOT use any kind of VIRTUAL dos for that... Eric PS: XDMA is the harddisk udma driver - I think it should not be loaded by default, but only on user request. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
When I boot balder10.img from dosbox, it says "PCI BIOS Invalid; XDMA not loaded!". I'd flash my bios from dosbox but I doubt that is a good idea. I put a screen capture of dos box: http://lockie.ca/test/boot_000.png - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Eric Auer wrote: > Hi James, > > >> [freedos 1.0] crashes after I press return on the menu. >> > > Now for the 1.0 ISO I am absolutely sure that it does have a > menu with several choices - more than just pressing return. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdbasecd.iso) doesn't. I ran balder in dosbox and it worked but I can't burn it to cd because k3b says it is invalid (maybe because it is a floppy image. I made a CD with the boot image balder10.img and it still crashes. The exact menu options are: 1. continue booting from CD 2. boot from the first hard drive 3. boot from floppy 4. skip CD and try first boot device I wish I could capture the screen. I ran 'boot balder10.img' from dosbox and I got a menu I'd never seen and it didn't crash. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
> > Hi James, > >> [freedos 1.0] crashes after I press return on the menu. > > Now for the 1.0 ISO I am absolutely sure that it does have a > menu with several choices - more than just pressing return. I think the first menu shows 3-4 options and press return is continue booting from CD. There are options to boot fro either of my 2 hard disks (2 options). I don't remember an option to boot without ems but I will dig. :-) > > So you can select another menu item, for example "boot without > emm386 driver for ems / umb". There are several menu items > and there are even several menus. Please tell exactly in which > menu which choice fails in which way. If a menu goes ways too > quickly, you can usually hit a cursor key or similar so DOS > knows you are busy making a selection and stops the timeout > which would normally select a default after a while. You can > even use the pause key on the upper right of your keyboard > (and continue by hitting another key). > >> www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip >> How do I run 'sys' under Linux? > > That is a bit complicated to use, but basically you do something > like "perl ./sys-freedos.pl --lba --disk=/dev/fd0" for diskette. > > For harddisk, you would select ONLY the fat filesystem in question, > NOT the whole harddisk... Otherwise you would overwrite your whole > partitioning scheme. So "sys in Linux" is basically as dangerous > as "fdisk in DOS" - one wrong choice and you have messed up your > PC. Of course expert users can often fix it again without losing > a single file, but this can be very complicated. > > > So... Please do figure out how to gain more control over > Balder or the CDROM distro before you try to SYS from Linux. > This will also help us to find out what is wrong with the > diskette and cdrom distro and whether it is sufficient to > do a clever selection of menu items to work around. > > Thanks! Eric > > PS: Please give more information about the kind of hardware > you are using. What sort of PC, harddisk, cdrom/dvd, BIOS, > which CPU, how much RAM, any sound, scsi, raid, sata, net...? > > I have an ASRock Alive NF5 eSata2+ motherboard first release BIOS which is the whole point to update via freedos. An AMD Athlon X2 4000+ 4GB of RAM 2 SATA hard disks DVD RW no floppy sound on the motherboard MSI [EMAIL PROTECTED] Plus DLink DWL-G520 wirelewess card - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Hi James, > [freedos 1.0] crashes after I press return on the menu. Now for the 1.0 ISO I am absolutely sure that it does have a menu with several choices - more than just pressing return. So you can select another menu item, for example "boot without emm386 driver for ems / umb". There are several menu items and there are even several menus. Please tell exactly in which menu which choice fails in which way. If a menu goes ways too quickly, you can usually hit a cursor key or similar so DOS knows you are busy making a selection and stops the timeout which would normally select a default after a while. You can even use the pause key on the upper right of your keyboard (and continue by hitting another key). > www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip > How do I run 'sys' under Linux? That is a bit complicated to use, but basically you do something like "perl ./sys-freedos.pl --lba --disk=/dev/fd0" for diskette. For harddisk, you would select ONLY the fat filesystem in question, NOT the whole harddisk... Otherwise you would overwrite your whole partitioning scheme. So "sys in Linux" is basically as dangerous as "fdisk in DOS" - one wrong choice and you have messed up your PC. Of course expert users can often fix it again without losing a single file, but this can be very complicated. So... Please do figure out how to gain more control over Balder or the CDROM distro before you try to SYS from Linux. This will also help us to find out what is wrong with the diskette and cdrom distro and whether it is sufficient to do a clever selection of menu items to work around. Thanks! Eric PS: Please give more information about the kind of hardware you are using. What sort of PC, harddisk, cdrom/dvd, BIOS, which CPU, how much RAM, any sound, scsi, raid, sata, net...? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Eric Auer wrote: > Hi James, > > >> I just ran the boot disk as-is. >> > > There should be some sort of boot menu which lets you > select whether you want to load the EMS / UMB driver emm386. > You can use F8 to single step over config / autoexec. > You usually do want to load HIMEM, but not emm386. > I didn't have a boot menu, it crashed too soon. I figured it ight have been the way I put it on my USB key but I put this on CD http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdbasecd.iso and it crashes after I press return on the menu. It is better but still no use. 0CD5 ECA0 0A07 1105 1B80 9D22 0001 4200 00FB 0080 0549 0002 > You can also update it to jemm386 from Japheth.de but all > emm386 can have the problem that they sometimes need manual > configuration to run stable, so they are not one size fits > all and should therefore be avoided in "universal default" > configuration options imho. On the other hand, UMBs are a > good way to have more DOS RAM free and automatic default > configuration often works, so "a good distro" will have a > non-default boot menu item with a "safe" emm386 config :-) > > >> I will play with the autoexec and see if I can narrow it down. >> > > Do not forget fdconfig sys or - if none exists - config sys... > FreeDOS uses the former if present and the latter otherwise. > > >> Make the partition larger than 1.44KB so I can easily >> fit more stuff on it. >> > > Ah then you probably do not want a diskimage distro. You > will instead want something like "take a FAT partition, > copy kernel sys and command com on it, and run SYS to make > it bootable / add a bootsector". That should work with > > www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip > > but if you formatted the partition with mkdosfs (dosfstools) > then you may need some extra manual settings for this tool. > > If you want to make some USB stick bootable, the best choice > is to leave it FAT-formatted as it is, not reformat it. You > may also have to use fdisk to mark the partition as bootable > and / or add bootable MBR code, but this will depend on your > BIOS. It is quite normal that a modern BIOS can use the first > partition on some USB device (USB stick, ZIP, etc) to simulate > a large unpartitioned drive, making the "active / bootable" > flag and MBR code less relevant for USB booting. > > Eric > How do I run 'sys' under Linux? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Hi James, > I just ran the boot disk as-is. There should be some sort of boot menu which lets you select whether you want to load the EMS / UMB driver emm386. You can use F8 to single step over config / autoexec. You usually do want to load HIMEM, but not emm386. You can also update it to jemm386 from Japheth.de but all emm386 can have the problem that they sometimes need manual configuration to run stable, so they are not one size fits all and should therefore be avoided in "universal default" configuration options imho. On the other hand, UMBs are a good way to have more DOS RAM free and automatic default configuration often works, so "a good distro" will have a non-default boot menu item with a "safe" emm386 config :-) > I will play with the autoexec and see if I can narrow it down. Do not forget fdconfig sys or - if none exists - config sys... FreeDOS uses the former if present and the latter otherwise. > Make the partition larger than 1.44KB so I can easily > fit more stuff on it. Ah then you probably do not want a diskimage distro. You will instead want something like "take a FAT partition, copy kernel sys and command com on it, and run SYS to make it bootable / add a bootsector". That should work with www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip but if you formatted the partition with mkdosfs (dosfstools) then you may need some extra manual settings for this tool. If you want to make some USB stick bootable, the best choice is to leave it FAT-formatted as it is, not reformat it. You may also have to use fdisk to mark the partition as bootable and / or add bootable MBR code, but this will depend on your BIOS. It is quite normal that a modern BIOS can use the first partition on some USB device (USB stick, ZIP, etc) to simulate a large unpartitioned drive, making the "active / bootable" flag and MBR code less relevant for USB booting. Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Eric Auer wrote: > Hi James, > > >> Grrr, balder crashes too. :-( >> > > Did you try -not- loading emm386? > I just ran the boot disk as-is. > >> 0CD5 ECA0 0A07 1105 1B80 90A2 0001 4200 00FB 0080 0549 0002 90A2 >> 0CD5 ECA0 0A07 1105 5010 9989 0001 4200 0280 5873B 0002 >> > > Same crash, which program were you running at that moment? > I will play with the autoexec.bat and see if I can narrow it down. > >> I burned a couple of CD that both crashed so I decided >> not to waste anymore CDs. :-) >> > > When will people learn to use cd-rw or dvd-rw...? > Good idea. I'll get one of those. > >> I use k3b and I didn't see any option to use a floppy boot image. >> > > You first start a data cd or dvd project and then select > project -> edit boot images. > Cool, thanks. > >> Is there a way to extend FAT? >> > > Extend in what way? > Make the partition larger than 1.44KB so I can easily fit more stuff on it. > >> I did 'cat balder10.img > /dev/sdc' to make my USB key (/dev/sdc) >> boot but I am having a hard time making the new BIOS fit. >> > > That would be a strange way to deal with a diskette image. > Try using usblinux / isolinux or try using > > www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip > > Eric Ok, thanks. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] crash with balder
Hi James, > Grrr, balder crashes too. :-( Did you try -not- loading emm386? > 0CD5 ECA0 0A07 1105 1B80 90A2 0001 4200 00FB 0080 0549 0002 90A2 > 0CD5 ECA0 0A07 1105 5010 9989 0001 4200 0280 5873B 0002 Same crash, which program were you running at that moment? > I burned a couple of CD that both crashed so I decided > not to waste anymore CDs. :-) When will people learn to use cd-rw or dvd-rw...? > I use k3b and I didn't see any option to use a floppy boot image. You first start a data cd or dvd project and then select project -> edit boot images. > Is there a way to extend FAT? Extend in what way? > I did 'cat balder10.img > /dev/sdc' to make my USB key (/dev/sdc) > boot but I am having a hard time making the new BIOS fit. That would be a strange way to deal with a diskette image. Try using usblinux / isolinux or try using www.coli.uni-saarland.de/~eric/stuff/soft/specials/sys-freedos-linux.zip Eric - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] crash with balder
Eric Auer wrote: > Hi James, > > >> I downloaded http://odin.fdos.org/fdodin06.bin.zip >> and put it on my flash drive to be bootable. >> Is there a more recent bootable version because that crashes. >> > > Yes ODIN is totally outdated. Please let me know what linked > to this version, so we can update the link to point to > > www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unofficial/balder/ > Grrr, balder crashes too. :-( Build 2036 Aug 18, 2006 interrupt dive by zero, stack: 0CD5 ECA0 0A07 1105 1B80 90A2 0001 4200 00FB 0080 0549 0002 90A2 > >> 1.1.33 build 2033 Jan 31 2004 >> interrupt divide by zero, stack: >> 0CD5 ECA0 0A07 1105 5010 9989 0001 4200 0280 5873B 0002 >> I've tried other (probably) older versions but they crash on my new >> machine too. >> I do not have a floppy and I run Linux. >> I have an ASRock-ALive NF%-eSata2+ mb. >> I just want to update the BIOS. >> > > You may want to boot from cdrom or dvd :-) Most cd-writing tools > let you make a cd/dvd bootable by adding a diskette image. For > example the Balder one (even that is not most recent, Rugxulo > would probably be even better but is work in progress) :-). > I burned a couple of CD that both crashed so I decided not to waste anymore CDs. :-) I use k3b and I didn't see any option to use a floppy boot image. :-( I'll ask on that mailing list. Is there a way to extend FAT? I did 'cat balder10.img > /dev/sdc' to make my USB key (/dev/sdc) boot but I am having a hard time making the new BIOS fit. > Eric > > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > I think they were links off fdos.org http://odin.fdos.org/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user