Re: [Freedos-user] first use of freedos
Hi, On Mon, Nov 4, 2013 at 1:13 AM, John R. Sowden wrote: > > got a 'distribution disk' of freedos Where? Which version? What files? > , ran the sys command. To / from what? Floppy? Hard drive? > copied it from the net to a floppy using ubuntu 13.10 Assuming the floppy is intact, I guess that would work with dd (or similar) if the media size is the same. > put it in a 486 24MB windows 98 computer with the windows programs > removed and the MSDOS 7.10 and 4dos in place, with a network. I assume here that you mean you're replacing MS-DOS with FreeDOS. Was there a particular reason for this, some specific program that wouldn't run or some other restriction? > A few issues: > > Freedos did not like 'sys'ing to the floppy that it resides on, so I > could boot into freedos, What did it say exactly? Did you try a different physical floppy disk? "sys a: c:"? Anyways, you can always boot FreeDOS via other means, hence allowing you to still read / write via FreeDOS on an optional basis. (Heck, the "MS-DOS 8" embedded within DISKCOPY.DLL that you can still write to floppy via Windows explorer [tested on Win7] has no SYS.COM command at all.) > running the ver command shows MD DOS version 7.10. I don't know if > MSDOS is still there or if this is a compatibility issue. I'd sure like > it to say freedos, if it is. The shell may misunderstand, who knows. But "normally" (although I haven't used MS-DOS / Win9x in a few years) I wouldn't expect it to say "MS-DOS" unless it was in fact MS-DOS. Though indeed the FAT32 version of FreeDOS by default always claims to be version 7.10. Well, the obvious answer is to check (or clean) your root directory. If there's only KERNEL.SYS and maybe COMMAND.COM, it's definitely FreeDOS. > Running the defrag program (freedos version) only allowed me to do a > 'quickie'. the real options were grayed out. I have a little dos stuff > (about 130mb) in the middle of this huge 4.3 gb drive. I releived the > drive of its win98 burden. I want the dos at the beginning, and the > unused 'wiped', as the program suggests. Literally in the middle of the partition? How many partitions do you have? FAT16? FAT32? Primary? Active? When you say 4.3 GB, I assume you mean physical drive, not just partition. > Freedos complains that my last drive is not high enough. Where? At bootup? When running a specific program? > It runs, but it stops and waits for a . This will confuse my secty > tomorrow > morning. I assume you mean "secretary"? Sounds like a time crunch, ugh, sorry if this isn't more helpful. Hmmm, you don't mean prompt for date + time do you? It always does that (IIRC) if no AUTOEXEC.BAT is found. > I run a network called "little big lan" (love it). It has a > program to set the last drive called netunits. I have it set to 10. > This computer has a floppy, a hd, and a cd. No more. 10 has been enough > for msdos 7.1 for the last decade. Raising it to 12 had no effect. You mean LASTDRIVE in CONFIG.SYS? No, it sounds like "netunits" (never heard of it). I'm far from experienced in networking, esp. old MS-DOS LAN stuff, but the normal way to increase drives is via LASTDRIVE. Though that's fairly common, so I assume you tried that. But that's all I can think of (and obviously that only uses letters, not numbers). Maybe you meant FILES? Nah, doubt it. > Thoughts? > > John (wordstar 5.5 and foxpro/dos forever!) "Just use Li..." ... Sorry, got carried away there. ;-) -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] first use of freedos
got a 'distribution disk' of freedos, ran the sys command. copied it from the net to a floppy using ubuntu 13.10, put it in a 486 24MB windows 98 computer with the windows programs removed and the MSDOS 7.10 and 4dos in place, with a network. A few issues: Freedos did not like 'sys'ing to the floppy that it resides on, so I could boot into freedos, running the ver command shows MD DOS version 7.10. I don't know if MSDOS is still there or if this is a compatibility issue. I'd sure like it to say freedos, if it is. Running the defrag program (freedos version) only allowed me to do a 'quickie'. the real options were grayed out. I have a little dos stuff (about 130mb) in the middle of this huge 4.3 gb drive. I releived the drive of its win98 burden. I want the dos at the beginning, and the unused 'wiped', as the program suggests. Freedos complains that my last drive is not high enough. It runs, but it stops and waits for a . This will confuse my secty tomorrow morning. I run a network called "little big lan" (love it). It has a program to set the last drive called netunits. I have it set to 10. This computer has a floppy, a hd, and a cd. No more. 10 has been enough for msdos 7.1 for the last decade. Raising it to 12 had no effect. Thoughts? John (wordstar 5.5 and foxpro/dos forever!) -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Vim is slow
Hi again, On Sun, Nov 3, 2013 at 9:21 AM, Miguel Garza wrote: > I'm playing with vim in FDOS. It's nice, but a bit slow in some respects, > particulary when using its internal file-browser. What internal file-browser? LIST? PG? MORE? EDIT? I have no idea, you have to be more specific, there are too many pieces. > I am running FDOS from a > thumbdrive on a modern (well, only a few years old) computer. I added > "DEVICE=...himemx.exe" to my config.sys file to fix a separate issue, which > worked for that issue, but not for vim's slowness. Any ideas? I don't actively use VIM. It's a great tool, though, and most people (e.g. new://comp.editors) seemed to heavily prefer it over anything else. Unfortunately, 7.2 dropped support for 16-bit DOS and 7.4 dropped DOS (DJGPP) entirely. (Though no huge surprise, they weren't ever really interested. They still shipped CWSDPMI r4 years and years after r5 and r7 were out, heh.) I don't know if VIM itself is slow for what you're trying to do or if it really is just your setup being less than optimal. In fact, maybe try deleting (r4) CWSDPMI.EXE if that's in the same subdir as VIM.EXE, as it will actually use that by default if found. r7 can be much faster (e.g. 2x) on modern machines (4 MB pages). I don't normally use vi for editing. Okay, I do use it semi-frequently, but mostly I prefer TDE, just an old habit. I do use VILE a lot on Linux (since the TDE build has keyboard issues there). The DJGPP version is very very nice too, though it's not quite as advanced as VIM in some ways (e.g. syntax highlighting). I only use that rarely in DOS (e.g. VirtualBox, more keyboard bugs, heheh) though it's great. It's not slow at all, and it's (also) way more than just a minimal vi clone. In fact, it's roughly based upon MicroEmacs, so it supports a lot of stuff that most "extended" vi clones support (multiple buffers, windows, highlighting, etc). There aren't a lot of other good DOS vi clones. Well, Elvis is only a 16-bit version, same with the XVI build I found a while back, same with SteVIe. Unlikely that I would even pretend you should switch to those (unless your setup needed it, of course). Okay, well GNU Emacs has Viper (and 23.3 binaries exist for DJGPP), but that's probably overkill (180 MB??) for what you want. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Vim is slow
Hi, On Sun, Nov 3, 2013 at 9:54 AM, Bernd Blaauw wrote: > Miguel Garza schreef op 3-11-2013 16:21: >> >> I'm playing with vim in FDOS. It's nice, but a bit slow in some >> respects, particulary when using its internal file-browser. I am running >> FDOS from a thumbdrive on a modern (well, only a few years old) >> computer. I added "DEVICE=...himemx.exe" to my config.sys file to fix a >> separate issue, which worked for that issue, but not for vim's slowness. >> Any ideas? > > USB Flash Drives can be pretty slow for reads/writes that are > non-sequential in nature, just like harddisks. What you could do is try > to run a cache-driver like LBACACHE, or to install a ramdisk driver and > copy files over to the created ramdisk. SHSURDRV is such a ramdisk > driver, so is RDRV (part of UIDE/UDVD driver collection) Indeed, the flash drive is probably the main culprit, it's very slow for writes. The best solution I've found is to use both cache and RAM disk. At bootup, copy the most frequently used utils to the RAM drive and put that in your PATH. That's what I do when I boot up my RUFUS-installed FreeDOS USB drive (though I native boot on my desktop much more frequently, to be honest, it's just easier). Just for the record, the speed goes from fastest to slowest with various media: RAM drive, hard drive, CD drive, USB drive, floppy drive. Okay, that's a rough guess, I haven't fully benchmarked them all, but for sure RAM is faster than anything, so even with a cache loaded (see below), it's still not as fast as cache + RAM disk. http://www.mail-archive.com/freedos-user@lists.sourceforge.net/msg13098.html Long story short: download Jack's DRIVERS.ZIP (or similar) and use XMGR.SYS (XMS), UIDE.SYS (cache) and RDISK.COM (RAM drive) and copy flash drive's C:\UTILS to RAM drive's G:\UTILS and put that in the PATH. Of course, if you want to save anything for later use, you'll still have to manually do that (to flash drive) before shutdown. Honestly, it may be more user friendly (for you) to just install PuppyLinux to USB and run DOSEMU. At least it saves your changes automatically. Though Fedora liveUSB may work too (persistent changes), but I haven't really tried since old F14 (and DOSEMU isn't in their repos, gotta get it manually). Well, RUFUS may be too minimal by default. Maybe FreeDOS needs a better (public) example (or ten) of different setups (autoexec.bat, config.sys). But I think RUFUS does optionally allow you to install the full FD 1.1 distro. (UNetBootIn does too but doesn't save changes.) Well, either way, it's a lot of manual tweaking since everybody is different. I know this isn't a perfect answer by any means, but hopefully it gives you some idea. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
Hi again, On Sun, Nov 3, 2013 at 4:07 PM, Rugxulo wrote: > > AFAIK, the %PATH% can (normally) only be 128 bytes or less. This is > also part of the overall environment limit (but what is default for > FreeCOM, /E:256 ??). There are possible partial workarounds that > extend it to 255 or such (e.g. 4DOS or Win9x via %CMDLINE%), I think, > but I've never messed with them much, so I don't know the details. > Other OSes have similar cmdline limits (e.g. 1000 or 8000, dunno) but > hide it better. DJGPP just uses response files (esp. behind the > scenes) to get approx. 12000 since so many Linux progs assume > virtually unlimited and try to cram too much raw info there (IMO). Sorry, I'm confusing PATH_MAX and size of environment and cmdline limits. These are really completely different things but often tied together for various reasons. So a response file has nothing to do with the %PATH%, per se, but trying to run anything in your %PATH% (or otherwise) assumes a certain length (as FPC's experimental 16-bit target work showed us on BTTR). I guess I was weakly trying to make a point, saying that everything has limits, even if we think they are virtually "unlimited". -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
Hi, On Sun, Nov 3, 2013 at 9:38 AM, Miguel Garza wrote: > > I've got my programs in subdirectories of C:\APPS, and whenever I add a new > program, I have to add its path to autoexec.bat like so: > > set PATH=.;c:\;\LOCALE;\APPS;[all the other paths to the other programs in > the APPS folder];\APPS\NEWPROG > > But now FDOS is telling me my PATH is too long and PATH isn't working. So I > took some of the paths off the end that I just added, and now PATH is > parsed. But is there any way I can have more paths in my PATH? AFAIK, the %PATH% can (normally) only be 128 bytes or less. This is also part of the overall environment limit (but what is default for FreeCOM, /E:256 ??). There are possible partial workarounds that extend it to 255 or such (e.g. 4DOS or Win9x via %CMDLINE%), I think, but I've never messed with them much, so I don't know the details. Other OSes have similar cmdline limits (e.g. 1000 or 8000, dunno) but hide it better. DJGPP just uses response files (esp. behind the scenes) to get approx. 12000 since so many Linux progs assume virtually unlimited and try to cram too much raw info there (IMO). Anyways, what nobody mentioned so far is SUBST, which is "probably" the solution you're looking for. But again, like they said, you really shouldn't have a hard need for literally everything in your %PATH%, only those that you use often. In fact, it's best to keep it fairly minimal by default in order to avoid clashes with similarly-named (but functionally different) utils. As mentioned, using .BATs to temporarily enable and disable various setups is a better way. http://help.fdos.org/en/hhstndrd/base/swsubst.htm -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
On Sun, Nov 3, 2013 at 10:38 AM, Miguel Garza wrote: > I've got my programs in subdirectories of C:\APPS, and whenever I add a new > program, I have to add its path to autoexec.bat like so: > > set PATH=.;c:\;\LOCALE;\APPS;[all the other paths to the other programs in > the APPS folder];\APPS\NEWPROG > > But now FDOS is telling me my PATH is too long and PATH isn't working. So I > took some of the paths off the end that I just added, and now PATH is > parsed. But is there any way I can have more paths in my PATH? You're running into a DOS limit on the length of an environment string. I assume \APPS is the top level directory, and each program is installed in a sub-directory of it. Every time you add a new program, you add another directory to your path. One question is whether they all *need* to be in separate directories? Most of the stuff I have in FreeDOS does not need to be: the programs are EXE files that can all be in a \DOS (or whatever) directory. I just have \DOS in my PATH for all of them. If an application is more complex and needs it's own directory, don't put it in the PATH. That's what batch files are for. I have a \BATCH directory in my PATH where batch files live. To run one of those programs, I do it through a batch file, like @echo off :: foobar.bat - run foobar application under FDOS c: set FOOBARHOME=c:\opt\foobar cd \opt\foobar foobar %1 exit Because \BATCH is in my PATH, when I type "foobar test" on the command line, DOS will find and run foobar.bat and pass it "test" as a parameter. DOS looks in what it thinks is the current directory first when you pass it a program name on the command line, so the batch file changes to the proper directory and runs the program. The batch file can also do other things the program might need, like defining environment variables and passing parameters on the command line. __ Dennis -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
Or try runme.bat path program.exe Echo off Cd %1 %2 :exit On Sunday, November 3, 2013, Bernd Blaauw wrote: > Miguel Garza schreef op 3-11-2013 16:38: > > But now FDOS is telling me my PATH is too long and PATH isn't working. > > So I took some of the paths off the end that I just added, and now PATH > > is parsed. But is there any way I can have more paths in my PATH? > > Perhaps MSDOS or 4DOS allowed longer paths, not sure about > FreeDOS/FreeCOM. An alternative solution would be to write an individual > batchfile for each program you'd like to run, and place these batchfiles > somewhere in C:\DOS or so. > > @echo off > C: > CD \ > CD PROGRAMS > CD APPS > CD MYPROG > MYPROG.EXE > CD \ > > > > -- > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
Thanks to you both! On Sun, Nov 3, 2013 at 10:07 AM, Matej Horvat wrote: > On Sun, 03 Nov 2013 16:57:50 +0100, Bernd Blaauw wrote: > > An alternative solution would be to write an individual > > batchfile for each program you'd like to run, and place these batchfiles > > somewhere in C:\DOS or so. > > > > @echo off > > C: > > CD \ > > CD PROGRAMS > > CD APPS > > CD MYPROG > > MYPROG.EXE > > CD \ > > I use a similar solution, but more elegant (IMO). Make a batch file for > each program in C:\APPS like this: > > @PUSHD C:\APPS\PROGRAM > @PROGRAM.EXE > @POPD > > This way, you can call it from anywhere without having it change your > current directory. > > BTW, I think it is redundant to have ".;" in your PATH, as DOS always > searches the current directory first. > > > -- > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
On Sun, 03 Nov 2013 16:57:50 +0100, Bernd Blaauw wrote: > An alternative solution would be to write an individual > batchfile for each program you'd like to run, and place these batchfiles > somewhere in C:\DOS or so. > > @echo off > C: > CD \ > CD PROGRAMS > CD APPS > CD MYPROG > MYPROG.EXE > CD \ I use a similar solution, but more elegant (IMO). Make a batch file for each program in C:\APPS like this: @PUSHD C:\APPS\PROGRAM @PROGRAM.EXE @POPD This way, you can call it from anywhere without having it change your current directory. BTW, I think it is redundant to have ".;" in your PATH, as DOS always searches the current directory first. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PATH
Miguel Garza schreef op 3-11-2013 16:38: > But now FDOS is telling me my PATH is too long and PATH isn't working. > So I took some of the paths off the end that I just added, and now PATH > is parsed. But is there any way I can have more paths in my PATH? Perhaps MSDOS or 4DOS allowed longer paths, not sure about FreeDOS/FreeCOM. An alternative solution would be to write an individual batchfile for each program you'd like to run, and place these batchfiles somewhere in C:\DOS or so. @echo off C: CD \ CD PROGRAMS CD APPS CD MYPROG MYPROG.EXE CD \ -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Vim is slow
Miguel Garza schreef op 3-11-2013 16:21: > I'm playing with vim in FDOS. It's nice, but a bit slow in some > respects, particulary when using its internal file-browser. I am running > FDOS from a thumbdrive on a modern (well, only a few years old) > computer. I added "DEVICE=...himemx.exe" to my config.sys file to fix a > separate issue, which worked for that issue, but not for vim's slowness. > Any ideas? USB Flash Drives can be pretty slow for reads/writes that are non-sequential in nature, just like harddisks. What you could do is try to run a cache-driver like LBACACHE, or to install a ramdisk driver and copy files over to the created ramdisk. SHSURDRV is such a ramdisk driver, so is RDRV (part of UIDE/UDVD driver collection) Bernd -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] PATH
I've got my programs in subdirectories of C:\APPS, and whenever I add a new program, I have to add its path to autoexec.bat like so: set PATH=.;c:\;\LOCALE;\APPS;[all the other paths to the other programs in the APPS folder];\APPS\NEWPROG But now FDOS is telling me my PATH is too long and PATH isn't working. So I took some of the paths off the end that I just added, and now PATH is parsed. But is there any way I can have more paths in my PATH? -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Vim is slow
I'm playing with vim in FDOS. It's nice, but a bit slow in some respects, particulary when using its internal file-browser. I am running FDOS from a thumbdrive on a modern (well, only a few years old) computer. I added "DEVICE=...himemx.exe" to my config.sys file to fix a separate issue, which worked for that issue, but not for vim's slowness. Any ideas? PS An update: I'd asked abt Pictview not loading more than a few lines of images files before failing with a memory msg, and was told how to load himemx at that time. Believe it or not, at the time I was a little overwhelmed by what was needed for troubleshooting. But when I did try it just now, to try and fix the vim issue actually, it worked flawlessly for the Pictview issue. Also, Pictview is able to display Photoshop files (.psd) as advertised, and PNG files too. And fast. Pretty amazing. On Thu, Oct 17, 2013 at 2:47 AM, wrote: From: Rugxulo To: "Discussion and general questions about FreeDOS." < freedos-user@lists.sourceforge.net> Cc: Date: Wed, 16 Oct 2013 23:15:26 -0500 Subject: Re: [Freedos-user] emm386, himem.sys, config.sys The FAQ says this: "PictView is written mainly in assembler and it runs on any 386 machine with at least 1 MB of RAM and a VGA adapter." Though it goes on to mention XMS, which sounds correct (though I admit to only rarely running pictview.exe as I'm no multimedia buff). So no, that's not EMS, so you don't need EMM386 at all, AFAIK. You only need the equivalent of HIMEM.SYS (usually HIMEMX or XMGR or FDXMS or similar). The file "jemmex.exe" contains "himemx.exe + jemm386.exe", but I'm not sure that's what you want either. So yeah, like Louis said, put "DEVICE=c:\fdos\himemx.exe" or "DEVICE=c:\fdos\xmgr.sys" in your CONFIG.SYS and try again. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
