Re: [Freedos-user] collision between emm386 and memdisk
-- Original message -- From: "m4mach" <[EMAIL PROTECTED]> > hi > [...] > > I use CD-ROM drivers, but don't know how to add programs from CD directory > to PATH variable. (to search for CD label?) > [...] You can specify the drive letter that will be used for your CDROM drive in autoexec.bat. Using shsucdx, you can just assign the starting drive letter as "X" and then use X:\FDOS or whatever in your path statements. See http://help.fdos.org/en/hhstndrd/shsucdx.htm for the "drive" parameter: drive The first CD drive will be assigned to this drive letter, then subsequent drive letters will be used for any other CD drives that are detected. Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] collision between emm386 and memdisk
hi >> If I undestand correctly: I will get the same error if I run any other >> programme which is placed near the end of the floppy image?? memdisk >> is not in the floppy > > I understood that you use memdisk to simulate a floppy in ram. > And that some himem / emm386 / japheth-equivalents had a problem > if the memdisk used more ram. My idea was that the problem only > triggers if you actually use ram of memdisk which somehow over- > laps with what the other drivers use. Can you make a list which > versions of himem / emm386 have the problem? To begin with, I > suggest the categories: 1 fd himem, 2 j himem (himemx), 3 fd emm386, > 4 jemm386, and 5 jemmex. Gives various (8) combinations: 1, 2, 1+3, > 1+4, 2+3, 2+4, 5, none. Question is which of the 8 have problems. Please belive me I'm an ordinary user not developer and don't have a time (and head:)) for searching bugs especially when it works. When it works I'm happy enough and don't want to know why it didn't work yesterday :). If you want I can send you my floppy image, unfortunatelly I don't have a copy of the "non-working" one. My HIMEM/EMM386 versions: 3.26/2.26, jemm version 564, kernel: 1.1.35 >> Well, I need to have all my DOS programs, and it's about 8 MB > > You should just include a cdrom driver to access the rest :-). > Options are: eltorito (if you boot with isolinux and memdisk > only), xcdrom (ide), gcdrom (sata), maybe others. The eltorito > dot sys driver from www.nu2.nu/eltorito/ is interesting. If > you like it, you should remind Bart to open-source it ;-). You > also need a high level driver for any cdrom drivers. In MSDOS, > it is called mscdex. We use shsucdx instead. I use CD-ROM drivers, but don't know how to add programs from CD directory to PATH variable. (to search for CD label?) Why use eltorito driver? I have xcdrom and it works fine with memdisk, but you suggested eltorito, is it better? m4mach - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] collision between emm386 and memdisk
Thanks Eric I think I will make some menu to let the user decide which manager have to be loaded, but as I see, there isn't good menu system in FreeDOS. I mean, there is only option to have one level in menu. I need more than one (for memory managers, some USB drivers, language etc).. Is there any way to have more menu levels? >Probably because you accessed fewer sectors near the end then If I undestand correctly: I will get the same error if I run any other programme which is placed near the end of the floppy image?? memdisk is not in the floppy >Another way might be to tell MEMDISK to simulate a harddisk instead >of a floppy. Note that that will modify the drive numbering for DOS. Yes, I've tried. You're right with drive number. I will stay with FAT12 and floppy. But does FAT12 make all filenames UPPERCASE? >Of course the question is: Why do you need an image above 2.88 MB at all? Well, I need to have all my DOS programs, and it's about 8 MB sorry for my english :) m4mach - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] collision between emm386 and memdisk
m4mach schreef: > hi all > > I have a problem running FreeDOS with himem/emm386 on a custom size floppy > image (8640 kB) I use memdisk to emulate the floppy. > Is a (compressed?) version of your floppy image available? don't need the full contents (might be proprietary parts), just the FreeDOS related parts. If you prefer, you can mail it to me, or make it somewhere available on a webserver. > I've tested 4 situations: > > 1. kernel on 2880 kB floppy image = works > 2. kernel on 8640 kB floppy image = works > 3. kernel + himem/emm386 on 2880 kB floppy = works > 4. kernel + himem/emm386 on 8640 kB floppy = ERROR > Which kernel exactly? the FreeDOS 1.0 kernel with support for pre-i80386 processors and FAT32? Also which versions of EMM386 and HIMEM? Latest development versions are available from Japheth's website ( http://www.japheth.de/Jemm.html ), it might be worthwile trying those :). Also which Syslinux flavor are you using? (syslinux, isolinux, extlinux, pxelinux?), which version of it and which Memdisk version? > In 4th situation the system hangs (freezes) just after emm386 shows all > inforamtions about memory he found , there is no any error - everything > looks fine. I suspect some collision between emm386 and memdisk (as it is > floppy size problem = memory problem). I've tested a lot of himem/emm386 > switches but no luck. > I've seen loading hang occasionally right after the 'Buffers in HMA' message from the kernel. Does loading only the HIMEM program work for you? Pressing F8 allows to skip drivers (singlestepping). > I can add that JEMMEX works fine in all 4 cases, but that is not a solution > I'm looking for. > Why would you not want to use this version? Maybe Japheth would be willing to locate the exact issue between old EMM386 and Memdisk. License is the same for JEMM386 and EMM386, as JEMM386 is a more advanced/developed version of EMM386, based on that same EMM386 (which in turn is a tremendous development achievement by Tom Ehlert and Michael Devore, based on an old driver). > I use the last stable versions of all software (but also tried older > himem/emm386 - without any change) > > I've got some help from memdisk side (mailing list), but without final > solution > Here is my mail, the answer and more details: > http://syslinux.zytor.com/archives/2007-July/008882.html > I'm subscribed there, keeping up with all things related to FreeDOS, ReactOS, Syslinux and Linuxbios :) Anyway, your mail is another reason for releasing an updated FreeDOS sometime, whoever is willing to do so :) Bernd - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
