Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 7-8-2011 17:24, c...@bttr-software.de schreef: >> Just the abort/retry/fail dialogue. > > Yeah, that's the critical error handler. > >> Doesn't seem to be a way out if you >> offer a PAUSE (and control-C to get to console) but only load ramdrive >> after USB drivers. > > What do you mean by "doesn't seem to be a way out" ? My experience with USB drivers so far is they kill my USB keyboard by overriding the legacy USB stack without providing a new keyboard driver. So far the solution seems to be to exclude whichever controller has the keyboard attached. I don't think connecting to PS/2 is an option due to the keyboard's built-in USB hub (Logitech G15 keyboard, USB1.1 attached, USB1.1 2-port hub). -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> Just the abort/retry/fail dialogue. Yeah, that's the critical error handler. > Doesn't seem to be a way out if you > offer a PAUSE (and control-C to get to console) but only load ramdrive > after USB drivers. What do you mean by "doesn't seem to be a way out" ? Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 6-8-2011 14:44, dos386 schreef: > BTW, I had IIRC seen a GUI FreeDOS installer back in 2005 ? 2004 > in 0.9 ? 0.8 distros. NO, I don't recommend those distros ... You're correct, it was removed for beta9 or FD1.0 due to some bugs/issues to my knowledge. Still waiting for Jim to come up with the new text mode installer to switch to target directory after installation so configuration batchfile can run (once only please - gotta fix this) -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
BTW, I had IIRC seen a GUI FreeDOS installer back in 2005 ? 2004 in 0.9 ? 0.8 distros. NO, I don't recommend those distros ... -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 6-8-2011 12:23, Georg Potthast schreef: > Rugxulo's bare bone floppy had too much meat for my application so I reduced > it further and added my DOSUSB driver files including a test file of 969k. > But it is a 20MB hard disk emulation. Was just wondering why you didn't go with straight floppy emulation. >> The usual trick is creating a ramdrive, copying files to there, adjust path >> and other settings (comspec), start a continuation batchfile from there >> including DOSUSB loading. > I could try that. Is there a sample that I can download somewhere? SHSURDRV has an option to mirror existing drives: SHSURDRV /D:A: (or was it /F:A:)?. Still I think Isolinux/Syslinux might be convenient, as its memdisk module already allows to boot an image as ramdisk. Due to you having a USB driver disk I guess it's perfectly safe for you to assume all machines your ISO runs on, will have at least 8MB RAM. > If you are booting from an USB-CD drive DOSUSB will stop further access to > it by the BIOS after being loaded. However, my Live-CD just look for USB 3.0 > ports so this does not apply when the USB-CD drive is connected to a 2.0 > port. Time for a USB2.0 test CD :) > Georg Bernd -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
@Christian: the autoexec.bat on my Live-CD does "devload usbdisk.sys" and then "xmsdsk.exe". So there are apparently no "redirector (for example, *CDEX) CDS entries" when usbdisk.sys is loaded. @Travis: The CD and its ISOLinux do not include speech drivers, so I see no reason for automatic selection. I only refer to the ISOLinux menu on the CD. Also the next dialog "language selection" does not time out automatically anyway. @Bernd: >Size of C: surprised me as well as DIR /S showed all contents doesn't even >add up to 2.88MB. Rugxulo's bare bone floppy had too much meat for my application so I reduced it further and added my DOSUSB driver files including a test file of 969k. But it is a 20MB hard disk emulation. >The usual trick is creating a ramdrive, copying files to there, adjust path >and other settings (comspec), start a continuation batchfile from there >including DOSUSB loading. I could try that. Is there a sample that I can download somewhere? If you are booting from an USB-CD drive DOSUSB will stop further access to it by the BIOS after being loaded. However, my Live-CD just look for USB 3.0 ports so this does not apply when the USB-CD drive is connected to a 2.0 port. Georg -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 5-8-2011 23:35, c...@bttr-software.de schreef: > Eww. What caused the crash? The DOS kernel should gracefully abort > attempts to write to read-only media. (It probably would raise a critical > error, but it shouldn't crash.) Or does the BIOS crash on attempts to > write to the disk with the Int13 interface? Just the abort/retry/fail dialogue. Doesn't seem to be a way out if you offer a PAUSE (and control-C to get to console) but only load ramdrive after USB drivers. > Regards, > Christian Bernd -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> Just what I tried last night. Trying DIR > OUT.TXT already crashed the > entire thing due to C: being emulated harddisk(-partition) on CD-ROM, > and thus by definition read-only. Eww. What caused the crash? The DOS kernel should gracefully abort attempts to write to read-only media. (It probably would raise a critical error, but it shouldn't crash.) Or does the BIOS crash on attempts to write to the disk with the Int13 interface? Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
>> Wait for the DEVLOAD developers to release a version (3.24?) with >> that bug fixed. > > Regarding the drive letters and devload: I do not think this is a bug in > devload here. On my Live-CDs I use devload in the autoexec.bat file and it > assigns a new drive letter just fine. There is definitively a bug in DEVLOAD (3.22 and older) regarding CDS entry assignment when redirector (for example, *CDEX) CDS entries exist between or right after block-device-based CDS entries. This is currently being addressed by the developers. Your earlier description: >>> ... Now, when I load DOSUSB and then "devload usbdisk.sys" the >>> block device driver usbdisk.sys will get the drive letter F: >>> from FreeDOS. Apparently it does not supply the next drive letter >>> which would be G:. I can then access the flash disk as F:, but >>> "FD11Setup" is gone. This appears to be exactly how the DEVLOAD bug would behave. If you have any better explanation and resolution for this odd behaviour, feel free to speak up. I don't know why your boot CDs apparently aren't affected by the bug: If however, as you mentioned, your CDs simulate hard disks, and if you only use the simulated hard disk to access the CD (that is, if you are not ever installing any *CDEX), then it's simply the case that all of your DOS drives use block-device-based CDS entries as opposed to redirector CDS entries. The older DEVLOAD releases work fine on systems without redirector CDS entries. If you are loading a *CDEX to access the CD, then it could be the case that you aren't affected by the DEVLOAD bug because you assign the CD a drive that isn't right after the last block-device-based drive - if so. If there's enough gaps for all drives to be installed by DEVLOAD between the last block-device-based CDS entry and the first redirector CDS entry, then the DEVLOAD bug does not affect DEVLOAD's operation either. Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
As regards the time out issue, before continuing, I understand the argument against selecting anything, and just letting the end-user choose one after they've gotten around to it. However, I would strongly discourage this behavior, since many folks expect the machine to choose a default, and boot if they do nothing. In addition, folks who are trying to use the environment w/o sight kind of need it to continue, so their speech drivers will load. If they add stuff to autoexec.bat to load their speech drivers, and don't look at config.sys after they have sighted assistance the first time, then they will have no idea why it's not working. This could lead to all kinds of confusion, as well as a great deal of frustration on behalf of the user who doesn't realize the computer is waiting for them to do something to make it continue. Defaulting to continue after x seconds makes more sense in light of such considerations. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 5-8-2011 19:45, Georg Potthast schreef: > > I am a bit overwhelmed by the discussion following my post. I will try to > address some points. Just a quick possible issue: what happens if you boot the offered ISO from USB CD? As the HDD emulation part is read-only, while your USB drivers reset the USB stack, everything disappears? -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 5-8-2011 19:45, Georg Potthast schreef: > > I am a bit overwhelmed by the discussion following my post. I will try to > address some points. hehe, the discussion was already going, just added our contributions to your feedback as well. DOS386 also had some very usefull feedback that I'll have to take into consideration. >> Is there any driver for read-mounting harddisk images (maybe SHSUFDRV) in a >> situation where you boot from a separate bootdisk, access the CD and mount >> this (single-partition) harddisk image? > El-Torito is meant to be used to boot from and the disk can usually just be > accessed when supported by the BIOS. Windows XP cannot do it by the way. Yeah there exists some specific tools to extract boot image from a CD, unfortunately I can't remember any of these. > I think most BIOS versions support El-Torito. If the BIOS can boot the OS > from an El-Torioto CD which is set up as a floppy disk emulation it can also > boot from a CD that is set up as a hard disk emulation, both are included in > the El-Torito standard. So you do not need a new PC for that. You can > download one of my Live-CDs and test, just enter CTRL-C at the first prompt > and you skip all the USB stuff. Just what I tried last night. Trying DIR > OUT.TXT already crashed the entire thing due to C: being emulated harddisk(-partition) on CD-ROM, and thus by definition read-only. Size of C: surprised me as well as DIR /S showed all contents doesn't even add up to 2.88MB. > It took me quite a while to figure out how to make such a CD, but I > documented it: > To set up a El-Torito hard disk emulation CD please look at chapter 4 of my > Bochs tutorial: > http://peter-bochs.googlecode.com/files/Bochs%20-%20a%20Guide%20and%20Tutorial%20for%20Windows.pdf might be an interesting read :) > >> Wait for the DEVLOAD developers to release a version (3.24?) with that bug >> fixed. > Regarding the drive letters and devload: I do not think this is a bug in > devload here. On my Live-CDs I use devload in the autoexec.bat file and it > assigns a new drive letter just fine. Depends what you load inbetween. DEVLOAD seemed to overwrite redirector drives. Try loading CD drivers first, and SUBST, MS Client etc, then try DEVLOAD some driver that assigns driveletters. >> please try if skipping JEMMEX solves both > I do not really care if Jemmex is loaded or not, I just feel if this CD > shall become a major FreeDOS distribution, there should be no crashes. Also > loading a keyboard driver should not cause a crash. Ofcourse you're right there. Being worked on, just as many more issues. > DOSUSB has a problem to query the BIOS to find out if DOS was booted from a > USB device and where this device is connected to before starting its own USB > support. Only a few BIOS versions will allow to retrieve the information > that drive C is a USB disk and still I do not know where the disc is > connected to, so I did not implement that. I recommend to exclude that > controller manually after figuring out where the boot disk is connected to. > This works for embedded applications but remains a general problem. If a > customer would like to have that I would look into it again but so far this > never came up except by Eric. The usual trick is creating a ramdrive, copying files to there, adjust path and other settings (comspec), start a continuation batchfile from there including DOSUSB loading. I experienced the same thing of drives disappearing under my feet (thus hanging system) when loading TDSK from CD drive. It simply hijacked the driveletter. A real issue is BIOS presenting drives to kernel followed by kernel happily mapping the drives to driveletters. Instead it's much more convenient to only assign driveletter for current drive, and have the other ones added later on by some driver. > As for the keyboard and mouse driver, I agree that one could add more > features to DOSUSB but that is still on the todo-list. I'd consider it pretty essential. Lack of PS/2 keyboards on modern systems while your driver overrides legacy emulation. A machine which you can't give input to is severely limited in its actions. Anyway, thanks for your feedback in a fruitful discussion :) > Georg Bernd -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
I am a bit overwhelmed by the discussion following my post. I will try to address some points. In my opinion the CD should be easily usable by first-time FreeDOS users and not only by experienced DOS developers. This is the view I had when testing the CD. Bernd Blaauw schreef: ;-) >The idea is people select what to do in the Isolinux menu, thus skipping >any CONFIG.SYS menu. However there should be a short timeout to select >alternative options in case JEMM and the computer don't like each other >very much. I cannot see a reason why the ISOLinux menu should automatically choose a selection after five seconds. Why not give the first-time user ample time to read and think about what selection may be best for him? >After all, computers are turning into "single-disk fully NTFS-partitioned" >systems. Another reason against the automatic selection of the FreeDOS installation menu entry. >Is there any driver for read-mounting harddisk images (maybe SHSUFDRV) in a >situation where you boot from a separate bootdisk, access the CD and mount >this (single-partition) harddisk image? El-Torito is meant to be used to boot from and the disk can usually just be accessed when supported by the BIOS. Windows XP cannot do it by the way. I think most BIOS versions support El-Torito. If the BIOS can boot the OS from an El-Torioto CD which is set up as a floppy disk emulation it can also boot from a CD that is set up as a hard disk emulation, both are included in the El-Torito standard. So you do not need a new PC for that. You can download one of my Live-CDs and test, just enter CTRL-C at the first prompt and you skip all the USB stuff. It took me quite a while to figure out how to make such a CD, but I documented it: To set up a El-Torito hard disk emulation CD please look at chapter 4 of my Bochs tutorial: http://peter-bochs.googlecode.com/files/Bochs%20-%20a%20Guide%20and%20Tutorial%20for%20Windows.pdf >Wait for the DEVLOAD developers to release a version (3.24?) with that bug >fixed. Regarding the drive letters and devload: I do not think this is a bug in devload here. On my Live-CDs I use devload in the autoexec.bat file and it assigns a new drive letter just fine. >please try if skipping JEMMEX solves both I do not really care if Jemmex is loaded or not, I just feel if this CD shall become a major FreeDOS distribution, there should be no crashes. Also loading a keyboard driver should not cause a crash. >Just wanted to add to the above by saying it would be awesome if a >semi-full USB stack would exist. Basicly: recognise USB equipment whenever >not booting from it. DOSUSB has a problem to query the BIOS to find out if DOS was booted from a USB device and where this device is connected to before starting its own USB support. Only a few BIOS versions will allow to retrieve the information that drive C is a USB disk and still I do not know where the disc is connected to, so I did not implement that. I recommend to exclude that controller manually after figuring out where the boot disk is connected to. This works for embedded applications but remains a general problem. If a customer would like to have that I would look into it again but so far this never came up except by Eric. As for the keyboard and mouse driver, I agree that one could add more features to DOSUSB but that is still on the todo-list. Georg -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 4-8-2011 14:19, dos386 schreef: > Definitely. I'd prefer to see no Linux and no ReactOR is > FreeDOS distros. BTW, the ReactOR on the FreeDOS > floppy is even able to B.S. ;-) BS? :) I'll do a SYS A: /BOOTONLY /K KERNEL.SYS for the next floppy to disable the menu (enable by SYS A: /BOOTONLY /K CPUBOOT.SYS), or alternative set default option to 0 seconds. I like my floppy, you'll see some benefit as soon as I get iPXE integrated. Loading FreeDOS installer from internet should be interesting. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 4-8-2011 12:03, dos386 schreef: >> Maybe it would be better to have NO *emm* style driver loaded by defaul > > + 1 > > Definitely. The is absolutely no reason to load it. Technically there's no reason whatsoever to load any memory driver, as long as programs can still load/run. My intention was to get feedback on JEMM/JEMMEX for Japheth's sake (and our benefit) by offering it as default option, with fallback to XMS or commandline. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> I did a test of this CD too. First I would suggest to make an El-Torito hard > disk instead of using ISOLinux. DOS I feel should boot directly and not by > booting a version of Linux first. + 1 Definitely. I'd prefer to see no Linux and no ReactOR is FreeDOS distros. BTW, the ReactOR on the FreeDOS floppy is even able to B.S. ;-) -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> > When I select "Use FreeDOS as LiveCD system.." and have a Flash disk > > inserted, the El-Torito Bootable CD-Rom driver results in the error: > > "JemmEX: exception 0D occured". > That is the good old general protection fault (GPF) :-D > that you also know from Windows. VMM32.VXD brewed a GPF :-D > Maybe it would be better to have NO *emm* style driver loaded by defaul + 1 Definitely. The is absolutely no reason to load it. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> Blockdevices seem to have a \NUL > device associated for each drive. I think it's a shortcoming of the redirector interface or implementation if/when/that character devices do not show up in redirected directories. Function 2F.1223 appears to be intended to allow the redirector to detect character device names, to handle them in the same way the block device file system handler does. > Maybe TRUENAME would be of any use. > Interesting to compare TRUENAME X: between SHSUCDX and MSCDEX :) I don't see how fiddling with character device names or "TRUENAME" (21.60) would be of any use here. Just loop through the CDS entries and check the flags and such. I think that's what SHSUCDX does to allocate drives, too. Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 4-8-2011 0:46, c...@bttr-software.de schreef: > > In any case, it shouldn't be too hard. There might be some difficult > corner cases, but there's implementations of CDS scanning available which > do work well enough, for example, SHSUCDX's. Nice challenge to test against SHSUCDX, MSCDEX, SUBST and possibly MS-CLIENT (NDIS/SMB TCP/IP stack). Blockdevices seem to have a \NUL device associated for each drive. Maybe TRUENAME would be of any use. Interesting to compare TRUENAME X: between SHSUCDX and MSCDEX :) -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> earlier in the thread, people said it is hard to find out > which drive letters are used in a fool-proof way... Where? In any case, it shouldn't be too hard. There might be some difficult corner cases, but there's implementations of CDS scanning available which do work well enough, for example, SHSUCDX's. Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> 3.23 should be the next version unless I missed one. Right. Messed that one up. > I hope to have a test version by this weekend, my current > code isn't ready for others yet. Looking forward to that. Regards, Christian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> That is the good old general protection fault (GPF) that you also know > from Windows. Maybe it would be better to have NO *emm* style driver > loaded by default, as those tend to be hard for "one size fits all" > configurations. Modern BIOSes and other hardware and firmware fail to > announce reserved areas properly, *emm* enables UMBs, conflict, bang. > > ... > > So maybe some "on-demand BIOS module for USB flash storage" is one of > those UMB conflict cases? But something else goes wrong with the keyb > driver as well - again, please try if skipping JEMMEX solves both :-) > Note that your BIOS typically decides about modules only at boot time. This doesn't sound like the EMM is at fault here; it just happens to catch GPF and UD exceptions to display a more informative message. Try using an alternative keyboard layout mapper. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 3-8-2011 23:05, Georg Potthast schreef: > I did a test of this CD too. First I would suggest to make an El-Torito hard > disk instead of using ISOLinux. DOS I feel should boot directly and not by > booting a version of Linux first. I did my LifeCDs with FreeDOS just as an > El-Torito hard disk with 10MB. I wonder if IsoHybrid disks would work. Those are loadable (by MEMDISK) as either ISO or Harddisk image. Not sure if CD drivers, ISO mounters etc will like this either. I should probably make a very flexible FreeDOS CD update batchfile right? * single layer ( 1 ISO) or shell (ISO inside Isolinux) * direct emulation - floppy image (read-only thus, CDROM required as long as emulated A:) - HDD image (same, but then C:) * non-emulation mode - grub - isolinux - nothing (smallest) - custom (memtest+, iPXE) - memdisk (ramdisk) - floppy - HDD - ISO - Isohybrid Deciding what should serve as floppy image source is interesting as well. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Hi Jeremy, earlier in the thread, people said it is hard to find out which drive letters are used in a fool-proof way... Also, I will not have "DOS time" for the rest of this week - so if you can come up with something magic, you are welcome. Thanks, Eric :-) >>> ... Now, when I load DOSUSB and then "devload usbdisk.sys" the >>> block device driver usbdisk.sys will get the drive letter F: from >>> FreeDOS. Apparently it does not supply the next drive letter which >>> would be G:. I can then access the flash disk as F:, but "FD11Setup" >>> is gone. >> If you use DEVLOAD to load your block device driver, then obviously it is >> DEVLOAD which assigns the drive, not DOS. And DEVLOAD's ignorance of >> non-block device CDS entries is a bug already discussed elsewhere. Wait >> for the DEVLOAD developers to release a version (3.24?) with that bug >> fixed. Alternatively, implement a proper regular executable (as opposed to >> device driver) and modify the CDS and (E)DPBs and device chain yourself as >> necessary. > 3.23 should be the next version unless I missed one. Anyway if Eric doesn't > do it first I am working on updating devload to take used cds entries into > consideration. I hope to have a test version by this weekend, my current > code isn't ready for others yet. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 3-8-2011 23:05, Georg Potthast schreef:
> I did a test of this CD too. First I would suggest to make an El-Torito hard
> disk instead of using ISOLinux. DOS I feel should boot directly and not by
> booting a version of Linux first. I did my LifeCDs with FreeDOS just as an
> El-Torito hard disk with 10MB.
Hi Georg, thanks for your feedback, much appreciated.
You mean ELTORITO harddisk emulation instead of floppy emulation or
non-emulation mode? That could work, though your use case (your own
written shareware USB drivers) assumes a much more modern machine than
many situations FreeDOS could be used for.
Is there any driver for read-mounting harddisk images (maybe SHSUFDRV)
in a situation where you boot from a separate bootdisk, access the CD
and mount this (single-partition) harddisk image?
> Then I have to mention that I cannot read the menu within 5 seconds and
> decide what to select. After 5 seconds the menu will run automatically into
> the install FreeDOS on hard disk branch. And then wait forever to select the
> language. Therefore I would suggest to have no menu selection to be run
> automatically. Today, most people may use the CD to boot FreeDOS on a
> Windows7 PC and they do not want to install FreeDOS on the NTFS disk.
The idea is people select what to do in the Isolinux menu, thus skipping
any CONFIG.SYS menu. However there should be a short timeout to select
alternative options in case JEMM and the computer don't like eachother
very much.
>
> When I select "Use FreeDOS as LiveCD system.." and have a Flash disk
> inserted, the El-Torito Bootable CD-Rom driver results in the error:
> "JemmEX: exception 0D occured".
That's new to me, I might be able to test this sometime. Also I should
upload the ISO-inside-ISO so inner ISO is loaded to system memory then
mounted by ELTORITO.SYS.
> When I have no Flash disk inserted it boots ok and the prompt is on drive F:
> However, when I enter "keyb gr" I get the error: "JemmEX: exception 06
> occured".
Yes KEYB or its keyboard layout files are a bit buggy, I've received
suggestions to use some older layout files, not tested that out.
>
> Further drive F: is called "FD11Setup". Drive A: is "FDOS11Setup". Now, when
> I load DOSUSB and then "devload usbdisk.sys" the block device driver
> usbdisk.sys will get the drive letter F: from FreeDOS. Apparently it does
> not supply the next drive letter which would be G:. I can then access the
> flash disk as F:, but "FD11Setup" is gone.
Yes I've experienced this issue as well. A workaround is loading
SHSUFDRV (SHSUFDRV /F:F:\ISOLINUX\FDBOOT.IMG) then load your drivers.
Another workaround is unloading SHSUCDX temporary (which is rather messy
if doing so from the CD's driveletter..). A proper solution is getting
DEVLOAD fixed.
As for your drivers, I'm rather curious. Suppose I boot an USB flash
disk (2.0 interface, 2.0 port), and crappy BIOS is happy to stick to 1.1
speed. The flash disk gets assigned C:.
Next, I'd load your drivers, which
1) disable all BIOS legacy USB emulation (bye keyboard, mouse..)
2) Make contents of C: disappear below my feet and scripts can't continue.
How's this situation solved?
>
> The next menu option ("Boot into LiveCD system") will display the message
> "SHSUCDX could not detect any drives". When I enter "keyb gr" it returns
> "bad command or file name"
If no CD found then no KEYB found either as it's not in the floppy part
but just on data part of CD.
> The next menu option ("Load liveCD system without drivers") will boot ok
> with the same flash disk inserted and the command prompt will show G:
> If I then enter "keyb gr" to get German keyboard support the keyboard driver
> will crash with "illegal opcode".
Same KEYB issue, but it's intriguing that in this case everything loads
properly, while JEMM refuses (you could try JEMMEX LOAD from commandline
and see if errors encountered)
> When I enter "menu" as instructed, FreeDOS returns "bad command or file
> name" - so it does not find the menu command.
Hm MENU should be an ALIAS to the \SETUP.BAT , type ALIAS. I'll check if
this still works as intended.
> By the way this option selects option 5 on the next menu which does not show
> that as a valid (or documented) option.
Maybe ISOLINUX.CFG has a {FD=5?SOMETHING} string, or FDCONFIG.SYS. I'm
not sure anymore.
Anyway, I like the ISOLINUX menu solution as it allows to select/run
FDISK pretty fast without going through the mess of CD drivers.
Another big benefit is freeing the CD drive, as well as having writeable
space on A:.
Your harddisk image suggestion is an interesting option, I'll look into
it through both direct emulation and through isolinux/memdisk emulation.
ofcourse it will show up as C:, pushing real harddisk back to D:.
http://bootcd.narod.ru/images_e.htm also shows some interesting floppy
images (thus not ruining harddisk driveletter).
--
BlackBerry® D
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
On Aug 3, 2011 5:27 PM, wrote: > > > ... Now, when I load DOSUSB and then "devload usbdisk.sys" the > > block device driver usbdisk.sys will get the drive letter F: from > > FreeDOS. Apparently it does not supply the next drive letter which > > would be G:. I can then access the flash disk as F:, but "FD11Setup" > > is gone. > > If you use DEVLOAD to load your block device driver, then obviously it is > DEVLOAD which assigns the drive, not DOS. And DEVLOAD's ignorance of > non-block device CDS entries is a bug already discussed elsewhere. Wait > for the DEVLOAD developers to release a version (3.24?) with that bug > fixed. Alternatively, implement a proper regular executable (as opposed to > device driver) and modify the CDS and (E)DPBs and device chain yourself as > necessary. > > > -- 3.23 should be the next version unless I missed one. Anyway if Eric doesn't do it first I am working on updating devload to take used cds entries into consideration. I hope to have a test version by this weekend, my current code isn't ready for others yet. Jeremy -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Hi Georg, > I did a test of this CD too. First I would suggest to make an El-Torito hard > disk instead of using ISOLinux. DOS I feel should boot directly and not by > booting a version of Linux first. Isolinux is not Linux. Isolinux is a boot menu which, among other things, has the ability to boot Linux. There is no Linux in there. > Then I have to mention that I cannot read the menu within 5 seconds and > decide what to select. After 5 seconds the menu will run automatically into > the install FreeDOS on hard disk branch. That indeed is a risky default after such a short waiting time. > And then wait forever to select the > language. Therefore I would suggest to have no menu selection to be run > automatically. Today, most people may use the CD to boot FreeDOS on a > Windows7 PC and they do not want to install FreeDOS on the NTFS disk. I agree. > When I select "Use FreeDOS as LiveCD system.." and have a Flash disk > inserted, the El-Torito Bootable CD-Rom driver results in the error: > "JemmEX: exception 0D occured". That is the good old general protection fault (GPF) that you also know from Windows. Maybe it would be better to have NO *emm* style driver loaded by default, as those tend to be hard for "one size fits all" configurations. Modern BIOSes and other hardware and firmware fail to announce reserved areas properly, *emm* enables UMBs, conflict, bang. > When I have no Flash disk inserted it boots ok and the prompt is on drive F: > However, when I enter "keyb gr" I get the error: "JemmEX: exception 06 > occured". So maybe some "on-demand BIOS module for USB flash storage" is one of those UMB conflict cases? But something else goes wrong with the keyb driver as well - again, please try if skipping JEMMEX solves both :-) Note that your BIOS typically decides about modules only at boot time. > Further drive F: is called "FD11Setup". Drive A: is "FDOS11Setup". Now, when Eric -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
> ... Now, when I load DOSUSB and then "devload usbdisk.sys" the > block device driver usbdisk.sys will get the drive letter F: from > FreeDOS. Apparently it does not supply the next drive letter which > would be G:. I can then access the flash disk as F:, but "FD11Setup" > is gone. If you use DEVLOAD to load your block device driver, then obviously it is DEVLOAD which assigns the drive, not DOS. And DEVLOAD's ignorance of non-block device CDS entries is a bug already discussed elsewhere. Wait for the DEVLOAD developers to release a version (3.24?) with that bug fixed. Alternatively, implement a proper regular executable (as opposed to device driver) and modify the CDS and (E)DPBs and device chain yourself as necessary. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
I did a test of this CD too. First I would suggest to make an El-Torito hard
disk instead of using ISOLinux. DOS I feel should boot directly and not by
booting a version of Linux first. I did my LifeCDs with FreeDOS just as an
El-Torito hard disk with 10MB.
Then I have to mention that I cannot read the menu within 5 seconds and
decide what to select. After 5 seconds the menu will run automatically into
the install FreeDOS on hard disk branch. And then wait forever to select the
language. Therefore I would suggest to have no menu selection to be run
automatically. Today, most people may use the CD to boot FreeDOS on a
Windows7 PC and they do not want to install FreeDOS on the NTFS disk.
When I select "Use FreeDOS as LiveCD system.." and have a Flash disk
inserted, the El-Torito Bootable CD-Rom driver results in the error:
"JemmEX: exception 0D occured".
When I have no Flash disk inserted it boots ok and the prompt is on drive F:
However, when I enter "keyb gr" I get the error: "JemmEX: exception 06
occured".
Further drive F: is called "FD11Setup". Drive A: is "FDOS11Setup". Now, when
I load DOSUSB and then "devload usbdisk.sys" the block device driver
usbdisk.sys will get the drive letter F: from FreeDOS. Apparently it does
not supply the next drive letter which would be G:. I can then access the
flash disk as F:, but "FD11Setup" is gone.
The next menu option ("Boot into LiveCD system") will display the message
"SHSUCDX could not detect any drives". When I enter "keyb gr" it returns
"bad command or file name"
The next menu option ("Load liveCD system without drivers") will boot ok
with the same flash disk inserted and the command prompt will show G:
If I then enter "keyb gr" to get German keyboard support the keyboard driver
will crash with "illegal opcode".
When I enter "menu" as instructed, FreeDOS returns "bad command or file
name" - so it does not find the menu command.
By the way this option selects option 5 on the next menu which does not show
that as a valid (or documented) option.
Georg
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 2-8-2011 14:28, dos386 schreef: > [-1.] it does install files (with some luck) but doesn't update the > bootsector, attempt to launch my new FreeDOS ends up > in "NTLDR missing" > > [0.] (see shot) "no persistent changes possible" is strange > > [1.] (see shot) should be "volume" not "drive" (M$-$lang $uck$), what's worse, >it just shows me 4 letters with NO information on them (location of the >volumes, fs (FAT16/FAT28/Former-EX-FAT-64), total size, free space, >existing files or OS, ...), even worse, ot offers me letters > already having >an OS or those having ZERO free space ... > [6.] about the bootsectors, it should tell me what OS I'm about to >kill (as far as guessable) and backup the original BS. Also, it should >tell me about installing onto a non-ZERO'th HD (needs to adjust >BIOS boot settings) or non-ZERO'th partition (needs to adjust the >$80-boot flag in boot sector) I've singled out all bootsector related stuff above for the reason that I haven't got a clue as to where to write the bootsector to, and how system files should be generated. Suppose I'm installing from USB disk (C:) to FAT primary partition on harddisk (D:), then it's implied I should write to D:\ and nothing to C:. Also paths should refer to C:\FDOS instead of D:\FDOS as when I boot from harddisk, currently D: will become C: Perhaps [ http://www.bttr-software.de/products/drvexch/ ] will help, though documentation seems to state C: can't be swapped This same situation occurs if your E: is a primary partition..do you want E:'s bootsector (thus allowing E: to become C: if you boot from that primary partition, possibly hiding or shifting other partitions) and startup files written to there as well? Or still write to what's currently C: ? I at least assume that the *active* primary FAT partition will be C: (unless USB flash disk is C: through USB emulation). Anyway, bootsectors, partitions, drives and startup files are doing my head in :) -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 2-8-2011 14:28, dos386 schreef: > Test of "1.1test3" CD : > > http://jafile.com/uploads/dos386/fd11t3.png Now that's some quite usable feedback, thank you very much DOS386. > > Issues: > > [-3.] many messages running over the screen but too fast to read Yeah file info from LSM files is displayed. Unfortunately the old installer wasn't smart enough to start on a new line after the DESCRIPTION part. You won't see this in the next installer anymore though as it's more limited (not handling individual packages and descriptions anymore, only entire sets). > [-2.] not prominently documented what's going to be installed (for >example "FreeDOS distro 1.1test3 2011-07-10 with kernel 2040 >2011-06-26 and FreeCOM 0.81pl999 2002-12-31" Good point, not even sure which old INSTALL textfile it is, would have to research that if it's worthwile changing. As soon as the new installer supports 'switch to target directory after installation' I'll swap the old installer out (though I'll have to document the syntax and inner workings for it somewhere as it's pretty cryptic). > [-1.] it does install files (with some luck) but doesn't update the > bootsector, attempt to launch my new FreeDOS ends up > in "NTLDR missing" I'll have to look into how to deal with bootsectors anyway. Right now all SYS actions are commented out with exception for the 'FORMAT a partition from FreeDOS menu'. I'm not sure how to handle this at all. Generating bootsectors of the current operating system, of FreeDOS and of Syslinux all seem like good ideas. Actually writing these bootsectors from saved file to bootsector-area is an entirely different matter, I require a SYS with full capabilities [ described at http://www.freedos.org/kernel/sys.txt ] as is located in A:\FREEDOS\SYS.COM in the 1.0 distro (FDBOOT.IMG). Even then it's a question of 'is SYS simply writing 512 bytes, or is it analyzing the bootsector and patching in geometry data properly?' It's an issue I'm currently experiencing with that ReactOS loader bootdisk and its 16KB clustersize which I fail to reduce (using NFORMAT or FDFORMAT). How do I find a bootsector that I can safely override? I don't know what MS FORMAT puts there by default, nor what FreeDOS FORMAT puts there. In ideal case I could dump the bootsector to disk, followed by a search for 'NO OPERATING SYSTEM FOUND'. Any succesful search of this string and I'd be safe to overwrite. > [0.] (see shot) "no persistent changes possible" is strange That's likely for the LiveCD, and doesn't consider any other FAT volumes in your system (be they floppy, usb flash drives or harddisk partitions). I'll see if I can rephrase this somehow. > > [1.] (see shot) should be "volume" not "drive" (M$-$lang $uck$), what's worse, >it just shows me 4 letters with NO information on them (location of the >volumes, fs (FAT16/FAT28/Former-EX-FAT-64), total size, free space, >existing files or OS, ...), even worse, ot offers me letters > already having >an OS or those having ZERO free space ... It gets mighty interesting to use 4DOS with all of its scriptability at this time, or FDISK /INFO. Ideally you'd see: [Drive:] - [Label] [Total capacity][Used Capacity][Free Capacity] and maybe even some filesystem info (FAT12/16/32), primary partition or logical, etc. > [2.] (see shot) Marginally outdated As mentioned, once old installer supports switching to target directory, I'll use that. Meanwhile everyone can test it already, simply start SETUP with a dummy argument, or a valid directory name which contains the [DRIVE:\DIRNAME]PACKAGES\BASE\*.ZIP structure: D:\SETUP.bat C:\FDSETUP > [3.] (see shot) Subminor text formatting problems See above, i could maybe reformat layout. Otherwise a change in INSTALL.EXE required > > [4.] (see shot) many packages need multiple reconfirmations per piece ??? Numerous ENTER and SPACE required with the old installer indeed. New installer will no longer be bothered by this issue. > [5.] (see crappy shot) about to reboot ... into "NTLDR missing" Ah that's a nice string to search for. I guess Eric's OSCHECK can help a bit as well. > [6.] about the bootsectors, it should tell me what OS I'm about to >kill (as far as guessable) and backup the original BS. Also, it should >tell me about installing onto a non-ZERO'th HD (needs to adjust >BIOS boot settings) or non-ZERO'th partition (needs to adjust the >$80-boot flag in boot sector) I've no idea what that last bit means, but your initial part looks good. I'd assume it's perfectly safe to overwrite/update a FreeDOS installation while having to ask around for the other options. Alternatively I'll be real annoying and simply install SYSLINUX and let its multiboot capabilities sort things out. Thanks for your feedback, the screenshots help quite a lot in visualising what flaws might be experienced.
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Test of "1.1test3" CD : http://jafile.com/uploads/dos386/fd11t3.png Issues: [-3.] many messages running over the screen but too fast to read [-2.] not prominently documented what's going to be installed (for example "FreeDOS distro 1.1test3 2011-07-10 with kernel 2040 2011-06-26 and FreeCOM 0.81pl999 2002-12-31" [-1.] it does install files (with some luck) but doesn't update the bootsector, attempt to launch my new FreeDOS ends up in "NTLDR missing" [0.] (see shot) "no persistent changes possible" is strange [1.] (see shot) should be "volume" not "drive" (M$-$lang $uck$), what's worse, it just shows me 4 letters with NO information on them (location of the volumes, fs (FAT16/FAT28/Former-EX-FAT-64), total size, free space, existing files or OS, ...), even worse, ot offers me letters already having an OS or those having ZERO free space ... [2.] (see shot) Marginally outdated [3.] (see shot) Subminor text formatting problems [4.] (see shot) many packages need multiple reconfirmations per piece ??? [5.] (see crappy shot) about to reboot ... into "NTLDR missing" [6.] about the bootsectors, it should tell me what OS I'm about to kill (as far as guessable) and backup the original BS. Also, it should tell me about installing onto a non-ZERO'th HD (needs to adjust BIOS boot settings) or non-ZERO'th partition (needs to adjust the $80-boot flag in boot sector) -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Hi, On Thu, Jul 28, 2011 at 2:09 PM, Bernd Blaauw wrote: > Op 28-7-2011 4:02, Jim Michaels schreef: > >> is there a way you can selectively choose what parts you want to >> install? like >> "select all" but uncheck arachne, lynx, and bobcat? >> >> could you add cURL for DOS? > > Currently used old installer is still selective, though through a lot of > user interaction. If I can find a usable binary of CURL I might add it. > I'm already disliking the filesize for base distribution, but as I'm > required to add sources I might as well increase size by adding WGET, > CURL etc :) Here's all the basic URLs to grab cURL (that I know of): == > they [DOS binary] are available here. > http://www.rahul.net/dkaufman/index.html I've never used cURL, but apparently latest is 7.21.7. I blindly wonder if it'll still compile with DJGPP + WATT-32 (too preoccupied to personally try right now, doh). Anyways, here's link to srcs for 7.10.5 (cURL it? heh): ftp://ftp.sunet.se/pub/www/utilities/curl/curl-7.10.5.tar.bz2 Official site is here: http://curl.haxx.se/ http://curl.haxx.se/download/curl-7.21.7.tar.bz2 Watt-32 (new) homepage seems to be here: http://home.broadpark.no/~gvanem/ -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Hi, On Thu, Jul 28, 2011 at 2:20 PM, Bernd Blaauw wrote: > Op 28-7-2011 4:30, Jim Michaels schreef: > >> and cdrtools for dos? > > http://sites.google.com/site/blairdude/cdrkit contains CDRKIT v1.1.9 > I'm not aware of any recent DOS CDRTOOLS ports. Old one is 2.01 > ( http://bootcd.narod.ru/index_e.htm), with CDRTOOLS 3.00 already having > been announced. There were some other unofficial compiles "announced" on BTTR's forum a few months ago, but I never tested (too dumb to know how, honestly!). You could search there if really curious. Or perhaps Jim Hall mirrored some of it to iBiblio, dunno, would have to check. > Trouble also remains the lack of an IDE ASPI driver for CD-writing, > above mentioned site offers a vendor's ASPI driver, but ofcourse the > legal situation is shady. Right, that alone might make the whole idea questionable at best (sadly). :-( -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 28-7-2011 4:30, Jim Michaels schreef: > and cdrtools for dos? http://sites.google.com/site/blairdude/cdrkit contains CDRKIT v1.1.9 I'm not aware of any recent DOS CDRTOOLS ports. Old one is 2.01 ( http://bootcd.narod.ru/index_e.htm), with CDRTOOLS 3.00 already having been announced. Trouble also remains the lack of an IDE ASPI driver for CD-writing, above mentioned site offers a vendor's ASPI driver, but ofcourse the legal situation is shady. -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
Op 28-7-2011 4:02, Jim Michaels schreef: > is there a way you can selectively choose what parts you want to > install? like > "select all" but uncheck arachne, lynx, and bobcat? > > could you add cURL for DOS? Currently used old installer is still selective, though through a lot of user interaction. If I can find a usable binary of CURL I might add it. I'm already disliking the filesize for base distribution, but as I'm required to add sources I might as well increase size by adding WGET, CURL etc :) -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
and cdrtools for dos? - Jim Michaels jmich...@yahoo.com j...@jimscomputerrepairandwebdesign.com http://JimsComputerRepairandWebDesign.com http://JesusnJim.com (my personal site, has software) --- Computer memory/disk size measurements: [KB KiB] [MB MiB] [GB GiB] [TB TiB] [10^3B=1,000B=1KB][2^10B=1,024B=1KiB] [10^6B=1,000,000B=1MB][2^20B=1,048,576B=1MiB] [10^9B=1,000,000,000B=1GB][2^30B=1,073,741,824B=1GiB] [10^12B=1,000,000,000,000B=1TB][2^40B=1,099,511,627,776B=1TiB] Note: disk size is measured in MB, GB, or TB, not in MiB, GiB, or TiB. computer memory (RAM) is measured in MiB and GiB. > >From: Jim Michaels >To: "freedos-devel@lists.sourceforge.net" >Sent: Wednesday, July 27, 2011 7:02 PM >Subject: Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released > > >is there a way you can selectively choose what parts you want to install? >like > >"select all" but uncheck arachne, lynx, and bobcat? > > >could you add cURL for DOS? > > >- >Jim Michaels >jmich...@yahoo.com >j...@jimscomputerrepairandwebdesign.com >http://JimsComputerRepairandWebDesign.com >http://JesusnJim.com (my personal site, has software) >--- >Computer memory/disk size measurements: >[KB KiB] [MB MiB] [GB GiB] [TB TiB] >[10^3B=1,000B=1KB][2^10B=1,024B=1KiB] >[10^6B=1,000,000B=1MB][2^20B=1,048,576B=1MiB] >[10^9B=1,000,000,000B=1GB][2^30B=1,073,741,824B=1GiB] >[10^12B=1,000,000,000,000B=1TB][2^40B=1,099,511,627,776B=1TiB] >Note: disk size is measured in MB, GB, or TB, not in MiB, GiB, or TiB. >computer memory (RAM) is measured in MiB and GiB. > > > > >> >>From: Bernd Blaauw >>To: freedos-devel@lists.sourceforge.net; freedos-u...@lists.sourceforge.net >>Sent: Tuesday, July 26, 2011 8:17 PM >>Subject: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released >> >>I'd like to announce a new FreeDOS 1.1 test CD-image file, see FreeDOS >>website for download details. >> >>I've squashed quite a few bugs which were mentioned in the BugTracker >>that Robert Riebisch linked to. This new release should also be more >>compatible with several emulation and virtualisation products, as well >>as work with being launched from different DOS and CDEX flavors. >> >>The generated configuration setttings have improved as well, with adding >>(commented out) experimental NLS/locale commands in AUTOEXEC.BAT >> >>If you find any obvious flaws please list them in the bugtracker. >> >> >> >>Bernd >> >> >>-- >>Got Input? Slashdot Needs You. >>Take our quick survey online. Come on, we don't ask for help often. >>Plus, you'll get a chance to win $100 to spend on ThinkGeek. >>http://p.sf.net/sfu/slashdot-survey >>___ >>Freedos-devel mailing list >>Freedos-devel@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/freedos-devel >> >> >> >-- >Got Input? Slashdot Needs You. >Take our quick survey online. Come on, we don't ask for help often. >Plus, you'll get a chance to win $100 to spend on ThinkGeek. >http://p.sf.net/sfu/slashdot-survey >___ >Freedos-devel mailing list >Freedos-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/freedos-devel > > >-- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released
is there a way you can selectively choose what parts you want to install? like "select all" but uncheck arachne, lynx, and bobcat? could you add cURL for DOS? - Jim Michaels jmich...@yahoo.com j...@jimscomputerrepairandwebdesign.com http://JimsComputerRepairandWebDesign.com http://JesusnJim.com (my personal site, has software) --- Computer memory/disk size measurements: [KB KiB] [MB MiB] [GB GiB] [TB TiB] [10^3B=1,000B=1KB][2^10B=1,024B=1KiB] [10^6B=1,000,000B=1MB][2^20B=1,048,576B=1MiB] [10^9B=1,000,000,000B=1GB][2^30B=1,073,741,824B=1GiB] [10^12B=1,000,000,000,000B=1TB][2^40B=1,099,511,627,776B=1TiB] Note: disk size is measured in MB, GB, or TB, not in MiB, GiB, or TiB. computer memory (RAM) is measured in MiB and GiB. > >From: Bernd Blaauw >To: freedos-devel@lists.sourceforge.net; freedos-u...@lists.sourceforge.net >Sent: Tuesday, July 26, 2011 8:17 PM >Subject: [Freedos-devel] New FreeDOS 1.1 test ISO (#3) released > >I'd like to announce a new FreeDOS 1.1 test CD-image file, see FreeDOS >website for download details. > >I've squashed quite a few bugs which were mentioned in the BugTracker >that Robert Riebisch linked to. This new release should also be more >compatible with several emulation and virtualisation products, as well >as work with being launched from different DOS and CDEX flavors. > >The generated configuration setttings have improved as well, with adding >(commented out) experimental NLS/locale commands in AUTOEXEC.BAT > >If you find any obvious flaws please list them in the bugtracker. > > > >Bernd > > >-- >Got Input? Slashdot Needs You. >Take our quick survey online. Come on, we don't ask for help often. >Plus, you'll get a chance to win $100 to spend on ThinkGeek. >http://p.sf.net/sfu/slashdot-survey >___ >Freedos-devel mailing list >Freedos-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/freedos-devel > > >-- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
