Re: [Freedos-user] Incompatibility with EMSDSK #3
Hi! DEVICE=C:\DEVS\RDOSUMB.COM #19 * DEVICEHIGH=C:\DEVS\JEMMEX.EXE A20METHOD:FAST FRAME=E000 VERBOSE NOE801 NOE820 NORAM D=0 VCPI DOS=UMB,HIGH DEVICEHIGH=C:\DEVS\EMSDSK.EXE 4364 /c02 ... 6 file(s)101,406 bytes 0 dir(s) 325,632 bytes free Note the reported free value. ... It seems that FreeDOS does not work well with real-mode UMBs, since EMSDSK no longer shows any problems if I rem the first line in CONFIG.SYS and change the NORAM option to RAM. Looking into UMBs (when they are real-mode), I found command.com there, possibly overlapping the EMS frame area. I do not know how command.com came there (try using SHELL instead of SHELLHIGH) but UMBs always cause a risk of using areas of RAM that you should not use. This happens both with real-mode UMBs and with JEMM386 / JEMMEX. You also use very forcing command line options for JEMMEX so maybe you even force it to use areas it should not. This can mean that access to disk/sound/network/USB/... will trigger something which overwrites your UMB, etc. Try finding a suitable X=... option for your JEMMEX and/or suitable options for RDOSUMB (or try UMBPCI) to avoid any problematic areas in your UMB. Note that EMSDSK might be able to work without page EMS frame, giving you more UMB. Eric -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Incompatibility with EMSDSK #3
DEVICE=C:\DEVS\RDOSUMB.COM #19 * DEVICEHIGH=C:\DEVS\JEMMEX.EXE A20METHOD:FAST FRAME=E000 VERBOSE NOE801 NOE820 NORAM D=0 VCPI DOS=UMB,HIGH DEVICEHIGH=C:\DEVS\EMSDSK.EXE 4364 /c02 ... 6 file(s)101,406 bytes 0 dir(s) 325,632 bytes free Note the reported free value. ... It seems that FreeDOS does not work well with real-mode UMBs, since EMSDSK no longer shows any problems if I rem the first line in CONFIG.SYS and change the NORAM option to RAM. Looking into UMBs (when they are real-mode), I found command.com there, possibly overlapping the EMS frame area. If any UMBs (provided by RDOSUMB) overlap the EMS page frame, this is a certain source of errors. Using your current configuration, inspect which areas of the UMA are provided as UMB and whether any of these areas contains or crosses segments E000h to EFFFh (where the 64 KiB large EMS page frame is). One of the MEM options might show you the (hexadecimal) segments and their size. (If you don't know how to look at the segment and size values, send a list of your UMBs with these values to the list.) If I omit the FRAME option in CONFIG.SYS, then I see thismessage during boot: *** EMS RAMdisk v1.9I (FU - 08/98): ems get frame error and EMSDSK does not install. The memory map in this caseshows no EMM0. Note that EMSDSK might be able to work without page EMS frame, giving you more UMB. Apparently not. You might of course try FRAME=NONE first and see if EMSDSK shows the same message. However many other EMS programs don't work without page frame anyway so I won't recommend running such a system. If you don't use any other programs that require EMS, a better option might be to disable EMS completely (JEMM option NOEMS, and remove FRAME=) and replace EMSDSK by XMSDSK (or the open source RDISK, which also runs with XMS). Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] cdrom
Hi, i have installed successfully freedos on Compaq lte 5100 I took the hardisk and connecetd with usb-ide adaptor and with qmeu installed the system on it, not sure if the system neede it fat 16 partition but know it works. My issue is to set the cdrom drive. in fdconfig.sys is one entry 123?DEVICEHIGH=c:\fdos\bin\xcdom.sys /d:FDCD0001 in autoexec.bat put a entry SHCDX86.COM /d:FDCD0001 but he cant find the driver whats wrong. Thx in advance Menuhin http://www.msaitov.de/pgp.htm -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] cdrom
Menuhin Saitov schreef: Hi, i have installed successfully freedos on Compaq lte 5100 I took the hardisk and connecetd with usb-ide adaptor and with qmeu installed the system on it, not sure if the system neede it fat 16 partition but know it works. My issue is to set the cdrom drive. in fdconfig.sys is one entry 123?DEVICEHIGH=c:\fdos\bin\xcdom.sys /d:FDCD0001 Was there a typing error here? as it's normally XCDROM.SYS. As the FreeDOS distribution is rather old right now, I'd recommend getting an updated yet renamed version of the cdrom driver at [ http://johnson.tmfc.net/dos/file/drivers.zip ]. Possibly you'd like a new version of SHSUCDX as well as the 8086-version contained a bug sometime if I remember correctly. [ http://johnson.tmfc.net/dos/file/shcdx33d.zip ] You can see if the UIDE.SYS driver loaded by checking if the FDCD0001 devicename is known to DOS: IF EXIST FDCD0001 ECHO CD-ROM driver loaded, please load SHSUCDX as well to assign a drive letter ( SHSUCDX /D:FDCD0001) Bernd -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Updated RDISK.COM Available.
The RDISK driver is now a .COM file and has been improved. RDISK can still be loaded as-before from CONFIG.SYS, or it can now load from AUTOEXEC.BAT and by user command without needing DEVLOAD. When loaded by AUTOEXEC or later, RDISK can now accept the /:[letter] switch specifying a desired drive letter, e.g. /:Q assigns drive Q: for all RDISK files. Without any /: switch, the next free DOS drive letter is used, as-before. RDISK is a lot more useful and flexible when users can set their own desired drive letters! RDISK still supports from 2-MB to 2-GB of memory and still takes 3 sectors [1536 bytes exactly!] on boot diskettes. RDISK is part of the DRIVERS.ZIP file that is available at johnson.tmfc.net/dos/driver.html -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] cdrom
On Wed, 24 Jun 2009, Bernd Blaauw wrote: Was there a typing error here? as it's normally XCDROM.SYS. YES it was i don't have internet on the laptop. As the FreeDOS distribution is rather old right now, I'd recommend getting an updated yet renamed version of the cdrom driver at [ http://johnson.tmfc.net/dos/file/drivers.zip ]. Possibly you'd like a new version of SHSUCDX as well as the 8086-version contained a bug sometime if I remember correctly. [ http://johnson.tmfc.net/dos/file/shcdx33d.zip ] You can see if the UIDE.SYS driver loaded by checking if the FDCD0001 devicename is known to DOS: IF EXIST FDCD0001 ECHO CD-ROM driver loaded, please load SHSUCDX as well to assign a drive letter ( SHSUCDX /D:FDCD0001) Bernd -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user http://www.msaitov.de/pgp.htm -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] freedos on dosemu.
Of course, if freedos is on dosemu on linux, you may still have the beauty of dos but not the blazing speed; there are search algorithims, etc, that can take *hours* on bloatware, but minutes in dos. The answer is to keep the dos offline; not so strange. I dual boot linux and windows, and go to the extent of *removing* the nic driver from windoze; this because of that always on aspect of ethernet(you have updates available). The filesystem in ubuntu makes it real easy to send and recieve files to/from windows.--kurtwb2...@gmail.com. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
