Re: [Freedos-user] MetaDOS floppy distro - XFDOS - DOS4WIN64 Qemu environment
Georg Potthast schreef op 7-12-2014 om 12:51: Without my included XFDOS ISO image this package is just about 5 MB in size. So if you have a DOS application that you want to make available for Windows 7 or 8 in 64 bit mode you could add this to the MetaDOS image in this package and allow your users to run it on Windows 7 or 8 without installing any additional emulation packages. If there is a FAT disk available, this can be accessed directly from MetaDOS if configured. http://qemu.weilnetz.de/ contains more recent binaries for QEMU for Windows, but the syntax for specifying files and options might be different. If only they had binaries that were 8.3-compliant and allowed read-only environment (no temp files, log files, etc) you could add QEMU/Bochs to CD with FreeDOS. For bochs, specifying an ISO that loads a writeable harddisk image works. Specifying a harddisk image doesn't work as you can't indicate read-only harddisk, only CD and floppy. Thanks for making this available Georg. Bernd -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Load file sys driver in dconfig.sys?
Ray Davison schreef op 4-5-2014 01:29: Is it possible to load an exe file system driver in dconfig.sys? I have a DOS HPFS driver that works OK, but I would like it to get a drive letter before the DVDs. I don't see why you'd have to load your EXE-driver in CONFIG.SYS then, considering the CDROM load process: 1) load cd-driver in (fd/d)config.sys 2) load exe-filesystem driver in autoexec.bat 3) load CDEX driver to assign driveletter(s) to CD drive(r) but to answer your question, CONFIG.SYS has an INSTALL= line (just like DEVICE= ) and otherwise you can still use a program like DEVLOAD. SHSUCDX has great flexibility for assigning driveletters to optical drives, using the /L:x option or other more complex options. Bernd -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UPX or not UPX FreeDOS programs/TSRs?
Frantisek Hanzlik schreef op 4-5-2014 11:17: Hi all more experienced, I'm trying to revise and update dosemu-freedos package (subset of FreeDOS stuff used in DOSEMU usual installation) and I'm not sure, what is better - whether packaged programs by UPX or not. Actual dosemu-freedos-1.0-bin.tgz contains 40+ binaries, roughly half of them is packed with UPX - generally as FreeDOS program maintainers did. And I'm not sure, what is optimal, use UPX or not. On some binaries it cause significant space reduction - e.g. 'display.exe' 0.13b has 62535 Byte, and UPXed has only 3651 Byte. On other hand - at current disks sizes few (dozen or hundred) kB is nothing, and UPX packaging has perhaps its own disadvantages - and maybe especially with TSRs (as 'display.exe' is) this may lead to memory fragmentation(?). Thus, what is Your opinion on the use of UPX? Thanks, Franta Hanzlik Runtime programs are usually safe to compress, drivers/TSRs can be tricky as you already indicate, which is a great reason not to compress DISPLAY program. I'd leave it as is right now (unless you're working with some very space-limited bootdisk or so, where every file is essential and any issues will show up very fast because of that exact reason). Bernd -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Load file sys driver in dconfig.sys?
Dale E Sterner schreef op 4-5-2014 17:33: What does an HPFS driver do? Access to the Apple Macintosh / MacOS / OSX operating system's filesystem, just as NTFS is associated with Microsoft Windows cheers DS On Sat, 03 May 2014 16:29:32 -0700 Ray Davison ray...@charter.net writes: Is it possible to load an exe file system driver in dconfig.sys? I have a DOS HPFS driver that works OK, but I would like it to get a drive letter before the DVDs. What is available for reading NTFS used in WXP, W7? TY Ray - - Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user FREE Stock Report How to Invest in the $70 Billion Bottled Water Boom http://thirdpartyoffers.juno.com/TGL3165/53665a5a29c7b5a590943mp06duc ** From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - Geen virus gevonden in dit bericht. Gecontroleerd door AVG - www.avg.com Versie: 2014.0.4577 / Virusdatabase: 3931/7439 - datum van uitgifte: 05/04/14 -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Load file sys driver in dconfig.sys?
Matej Horvat schreef op 4-5-2014 17:53: No, the Mac OS file systems are HFS and HFS+ (and MFS if you're vintage). HPFS is the OS/2 file system. Oops, I stand corrected. Thanks! Also for eComStation then I suppose, or whatever the name nowadays is. Bernd -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Other File systems for FreeDOS?
If you mean besides FAT(12/16/32), ISO9660 (level 1) can be read thanks to SHSUCDX. sparky4 schreef op 2-2-2014 20:16: any other Files systems that FreeDOS can read and write? or have it's own? -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New 12-Jan-2014 UIDE, With 4 Caches!
dmccunney schreef op 8-1-2014 12:43: I did not miss his point. I suggested a technique he could use to soak up *some* of his system memory. I'm quite aware DOS and DOS apps can't use *all* of it, and that 4GB is the most he can use.. DOS drivers work within a single 4GB memory section, and lots of stuff gets taken out of it by memory-mapped hardware. For example my current machine only seems to find 1506MB in DOS and ReactOS. Perhaps system memory for integrated graphics takes away quite a bit of the 1st 4GB area. With DOS drivers out of the question, you're left with bootloaders that can work above 4GB. Syslinux's MEMDISK can load disk images, but only below 4GB. a modified (by Chenall) GRUB bootloader can load disk images above 4GB. It would require a contiguous 4GB memory area somewhere in the above-4GB memory. Also coming into play is the disk image itself, as on disk it's only allowed to be 4GB due to FAT32 filesystem limitations. Perhaps decompression works, loading a compressed 20GB harddisk image into system memory. Loading speed can be troublesome if BIOS is involved rather than some native full-speed accelerated mechanism. I've succesfully loaded the entire KNOPPIX (Linux) DVD (4GB size) to system memory by typing KNOPPIX 64 toram. Still not sure I could eject/remove the physical load device though or if it's still expected to be present. I have a 2GB partition allocated to FreeDOS on the machine where it lives, and I'm not coming close to using all of it. I could put the entire FreeDOS drive on a ramdisk if the machine had that much ram to spare. I don't know what to fill up DOS systems with either, not using them exclusively enough I'm afraid. Bernd -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New 12-Jan-2014 UIDE, With 4 Caches!
Jack schreef op 7-1-2014 15:40: The Common cache is always set and uses a default size of 80-MB. All 4 caches can be from 0 (unused) to 4-Gigabytes, and their only rule is that their total size cannot exceed a system's XMS memory! You make it sound like I could use 4 caches of 4GB each, nice to fill up a larger part of my 32GB system memory :) Some can say I am Dreaming!, to believe that new drivers needing caching may be written so late in the DOS life-cycle. But it can happen -- New schemes like FireWire and USB appear all the time! And in any case, I wanted to get multi-caching done in UIDE, while I still had some ideas about HOW to do it!! J.R.E. Enjoy 2014 in good health Jack ! Thanks for updating your work. Bernd -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bloody SMC w8003wc packet driver set up! please help!
sparky4 insano schreef op 16-12-2013 20:54: I am stumped this card is very stingy... Your best bet would be some Realtek or Intel wired network card, perhaps in combination with a PLX adapter (network through power wall socket). I cannot seem to get it to do a DHCP no matter what packet driver i use for it In theory people can write their own packet drivers for the cards they have. In practice I've never seen it done. Bernd -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/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=65839951iu=/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=65839951iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdnpkg
Mateusz Viste schreef op 13-10-2013 23:56: Of course, if you have plenty of disk space, you might want to copy these repositories to your hard disk, and make the repositories pointing there. I think Mark ment pointing to the ISO file, but I guess no native ISO support is implemented, so a CD emulator would be required. Luckily Jason Hood wrote/improved some CD-related tools: SHSUCDRV /F:C:\ALL_CD.ISO SHSUCDX /D:SHSU-CDH /L:X Bernd -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDNPKG update
Mateusz Viste schreef op 12-10-2013 16:52: Hi Marcos, That's great, I'm glad you sorted it out :) Does the program have to write all the mkdir lines all the time when installing a package? I'd expect only the non-existing ones to be listed. mkdir C:\FDOS\doc\fdnpkg\ instead of: mkdir C:\FDOS\appinfo\ mkdir C:\FDOS\bin\ mkdir C:\FDOS\doc\ mkdir C:\FDOS\doc\fdnpkg\ mkdir C:\FDOS\nls\ Also is it possible to install multiple packages using a single command like Linux can? (something like apt-get install x y z) Bernd PS: A batchfile would work as well for that: @echo off goto loop :loop if %1== goto end for %%x in ( *.* ) do if %%x==%1 do FDNPKG INSTALL %1 shift goto loop :end -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDNPKG update
Mateusz Viste schreef op 12-10-2013 21:28: This could be an interesting feature. It doesn't make as much sense as in a linux distro, because there is no dependencies between FreeDOS packages, but it could be nice anyway to be able to install a few packages in one command (especially when they are related.. for example djgpp-make, djgpp-gcc and djgpp-doc..). I will definitely think about it. I used that posted batchfile as INSTALL.BAT, went to the BASE directory of your ISO, and simply did a INSTALL *.* so all of the BASE directory gets installed from CD/ISO to systemdisk/ramdisk. I think Tom mentioned the ISO wasn't entirely license-compliant yet for all listed software due to missing sources for several packages. That's what usually stops me from offering/redistributing what I create. Bernd -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDNPKG update
Mateusz Viste schreef op 12-10-2013 21:52: argument). So for such need, a full-blown script (like the one you did) will probably be inevitable anyway... I'm lazy, so prefer INSTALL KERNEL instead of remembering to type FDNPKG INSTALL KERNEL. Even for a single package thus :) Something like the following works nicely: INSTALL KERNEL COMMAND JEMMEX Now only some intelligent script to actually create AUTOEXEC.BAT (and config.sys) so some kind of configuration is done after installation. Bernd -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New UHDD/UDVD2 -- A Clarification!
Chris Evans schreef op 27-8-2013 22:51: Where can I get udvd2 and uhdd driver from? http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/cdrom/uide/drivers-2013-08-26.zip as mentioned at http://www.freedos.org main page (and http://www.bttr-software.de/forum/forum_entry.php?id=12984 ) Bernd -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] looking for a utility
John R. Sowden schreef op 2-8-2013 22:28: I am looking for a program that will run in config.sys before anything except possibly memory managers (before drivers). I want to display a line of text of my choice and then pause the execution at that point until I hit enter. Hopefully, if will disappear from memory after use. My application is to remind me to plug in a usb stick prior to booting because, under the usb dos drivers I only get 1 bite at the apple per boot. FreeDOS has a ECHO command for config.sys, combine it with a question-mark and you're done. Something like: ECHO? PLEASE PLUG IN YOUR USB STICK AND HIT ENTER Otherwise something like http://www.bttr-software.de/products/pause/ might also work -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FDNPKG install CD
Mateusz Viste schreef op 22-7-2013 21:37: edit // I examined settings of the virtual machine, and noticed that I had set the 'CPU capping' to 30%. I moved the setting to 100%, and then the miracle happened - both UDVD2 and FDAPM stopped freezing! I rebooted many times to be sure, and it all worked every time. Emulation... Bleh :) That's good, maybe Ulrich could add this info to the wiki. For VMware, I know using JEMMEX masks a reboot-issue in kernel (or FreeCOM) when trying to do a keyboard-reboot-sequence (ctrl-alt-del , but in vmware it's ctrl-alt-insert so host OS doesn't catch the combo) REN CONFIG.SYS CONFIG.OLD results in: (getting the same issue on FDAPM COLDBOOT. WARMBOOT works, HOTBOOT hangs. No JEMMEX HOTBOOT driver present/loaded) Invalid opcode at FFF0 F000 0002 015C 0F9D 118A 00D9 0008 0070 118A 00D9 FF53 F000 Cannot terminate permanent FreeCOM instance System halted ... reboot or power off now Also went over the CD, seeing the following obvious things: upx v3.09 http://upx.sf.net himemx v3.34http://www.japheth.de/Jemm.html uide 30-april-2013 mtcp: 2013-04-26 DEVEL: contains UPX again Watcom: most recent? -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FDNPKG install CD
Mateusz Viste schreef op 21-7-2013 18:45: Just like Rugxulo, I'm a bit lost about all these IDE/SATA/PATA stuff, until now I was naively assuming that a SATA CD drive is behaving like a PATA one, and same drivers will work, and the only difference is at the physical level... You're right. IDE can be configured as PIO or UDMA, SATA can be configured in AHCI or IDE (legacy) mode. That still doesn't take into account other interfaces/controllers: * SCSI * FireWire * USB * parallel port * serial port * soundcards * specific interface cards All of these can have a CD drive attached to them. Remember Iomega's zipdrives having lots of different drivers By the way, how come that SATA HDD drives works fine without requiring any additional drivers then? Ancient BIOS int13 compatibility causes your bootdrive to be listed as drive 0x80, and DOS kernel assigns driveletters to partitions on it, starting with C:. Same as some small capacity removable drives (ZIP, USBstick) could be listed as drive A: , and high capacity ones as drive C: Anyway, I tried to replace the xcdrom.sys with udvd2.sys, as I understand that the latter have some special magic for supporting SATA CD drives, but unfortunately I got some troubles - when UDVD2 loads, it freezes the boot for ~1 minute, which is really a pain. Ouch, thought this was solved, both with and without some custom fixing driver. Most recent VirtualBox (4.2.16?) used? Most recent UDVD2.SYS used? http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/cdrom/uide/drivers-2013-04-30.zip In worst case, revert to XCDROM but keep UDVD2 around. Also add SYSLINUX's ELTORITO.SYS driver on the disk if you want. That one is very specific though, and only grants access to the most recent ISO9660 filesystem that you booted from in non-emulation mode (as used by Isolinux and GRUB). Thus only grants access to 1 'cd-drive' no matter what interface you booted it from. (but even that can be broken, if replacing BIOS USB emulation stack by an own USB driver stack in DOS). Your CD is in floppy-emulation mode however, trying to explain how to add isolinux is a slight nightmare though, same for trying to explain how to make it bootable. I am testing this inside a VirtualBox machine. I recall some months ago (or was it years maybe?) some flames on the list about this problem, but don't remember much constructive ideas, other than saying 'virtualbox is buggy'. Incomplete emulation isn't much fun. Every emulator has its own quircks. Is the situation still the same, ie. is there no way to make UDVD start faster under VirtualBox? Is there any other driver nowaday that could handle IDE/SATA drives and not freeze VBox for a minute? Keep what you have if that proves to be better. Ideal loading order would be: 1) ELTORITO.SYS 2) if fails, load XCDROM Of course I don't say UDVD2 is bad (and I certainly don't want to start any nuclear war about this), but the fact is that many people test stuff under VBox these days, and if a bootable CD freezes 2s after starting booting, they won't get any further. You're right. I've not tried to use RUFUS on your ISO to get its content onto USB flash drive. A step too far for now :) Bernd -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FDNPKG install CD
Mateusz Viste schreef op 19-7-2013 20:54: This makes it possible to use this CD on a clean PC to install the latest version of FreeDOS. There is no installer - you need to use FDISK, FORMAT and SYS by yourself. Then use FDNPKG to install whatever packages you need. Thanks for making this available Mateusz! I'm running into a few issues here: * old versions of software (or is this to demo the updater? ). * missing CWSDPMI.EXE apparently * FDNPKG exits on SIGSERV on many commands * FDISK 1.3.1 doesn't like VMware Workstation 9. * bootCD only compatible with optical drives on IDE controller. * old CD drivers used, maybe UDVD2 * any (working) usage examples for FDNPKG available? * harddisk (with FAT partition) required. SHSURDRV works on systems with enough RAM, as your config loads XMS/EMS/UMB/HMA anyway already. I haven't tested it thoroughly (just verified that I am able to boot and install at least one package), so please not hesitate to report any problems (solutions to these problems are welcome, too). ;) Could you also please make available the 1.44MB bootdisk image used in the CD? Some people like to butcher (ehm..optimize) this, without downloading the entire ISO. Bernd -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FDNPKG install CD
Mateusz Viste schreef op 20-7-2013 23:08: Could you tell me please which software you see old? Mainly the bootdisk programs: * kernel: 2036 instead of 2041 * xcdrom instead of udvd2 * sys 3.6 instead of 3.7 or 3.8-test * missing CWSDPMI.EXE apparently Yes, cwsdpmi is not on the boot floppy. Mostly because it's not needed - have you run into any kind of troubles because of the lack of cwsdpmi? Yes: load error: no DPMI - Get csdpmi*b.zip upon invoking FDNPKG.EXE Anyway, I fixed it, and updated the binary on the boot image. The bugfix will be part of the next FDNPKG release (which should happen soon by the way). Thanks for fixing. What's happening exactly? I'm not really a VMware aficionado, never tested FreeDOS with this. Is it some kind of a 'known bug' specific to FDISK and VMware? What solution would you suggest? I get errorlevel 64: Error Reading Hard Disk: Search operation failed. Program terminated. fdisk 1.2.1 works. Emulators make things difficult. Dosbox and Rpix86 have very strange behaviour for driveletters, filesystems and memory behaviour. Is it because of the XCDROM.SYS ? I'm no expert here, but aren't SATA CD drives acting as some kind of 'emulated IDE' ? Or does it mean that the boot image would need a special SATA driver, and some detection logic to load the right driver? This starts to sound complicated :P Yes, and a lack of DOS drivers for various controllers/interfaces is the main culprit. The CD driver works for IDE and for SATA in legacy mode. Now imagine having only an USB CD drive on a system. (or something emulating it, like a Zalman hdd-caddy, or ISOSTICK) But do keep things simple, better a mostly-working environment that's released, instead of something over-engineered but never-released (like I have). I think you got lost because of the memory bug. Now that it's fixed, FDNPKG usage should be quite intuitive. I mean I basically get lost of how to get a list of available programs I can install. A bit of browsing, more or less. SEARCH already implies you as a user know what you want. I'm not sure I understand what you are saying.. Yes, a harddisk is required indeed... since the goal is to install FreeDOS on a hdd. I'm not sure anymore nowadays the goal is installing FreeDOS on a dedicated system, but rather to have it available and to use it, when necessary. What I mean to say is, people will boot from your CD, then find out their harddisk is partitioned 100% already for Windows. Thus, no easy way to get a drive C: available. Are you suggesting emulating a C: drive with a RAMdisk, and installing FreeDOS there? What would be the real life use case? Are you thinking about some kind of full-blown automated FreeDOS RAM-powered livecd, like what Knoppix does with the 'toram' boot option? Just put SHSURDRV.EXE on the bootdisk image, and you'll get there. Speaking of bootdisk..if people boot from their own boot medium (harddisk or some specific floppy) including CD access, they can't run FDNPKG as it's not in the data part of the CD ( X: ) but only in the bootdisk part (FDBOOT.IMG). A minor inconvenience for example on systems that can't boot from CD. That's a very good point - I will synch since now on the floppy image on iBiblio separately, too. It's named 'boot.img', and it's in the same location as the CD image: Thanks! I'll get the FDNPKG from there. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/ -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos-user basic how-to questions...
Pierre LaMontagne schreef op 8-5-2013 16:15: 1 How can I use my USB flash drives in FDOS? I checked my CMOS settings. 'Legacy USB' support is enabled, but when I tried accessing the flash drive in FDOS, it wasn't available. I'm assuming, once working, I would be able to use it as a floppy? This would allow me to put files on my modern PC. Partition format it as FAT32 with Windows tools like RUFUS or RMprepUSB. Then boot from this bootable USB Flash Drive. That's about all the legacy emulation a BIOS will do. Booting from harddisk/floppy then trying to get access to USB Flash Drives is troublesome due to lack of the BIOS emulation (only provided for the booted drive) as well as DOS drivers for USB/SCSI/FireWire controllers. 2 I'd also like to be able to burn files to my optical drive as opposed to only reading from it. Is there an app to burn files to CD from FDOS? This also would allow me to put files to my modern PC. If you're able to find an ASPI driver, then MKISOFS or CDRKIT can do the burning. Usually this means creating a new disk image (ISO file) then writing that to CD. I'm assuming your CD drive is connected to IDE or SATA controller. If not you're out of luck. http://bootcd.narod.ru/index_e.htm lists an ASPI.SYS Other than these 2 things, FDOS has been very useful to me. I'm so thankful for it. Goodluck :) -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS jemmex.exe optimalization
Rugxulo schreef op 7-5-2013 15:31: Yeah, gotta love problems like this. You'll have to take away and add things one by one until you can deduce what the real problem is. My recommendation would be to see if one of the several bootdisk versions work. So search on Google for netbootdisk or Nwdsk or Modboot. If the MS-Client program works on those disks, you can try to adapt it to your own situation. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Installing FreeDOS on the second partition of the disk
Aleve Sicofante schreef op 22-4-2013 2:07: Thanks Jeremy and thanks to Felix too. I think at this point I should paint the whole picture, so you guys get a better idea. I bought a 2.5 drive enclosure from Zalman, the VE-300, that acts as two devices in one: it shows itself to the system as two devices: a hard disk drive AND an optical disk drive. The optical drive has in it what corresponds to an ISO that resides in a special directory of the FIRST partition in the hard disk. You choose which ISO with a clickwheel and an LCD menu on the Zalman enclosure. The fact that the Zalman VE-300 won't understand but the first partition for its optical drive emulation is the reason I can't use the first partition for FreeDOS. This setup will be my repairman companion and I want FreeDOS for those utilities that would otherwise need a floppy drive or are distributed only as DOS utilities. There should be FAT32 firmware for VE-300 available at the Zalman website. Default indeed is NTFS, to allow ISO files with a size of 4GB and above. Another option is the ISOSTICK hardware device, which only supports FAT32. the system won't boot if the installation wasn't made on the first or only partition (I tried both), no matter what I chose in the final screen. This might be the BIOS coming into play, expecting bootable partitions to start below 8GB or so. BTW: the installation procedure tells me I'm installing FreeDOS 1.0 all the time, not FreeDOS 1.1. I swear I burned the only image I downloaded from the FreeDOS website, and that's fd11src.iso. You might have switched languages where the translated files aren't kept up to date. My recommendation would be to either download UBCD ISO-file (which includes FreeDOS) or to install FreeDOS inside of Bochs emulator, then create an ISO where you boot the harddisk-image used for Bochs. I'm working on that last one right now (to avoid the entire installation procedure) for 16MB+ machines, though as usual distribution is a nightmare when you have to take care of providing sources as well for all programs. Improving the installers is a bit difficult, lots of software isn't maintained anymore or not up to date for current machines. If you want to see if FreeDOS boots properly, the manual barebones way is best (use FDISK, FDISK /MBR , FORMAT C: , SYS C: ). Installing FreeDOS programs afterwards should be possible when starting INSTALL.EXE while you're in the X:\FREEDOS directory. Post-installation configuration is done in POSTINST.BAT at C:\DOS -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Bios limitation at 8 gb, and new hdd
Op 9-2-2013 12:18, sakura kinomoto schreef: Hi all! I have a PC 1996 year, and bought a hd d, Samsung sp0802n, (maybe 2005 year), with 80 gigabites But my bios can see only (first) 8 gigabites I am newbie, so, please, tell me, what software can help? Thanks for any hint! You might want to purchase a PCI IDE controller, its an add-in card that has its own firmware for harddisks and thus doesn't rely on the system BIOS. Hopefully your BIOS allows to boot from add-in cards if they have their own system ROM firmware. [ http://en.wikipedia.org/wiki/BIOS_Boot_Specification#BIOS_Boot_Specification ] Something like this: http://www.amazon.com/Syba-Combo-SATA-Card-SY-VIA-150/sim/B002GHBVSA/2 The software route would be a DDO ( http://en.wikipedia.org/wiki/Dynamic_Drive_Overlay ) but I don't know if these programs are freely available or only for sale (like Ontrack's old DDO software). Usually ends up giving lots of trouble when disk maintenance programs are running. Bernd -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New standard FreeDOS text editor - what it should be (voting)?
Op 29-1-2013 20:02, Michael B. Brutman schreef: PC/MS DOS 5.x and 6.x will run in 256K with usable memory to spare. PC/MS DOS 3.x will run in 128K with usable memory to spare. If FreeDOS is designed/optimized for a bigger footprint then that's fair, but there is nothing wrong with asking or trying to push the limits. So make it 256K. Fine. The point (which you missed by a country mile) is that it should run on a fairly small machine. Because they are out there ... And no, 35 years ago would put us in 1978. 128K/256K PC style machines were common even in 1985/1986. FreeDOS does not add that much extra function where a 256K (or even a smaller machine) could not be a reasonable target. Boot FreeDOS on a modern machine (or emulator) without loading an XMS driver. You'll see about 56KB for kernel (likely config.sys settings can reduce memory if manually specifying a lower amount of buffers/files etc) and FreeCOM using about 101KB (which you can't reduce, even if loading an XMS-manager from commandline). That makes 157KB, without having loaded drivers and loaded programs. Though compiled versions of FreeCOM exist that can swap large parts of shell to disk upon executing a command, my bet would be on the shells used by embedded ROM-DOS or so. 4DOS also is able to swap to disk (256KB swapfile) in order to preserve memory for starting/running programs. Out of the remaining amount of conventional memory, I've got no idea what's still able to run and what not. Only ever used machines that had at least 640KB available. Any emulator available that allows to set CPU below 386 and total system memory capacity at a user-selected value below 1024KB ? Bernd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] vfd(2)
Op 16-1-2013 6:28, kurt godel schreef: fdread from Feinman's createcd133, which flawlessly created an .img from a real floppy in the drive. I can actually boot this machine from a bootable floppy, yet the fdread utility runs to a certain percentage than stops with the message:disk not formatted properly.' That motivated use of VFD; I didn't realize VFD could edit an existing .img; the how-to documentation for VFD is almost non-existant. I'll try Bernds suggestion.TNX. Under Windows, WinImage is a good one. Perhaps under DOS, FreeDOS's DISKCOPY program would do the trick (DISKCOPY A: C:\FLOPPY.IMG /O /G /X ) Not sure what the fdread program is, maybe was created before DISKCOPY. Some RAREAD/RAWREAD program is also an option if it exists as counterpart for RAWRITE. -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dos networking and wireless?
Op 15-1-2013 17:00, Karen Lewellen schreef: my goodness! that is amazing, and so are you. Thanks for providing such rich information. Karen powerline adapters (PLC) might also be an option, though that's not completely wireless ofcourse. Of modern PCIe and/or USB LAN adapters, no idea yet which would work. Maybe Intel or Realtek. Bernd -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VFD
Op 15-1-2013 20:34, kurt godel schreef: If anyone out there is familiar with vfd(virtual floppy disk), I create the floppy, and associate it with the 'send to' item in the right click, but when I try to send a file into the virtual floppy, I get the box: please insert a disk into drive: x This happens whether I name the drive A,B, or anything else. What am I missing? Download a 1.44MB bootdisk image (bootdisk.com website for example) and mount that as drive A: using VFD. Afterwards clear the contents of A: so you can store your own files there. Note I've got no experience with VFD whatsoever, so to me it seems more convenient to have a verified floppy file present already rather than creating one yourself. Bernd -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos-user Digest, Vol 731, Issue 1
Op 7-1-2013 18:48, wiwa64 schreef: I'm not quite sure whether i got your point correctly, but have you had a look at FNTOOL? It's kind of a superset of tools like dirname and basename. E.g. FNTOOL /B C:\TEST\REMASTER\DOS would return just DOS. Looks like you're right, FNTOOL /B %_CWD% works like a charm. Another issue solved after all then despite flaky testing on my side a while ago. Thanks! -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Install from G-DOS
Op 12-1-2013 18:52, Thomas D. Dean schreef: What can I do to complete the installation? The installation process assumes you're installing from CD. What I'd recommend is storing the ISO on drive C:, then the following: SHSUFDRV /F:C:\FD11SRC.ISO SHSUCDX /D:SHSU-CDH,X and then switch to drive X: (listing the content of the ISO) and start SETUP. Maybe even SUBST works, never tried that. If you only want to unpack all the software archives (zip files), running INSTALL.EXE should be possible, from the \FREEDOS directory if I'm not mistaken. Or use UNZIP.EXE Bernd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos V2.0 - when will it be available?
Op 8-1-2013 15:38, KOS schreef: Hello there, do you know when V2.0 of freedos will be available? I'm not sure there's going to be a V2.0 sometime soon, be there FreeDOS roadmaps or not. I'm still quitely working on version 1.2 of the FreeDOS distribution whenever I find spare time. Is there anything that you need but find lacking sofar in the 1.0 and 1.1 releases? Or for that matter in the core components like the kernel and shell? Bernd -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos V2.0 - when will it be available?
Op 8-1-2013 20:22, KOS schreef: No currently there is not something because I have not managed to install it yet, since I cannot make the bootloader work. After installing everything, the bootloader does not give me the right options like shown here http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_5 (I am installing it on a real machine not a VM). Are the expected files present at C: ? Next to whatever directory you installed FreeDOS to, you should have the following files: C:\KERNEL.SYS C:\COMMAND.COM optional: C:\CONFIG.SYS (or FDCONFIG.SYS) optional: C:\AUTOEXEC.BAT If it's just the bootsector missing, then solving the issue is done by performing (from FreeDos directory or from bootdisk or CD) : SYS C: I like that dos is still developed by you and I hope I could help somehow one day (being a programmer) Sounds like an interesting option. I'd still recommend to use some virtual machine and develop your program there. Bernd -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos V2.0 - when will it be available?
Op 8-1-2013 20:59, KOS schreef: should I give SYS C: at the grub prompt? If you're able to reach DOS already, perform SYS C: Alternatively, you'll have to search (Google should do the trick) how to chain from GRUB, GRUB2 or GRUB4DOS to KERNEL.SYS , skipping the entire bootsector thing. If you can use your flashcard on a Windows machine, then RUFUS [ http://rufus.akeo.ie/ ] should be able to make the storage card bootable. I have developed XDOS http://www.microwave.gr/giannopk/xdos.htm a collection of msdos 6.22 and a huge lot of applications. I have not written a single line of code, this is just a collection of programs about 2gb. I think it would be nice to share them with someone developing freedos so that they are included in the next distro as they are or just to give new ideas of what programs could be written. I have spent about 3 months collecting these programs and make them work ok. Please let me know if you are interested in seeing this stuff I'd be interested. Assuming you can't make this available publicly anyway due to using MSDOS, uploading to a website isn't an option. However if you want, mail the entire thing to me in a compressed archive (renamed zipfile for example) at bbla...@gmail.com Already been recently rewriting some distributions that use FreeDOS as those rely on ATAPI CD-drives while I use the ISOstick USB-device instead. So, it's worth looking at what people come up with before implementing things in a new FreeDOS distribution. Bernd -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CD-DVD ROM drıve
Op 3-1-2013 23:14, TuLithu schreef: Last night I installed FreeDOS on my HP Pavilion g series laptop. Everything seems to work fine, except I can't access my DVD ROM drive. I have spent several hours reading the help files and examining the config.sys and autoexec.bat files, but I can't figure out what the problem is. Did you install it from the optical DVD drive? How's it connected to your machine? Plain old IDE (or SATA) or somehow externally using USB or PCMCIA? I figured the drive would be at D: or E:, but I just get an invalid drive message. If anyone can help, it would be greatly appreciated. I haven't used DOS since about 1995, and even then, I only knew the bare basics. An installed FreeDOS can show drive assignment through SHSUCDX /D Also running MEM /C will show you if UIDE.SYS is installed, it's the default CD driver for IDE-connected optical drives. To manually get UIDE going requires typing the following 2 lines (which can be present in AUTOEXEC.BAT startup file) : DEVLOAD UIDE.SYS /D:FDCD0001 SHSUCDX /D:FDCD0001 http://johnson.tmfc.net/dos/driver.html contains newer versions of UIDE and UDVD2 -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New Version of DOSUTILS
Op 4-1-2013 1:08, wiwa64 schreef: Please feel free to explore the various (in total seventeen) utilities in the package, which can be downloaded from here: http://www.bttr-software.de/products/jhoffmann/, to see whether some of them might possibly be useful. Further details are given in the two instructon files dosutils.txt and form.txt which are also part of the package. Thanks for the update. I remember one of your tools being able to show the directory path, but not in separate pieces ( I wanted to convert path to Linux-style to satisfy Syslinux.cfg requirements for the Syslinux installer). Preferably just the directory name, without any - filename - directory/directories above it - slashes/backslashes - colon - driveletter so C:\TEST\REMASTER\DOS\ would return DOS if executed from that directory. If going one dir up, it would return the string REMASTER (etc..). End result is something alike: @echo off set /E output=tool.exe /basename set string=%output% cd.. set /E output=tool.exe /basename set string=%output%/%string% set string=/%string% echo Unix-path for %_CWD% is %string% (without driveletter) Think it was the basename tool. Bernd -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How create a booting freddos cd live
Op 31-12-2012 13:32, iw2evk schreef: Hi at all, whath is the right and shorth procedure for create a freedos 1.1 booting live cd? There's no full-proof method yet as that also means specifying which program you use to create the master ISO. mkisofs -R -D -V FreeDOS 1.0b -o /tmp/fdbasecd-remastered.iso -b \ ./isolinux/isolinux.bin -c ./isolinux/boot.cat -no-emul-boot \ -boot-load-size 4 -boot-info-table ./ is what Eric Auer once wrote, but specific to Linux. If all you want to do is write a downloaded ISO to (re)writeable optical disc, then use some CD recording program (CDRECORD or WODIM, or on Windows programs like IMGBURN) and point them to your CD-image file (FD11SRC.ISO or FDBOOTCD.ISO file). CD-writing under DOS is very rare as most Unix-ported ISO9660-tools depend on a SCSI subsystem, thus requiring a SCSI or ASPI driver for your SCSI/IDE controller to which the CD-drive is connected. With no publicly redistributable ASPI driver, people generally are out of luck. P.s have a good 2013!! Same :) Bernd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How create a booting freddos cd live
Op 31-12-2012 19:11, iw2evk schreef: Hi and good 2013! Thanks, same to you. Couple of more hours to go here, in the Netherlands. I've burning fdsrc1.1. from freedos site, but it'a a Install only disk. I'm intersted to boot freedos from cd (for use in pc with loaded another o.s.. It's a bootable CD just like any Linux distro. The autorun.inf is for additional Windows features, and trying to run SETUP.BAT should also warn you that you can't run all of SETUP.BAT in Windows. What the CD does, is getting started by BIOS. Then it loads Isolinux as the bootloader, reads isolinux.cfg, shows a menu, loads a diskette image into memory as drive A:, boots that, loads CD drivers, accesses the CD, finds and executes SETUP.BAT on the CD. Once SETUP.BAT is running it will show you an installation menu. Just burn the FreeDOS ISO just like any random Linux ISO file. (burn image in ImageBurn program), not as some datafile (and also don't extract the contents and put that on CD) Bernd I due change autorun.inf and setup.bat for starting boot of freedos from CD? (live cd mode like linux distro) There's no need to change anything. Modifying CD content and recreating an ISO is a tricky business. Bernd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Made XP work okay...
Op 26-12-2012 11:58, Michael Robinson schreef: I've been studying Windows 7 verses Windows XP and honestly, it's a toss up. Both systems are bloated and complex. A ROM based dos system is more secure than even the typical Linux system and it's going to be light weight. That's not saying much though, I can't compare Apples to Oranges and be fair about it. (cc'ing Kevin in case he's interested, but might be wisest to leave him out of further discussion if replying) I remember Kevin O'Connor demonstrating Coreboot + SeaBIOS + embedded FreeDOS floppy image a couple years ago. This was for some old version of the QEMU emulator program. As coreboot als works on some real hardware (for example http://www.coreboot.org/ASRock_E350M1 ) you can actually build an embedded DOS. Too bad you first have to install a multiple-Gigabytes Linux distro to start compiling this. It can go even further: use the Cache-As-RAM trick and in theory you wouldn't need any memory installed. Assign outermost cache (L2 or L3) as memory and split it between working memory (640K? 2MB?) and video memory (yay AMD APUs!). It would make a nice tech demo. Then again, programmer's time is expensive, RAM isn't. In above experiment, coreboot would then need to decide: * memory installed: do regular thing * no memory present: load FreeDOS floppy img, @ECHO PLEASE INSTALL DIMMS Alternatives were 1 or 2 flavors of storing FreeDOS in a small ROM and have that loaded by your motherboard. Usually requires modifying the system BIOS or flashing the ROM into a network card or storage controller. ( [ http://rayer.g6.cz/romos/romose.htm ] works with Bochs I think) ( never tried http://www.datalight.com/products/rom-dos ) To be fair, Linux likely could also be stored in ROM/flash/eeprom especially with today's large sizes necessary for UEFI. currently not supported in DOS and one has to take care of that somehow. I think that running Warcraft II Battle.Net edition on a freedos system is possible, but there are a lot of pieces to pull together and Blizzard probably won't offer to help. I'll try to get some PCIe network cards and see if they work with iPXE (network bootloader software) as well as packet drivers. Might start with some Intel card. My preference is to run DOS from a ramdisk, then obtain further software through whatever networked program in DOS. can't. Even if they make their fundraising goals and can hire competent programmers to help move the project along faster, there is no telling when stability will be achieved. Consider it a legally free to redistribute flavor of Windows, instead of an operating system suitable for gaming. The only way I get ReactOS working is by removing all USB devices and booting from ATAPI CD. I don't know how old your systems all are, but old Windows versions should boot fine in Bochs as it's a rather complete system emulator. So: host OS (windows/Linux/OSX) + Bochs + Win9x + game. Bernd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Windows 98SE and ipxwrapper...
Op 26-12-2012 5:40, dmccunney schreef: I have an old Fujitsu Lifebook p2110 with an 867mhz Transmeta Crusoe CPU and 256MB RAM (of which the Crusoe grabs 16MB off the top for code morphing.) That morphing and learning the architecture is indeed slow for a while, possibly forever. The big issue on the Lifebook is a slow IDE4 HD with an anemic transfer rate. IDE4 is a BIOS limitation, so a faster drive isn't an option. Big apps just load slow, aside from RAM requirements once up. I don't even try to run a current Firefox, as it's really sluggish on Linux or Windows. To the extent I browse from the box (seldom), I use Midori, Opera, SeaMonkey 1.X, or (if in Windows) occasionally IE (long enough to go to a known good site, grab something, and exit.). Economically probably not worthwile, but SSDs exist in various forms. The usual SAS, SATA and PCIe (and mSATA), but also still old IDE in both desktop (40pin) and laptop versions (44pin). I'm not sure if any NT-family Windows version is just as compatible with old software as that Win98 is. Likely Linux with Wine comes close as well. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re (2): Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.
Op 21-12-2012 3:40, peasth...@shaw.ca schreef: Well that was OK when diskettes were the only rotating media. Usually a diskette wasn't partitioned. Part and volume were synonymous. optical media usually weren't partitioned either, and flashdrives might be partitioned but usually only with 1 partition. Windows is very specific about partitioned removable media. External harddisks is another story ofcourse, and even there most/all partitions aren't visible to DOS anyway, as Microsoft discourages using FAT, for example by disabling the ability in their own FORMAT/DISKPART tools to create FAT partitions over 32GB (which starts to show for USB sticks and SD cards). Where a hard disk drive is involved, drive should mean hard disk drive and part should mean part of a hard disk drive. When software says it will format the drive I want to be sure it doesn't mean format the whole hard disk drive. Unambiguous terminology really does help. I've never used 'part' and don't recognise it from any operating system I know. Ideally you'd have something like: C: (primary partition/volume #1, active, label xyz, capacity X, used Y, disk Z, total sectors/heads/tracks = A/B/C, starting from D up to E). I had hoped to run FreeDOS on the OLPC XO-1.5 but it is no simple problem. http://wiki.laptop.org/go/Talk:Our_software That sounds like a video BIOS indeed. I don't know if Coreboot could run on that machine at all. If so, it might be able to run SeaBIOS and corresponding VGA BIOS as well. I'm not in possession of a 35 euro Raspberry Pi computer, but that running on Linux with a DOS emulator (BOCHS/QEMU) on top could run just fine. Even when considering how memory-hungry most Linux distributions are. Guess it helps they upgraded the machines to 512MB. I don't know of any effort of running Bochs on a very stripped Linux. Kernel + initrd + tiny userland + Bochs + FreeDOS should do the trick. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re (2): Another possible ambiguity of target; a drive part not acceptable to the installer.
Op 19-12-2012 19:37, peasth...@shaw.ca schreef: The FreeDOS 1.1 Base CD offers to apply fdisk; but you recommend not using it? An installer which should not be used? The FDISK of any DOS has always been very limited, mimicking Microsoft's installation procedure (I'm the only operating system, overwrite any previous code). For a blank harddisk FDISK will do just fine. ... make sure the partition (drive) ... There's that ambiguity again. Do you mean hard disk drive as in /dev/sda or part of a drive as in /dev/sda1, /dev/sda2 and etc. 'Drive' is a typical DOS terminology, meaning partition/volume, thus sda1 etc. It's used as 'Drive C:'. Basically referring to everything which has a driveletter assigned (floppy, harddisk, cdrom, network shares, etc). More advanced operating systems have improved partitioning tools that also take multiple operating systems into consideration and allow to setup multibooting by installing a bootmanager or including previous operating systems to their own bootloader. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Windows 98SE screwing up Freedos 1.1...
Op 19-12-2012 7:45, Michael Robinson schreef: like freedos command.com got renamed to command.dos and I've already renamed autoexec.bat to fdauto.bat, but fdconfig.sys seems to be I think the files get renamed to *.DOS (AUTOEXEC.DOS/CONFIG.DOS/COMMAND.DOS/MSDOS.DOS/IO.DOS) or a few of them to *.SYS , for any old 'ms-dos' that Windows 9x encounters. Overwriting the bootsector of drive C: is as simple as SYS C: /BOOTONLY when using FreeDOS SYS program. The downside of that is you ruin your Windows installation as that's no longer bootable. Better solution is using some kind of bootmanager like Grub4DOS and then adding both FreeDOS and Windows 98. Another solution might be to adjust MSDOS.SYS textfile in Windows 98 to not load Windows automatically, and then adjust CONFIG.SYS to load FreeDOS files. That way you have everything FreeDOS except the kernel. [ http://www.vfrazee.com/ms-dos/6.22/help/commands%20for%20defining%20multiple%20configurations.htm ] missing. One option is to use a program called fips, delete the freedos stuff, and install freedos to a second primary partition. This is somewhat of an extreme approach though. For the most part, I only want to run old games like Warcraft II where freedos + hxrt might do the trick, except that I'll need networking too. A working War2 (that is, if you have the DOS version) might work if you're able to install TCP/IP stack, or IPX stack, or Kali. Always confuses me, that ancient stuff. ReactOS would support these old games, but there hasn't been another release for months and I can't even get the latest trunk to build. http://www.reactos.org/getbuilds/ lists CD images. I've used the rbuild system in the past, the cmake build system takes some time to get used to. Not tried it recently. Not been able to boot anything on real hardware either, stubborn Logitech keyboard with USB hubs confuses things too much. Running an unlicensed copy of 98 is not the best idea where there's the issue of 98 having a lot of bugs and being out of support. A firewall could help a bit. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] hunting a program?
Op 19-12-2012 15:19, Michael B. Brutman schreef: mTCP sounds right. ; - 0 Speaking of networking, does anyone know which modern cards are compatible with both of the following? 1) packet driver 2) iPXE A universal UNDI driver would also do miracles. I've got a closed source binary of the discontinued UNDI driver from the bankrupt (well, bought) EMBOOT, Inc. Not suitable for general use thus. I still have to test if HTGET can obtain FreeDOS ISO files, Ibiblio isn't much fun with mixed http/ftp content. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Copy from network drive
Op 12-12-2012 23:52, Tom Ehlert schreef: and 4DOS (which produces this error message) is NOT part of FreeDOS. FreeDOS 1.1 contains 4DOS (v8.00, as maintained and improved by Lucho) as an alternative shell (config.sys option 3 or so, FreeCom is default). Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] burn cd, dvd
Op 12-12-2012 19:04, sakura kinomoto schreef: I have good Optiarc Dvd-Rw Ad-7200 A; freedos succesfully read cd, dvd... how i can write dvd? please, tell me a simple instruction https://sites.google.com/site/blairdude/cdrkit It requires an ASPI/SCSI driver for your SCSI or IDE controller. http://bootcd.narod.ru/index_e.htm lists an ASPI.SYS that should work. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Copy from network drive
Op 11-12-2012 23:26, Marcos Favero Florence de Barros schreef: Hi, We are facing a difficulty with the 'copy' command in the network of our Health Center. What's running? SMB using MS-Client? NFS using something? I guess you used shares mapped to driveletters. The SHARE program might solve your issue. Otherwise the server perhaps has issues, instead of the clients. Perhaps one of the disks at http://www.veder.com/nwdsk/ could be a solution, or http://www.netbootdisk.com/ In other words: I've got no idea, keep trying stuff till you run out of ideas. Bernd -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Bruce3
Op 28-11-2012 6:39, bruce.bowman tds.net schreef: Something is definitely wrong with nonexistent drive D:, and I suspected the source to be one or both of the USB device drivers usbaspi.sys or di1000dd.sys. These drivers were the ones recommended by the DFSee live CD that I've been hacking for this project. Using BIOS Legacy USB emulation together with a later-loaded stack of drivers usually means trouble as the driveletter is pointing to a disk no longer controlled by BIOS. Instead the DOS USB-driver you used assigns a new driveletter. Same typically happens to mouse, keyboard and cdrom devices if they're connected to USB. Loading a USB stack of your own disables the emulation provided by BIOS entirely, and thus if the new stack is incomplete (lacking a driver for USB CDROM for example) you lose access to that device. This is also the reason many systems only allow USB sticks in USB2-ports as install/live disk. My apologies for not having pointed you to the /F switch for the shell in advance when trying IF EXIST X:\NUL stuff As someone mentioned earlier, use separate batchfiles or use one with labels where the file calls itself slightly recursively. @echo off echo This is file1.bat for %%x in ( C D E .. X Y Z ) do if exist %%x\NUL call file2.bat %%x @echo off if %1== goto error echo This is file2.bat checking %1 IF exist %1\GAMES\NUL echo Games directory found! rem rest of checks go here goto end :error echo No file specified goto end :end echo Reached end of file2.bat Recursively: @echo off if %1== goto init goto loop :loop if %1== goto end if exist %1\NUL echo %1 exists! shift goto loop :init call %0 C D E .. X Y Z goto end :end Many variations are possible. Maybe easiest even to use 4DOS as shell as that allows more complex scripts. Bernd -- Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Bruce3
Op 27-11-2012 6:45, bruce.bowman tds.net schreef: In fact I am essentially done with my project but still want something I can throw in a batch file to probe for writeable drive letters so I can give the user an opportunity to save a game and resume later (like they used to). DOS kernels only assign driveletters to FAT filesystems. For (emulated?) floppy drives A: and B: get assigned, thus C: till Z: get assigned to everything else. A FAT filesystem contains the NUL blockdevice, making it easy to test: @echo off IF EXIST C:\NUL echo Driveletter C: points to a FAT filesystem. Testing if you can store files on the drive is a different issue altogether, as it involves: * checking if the drive isn't full yet * checking if the drive isn't write-protected (read-only) * checking if there's enough free diskspace Bernd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS bootable CD image sought
Op 26-11-2012 20:47, bruce.bowman tds.net schreef: All the bootable CDs that I've seen have contained a floppy disk image. This is what actually boots. During the boot process the embedded AUTOEXEC.BAT and CONFIG.SYS reload the drive and assigns it a DOS drive letter. Only after that's done does the full content of the CD become accessible to the OS. Yes, DOS is only able to boot from FAT filesystem, and thus not natively from CD-ROM as that uses ISO9660 filesystem. In theory it might be possible to build this into the FreeDOS kernel, but then again it's not really DOS anymore in such a case. To work around this, the EL-Torito specification was created, allowing you to specify a bootloader or bootdisk image as startup part on a CD. MagicISO seems to do well with editing the CD image but not the FD image. To get this to autorun, I have to be able to edit AUTOEXEC.BAT and CONFIG.SYS. So MagicISO is not the answer. I've done a full scan and detected no sign of the trojan that someone warned me about. Nonetheless, I have removed this software from my computer. I did a full backup and saved my system state last weekend, so I'm not too worried about it. I use WinImage to extract files to local disk, then modify these files and finally insert/replace them again in the disk image. Your ISO modification tool (UltraISO, PowerISO etc) might allow to insert the modified bootdisk imagefile again. The other option ofcourse is to recreate the CD-ROM using ImgBurn for example (or arcane options like MKISOFS). Explaining how to use CD mastering programs can be quite difficult. I'm now starting all over using the instructions found here: http://www.k1ea.com/hints/Creating_a_Bootable_DOS_CD_V%201.5.pdf At first sight that looks like Georg Potthast's guide for creating a bootcd using a harddisk image. I would like to do this using FreeDOS instead of DOS 7.1, though. The more I play with FreeDOS the more I like its features. What actually happens if I install FreeDOS on my Windows computer? I don't want to do that and end up with a machine that won't boot XP. I'd recommend not to install FreeDOS on the same partition (driveletter) as Windows XP. A separate partition or disk might be safest. On modern systems use a USB Flash Drive and some USB installation tool like RUFUS. Bernd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS bootable CD image sought
Op 25-11-2012 4:28, bruce.bowman tds.net schreef: The bootable CD images that I've been seeing for FreeDOS and DOS 7.1 are all /installation/ disks that first fake a floppy drive and then load a bootable floppy disk image that cannot be edited. I don't want to actually install DOS and overwrite Windoze. I do want something that will boot directly to the command line, allow me to add my own files and directories and...preferably...allow me to put DOS commands in an AUTOEXEC file. FreeDOS 1.0 has a LiveCD mode still. The used floppy image file is writeable once loaded (to system memory). I don't know if the program that you want to distribute fits inside the floppy part (anywhere between 360KB and 2.88MB) and if you want to write to ramdisk or to FAT-filesystem on harddisk. All I can recommend is to start using an emulator like VirtualBox. 1) Use a CD burning program to create ISO that holds your program 2) Assign it as CD to your emulator 3) Use a bootable floppy image file and assign it as floppy to emulator 4) Boot the emulator and boot from floppy inside it 5) Modify the floppy to suit your goals by A) deleting unnecessary files B) loading CD drivers and accessing the CD-ROM (assigned ISO) C) loading a ramdisk driver and copying CD content to ramdisk 6) Use CD burning program to add the floppy as bootup disk to ISO If you decide to start with an existing bootCD, just delete autoexec.bat from the floppy image part and write your own from scratch to avoid all the SETUP/install procedures. Maybe this is usefull as well: http://www.fdos.org/bootdisks/ *In XP, I can hit F8, boot to safe mode, and get SVGA graphics with VBE that way. But it messes up my desktop and takes a long time to boot. Scitech used to have some UNIVBE drivers. No idea if they still exist. Bernd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Target partition for installation and information displayed by the installer.
Op 22-11-2012 17:04, Peter Easthope schreef: The partition information refers to the hard disk, which is not the intended target. Hopefully the instruction Press 1 to start installing ... to drive C: is correct. In other words, hopefully drive C: is the CF card and not the hard drive which is identified as D:. It's strange that FDISK doesn't list C:. Likely you'll be able to press 'q' as input at the installer screen, which will abort setup. If you definately want to ensure the harddisk isn't listed, temporarily disable your IDE/SATA controller in BIOS or disconnect the connection cables. I'm reluctant to continue with the installation at risk of clobbering data on the hard disk. Shouldn't the partition information at the top refer to drive C: rather than D:? Or is the installer aiming to target the hard disk? I've never seen FDISK not mention C: unless there wasn't a FAT partition yet. You should be able to safely continue, most setup code is written in Batch-script language instead of some compiled program. In any case, there can be only one target part and reference to both C: and D: in this display is a bug, isn't it? Seems like FDISK picked the wrong disk or your machine (or FreeDOS kernel) is happy to assign C: to a drive that's not counted as harddisk but as a huge removable drive. Bernd -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] hard drive question?
Op 13-11-2012 19:12, Single Stage to Orbit schreef: I remember using 32MB partitions :-) That's the 80286 era or so. 386/4MB/40MB/DOS5 is furthest it goes back for me. -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] hard drive question?
Op 12-11-2012 18:14, Karen Lewellen schreef: Hi, interesting read...complete with weikipedia's often begging for real sources smiles. still it seems the novel 7 is older officially than what we are already using. Earlier in the thread you mentioned a 13GB disk seen a bit smaller with all things going wrong. This might mean the system has a BIOS harddisk-recognition limitation, usually bugging out partition management. For reference again Wikipedia: http://en.wikipedia.org/wiki/Dynamic_Drive_Overlay Hopefully the system will accept FreeDOS just fine on the harddisk. Always disliked DDO software, it messed up lots of disk tools. Bernd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] hard drive question?
Op 11-11-2012 16:22, Karen Lewellen schreef: Hi folks, Asking for the person still doing that Dr dos 703 thing. What is the largest drive capacitor for the current edition of freedos? Thanks, Karen 2 terabyte total disksize is the maximum allowed for a single MBR-partitioned storage device if used individually. 2TB is also the limit for a FAT32 partition. No idea about DR-DOS, likely same limitations. I remember the old days of having 4 (primary? extended? logical?) FAT16 partitions of 2GB each, allowing up to 8GB total. All above is traditional BIOS + MBR. Don't know about UEFI system firmware and GPT-formatted storage devices. Don't know about combining drives/volumes (RAID) either. Bernd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] hard drive question?
Op 11-11-2012 19:57, Karen Lewellen schreef: realizing there may be other answers, let me try that again. you are saying if one intends installing freedos as the only operating system on a hard drive it cannot see a drive larger than 2 gig at all? or are you saying that it only creates fat 16 partitions with the gig limit? Meaning you cannot create a fat 32 partition in freedos at all? Ah I see the bottom part of my earlier response confused you, my apologies. There's FreeDOS kernels only supporting FAT16 on which you'd have above issue yes. However by default the FAT32-enabled kernel is used, thus limiting you to slightly over 2000 GB total capacity. FreeDOS can see/use FAT32 partitions up to this 2000 GB size each. All in all, every normally used harddisk will work. Just don't buy a 3TB or 4TB harddisk if intended for usage with DOS. Bernd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Thousands of Run chkdsk: Bad FAT I/O: 0x... messages, error when formatting
Op 10-11-2012 12:11, André Bachmann schreef: Well, all of this problems would be much less annoying if there would be an image on the FreeDOS site which I can simply dd to an USB drive - all of these error prone steps would be unnecessary. Which emulation or (para)virtualisation product uses/produces harddisk images that can directly be 'dd'ed to a physical disk? I've experimented a bit with Isohybrid images (CD image with harddisk header) that can be written to USB stick, but afterwards Windows doesn't like the stick anymore as it wants to format it. Also installing FreeDOS on the same stick isn't that much of a success. USB stick partition layout: * MBR (not UEFI/EFI's GPT) * partition 1: active, primary, (unknown / non-DOS) read-only ISO9660 * partition 2: primary, FAT32, writeable. After writing the FreeDOS CD to partition 1, and booting from the stick, the idea is a small bootdisk image is loaded in memory from this CD filesystem (DOS boots only from FAT, not ISO9660) after which the rest of the 1st partition is accessed. Unfortunately no CD driver exists for this kind of scenario. A workaround is loading a secondary ISO file in memory from this 1st partition, allowing FreeDOS to find its files using the ELTORITO.SYS driver. With the files found, creation and installation to partition 2 is possible Windows insisting on removable media not being allowed to have partitions, let alone using unrecognised filesystems on them, isn't helping at all to proceed. [ http://code.google.com/p/nanox-microwindows-nxlib-fltk-for-dos/wiki/XFDOS ] uses a bootable harddisk image but no individual harddisk image file is available, only a CD which uses harddisk-emulation. Bernd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Thousands of Run chkdsk: Bad FAT I/O: 0x... messages, error when formatting
Op 9-11-2012 16:47, André Bachmann schreef: Hi there, I was going to install FreeDOS 1.1 on a USB drive within qemu 1.1.1 on Opensuse 12.2 32 bit. After selecting the language in the FreeDOS installer, my notebook was busy during the next hour with thousands of thousands of messages like Run chkdsk: Bad FAT I/O: 0x I've seen this as well, usually with a drive C: (primary active FAT32 partition) that didn't have a filesystem on it yet (done by FORMAT) Some installation tools check drive C: to see if it's present. Here is exactly what I did: - plugged in a USB drive - erased all partition data with dd if=/dev/zero of=/dev/sdb bs=1M count=16 - created a new FAT16 partition with fdisk (1 GB, partition label 6), set this to active - created the filesystem with mkfs -t vfat -n FreeDOS /dev/sdb1 You could try providing this USB Flash Device to QEMU without first assigning a partition and filesystem. FreeDOS is able to do it by itself using the FDISK program to create a partition, and FORMAT program (after rebooting QEMU once FDISK has finished). FORMAT C: /Q should do the trick. Afterwards run SYS C: After that, I started qemu with qemu-system-i386 -hda /dev/sdb -cdrom fd11src.iso -boot d. The FreeDOS installer started, I begun the installation with 1. It let me choose my language, and after this the enormous amount of error messages. About an hour later, the installer finally asked me where to install - I chose C: (the installer showed me mysteriously only 255 MB). Then it asked me if I want to format the drive with FAT32 - which I accepted. However, now it showed me the following error message: Invalid Drive! Aborting. [Error 61] FORMAT status: 4 Could not format your hard disk Not seen this error before, sorry. Is your USB stick more emulator-friendly if performing the partitioning with Gparted or something? Standard reference procedure should be something like detailed in: http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox Bernd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FNG
Op 17-10-2012 1:24, ninefofo schreef: Is there a FreeDOS utility similar to memmaker? Need help getting the There's no automated utility. Perhaps you could list your CONFIG.SYS AUTOEXEC.BAT contents? Optimising can be a pain sometimes, especially when big programs like MS-Client (TCP/IP stack) are involved, or specific games. The general solution is a config.sys with contents at least: DEVICE=JEMMEX.EXE NOEMS I=TEST X=TEST DOS=HIGH,UMB DOSDATA=UMB and using LH for drivers, if/when possible. Be aware you can manually finetune the I= and X= parameters to include UMB-regions. Likely the JEMMEX package from Japheth's website contains additional programs to list which UMB regions aren't in use by adapter ROMs. most out of my USB boot. Also, are there USB 2.0 drivers to get the read speeds up? Experiencing any issues regarding reads then? My old system limited USB2.0 ports in BIOS and DOS to USB1.1 speed. With a fast enough USB flash stick that ment 1MB/s instead of 45MB/s. To answer your question, Bret Johnson's USBDOS stack (USB1.1 only for UHCI/OHCI) or Georg Potthast's DOSUSB stack might be able to increase speeds. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDNPKG: FreeDOS network package manager
Op 14-10-2012 0:31, Rugxulo schreef: There are some people who seriously wanted such a thing for FreeDOS, e.g. some random dude on OS News when FD 1.1 was announced. So I guess he'll finally be glad, heh. From what I've noticed it's a big binary, likely due to including wattcp and perhaps also a decompressor. I've not experimented with it, got stuck reading the little amount of documentation that's present. I'm surprised Mike didn't bring up the suggestion of making it MTCP-compatible and thus perhaps also smaller. FDNPKG allows to install packages both from network repositories and from local *.zip packages. Installing from local *.zip implies the ability to run the program without a package driver present. Not everyone has a network interface card, and even if they do, there aren't always packet drivers or shims available. Easy alternative would be adding a public domain or opensource dummy shim so local use is possible. It supports multiple network repositories - this allows anyone to create (and host) his own FreeDOS packages repository (we could imagine internet FreeDOS repositories with old shareware games, or DOS ports of specific opensource projects, etc...). Can a directory be specified? Creating a local config file with loc1 = x:\cdrom\loc1 loc2 = x:\cdrom\loc2 (etc..) seems easy enough to do from a batchfile. While this is still pretty dang cool, I can't help but halfway think that a lot of times it's just easier to host / post / hoard self-made patches (aka, plain text differences or build scripts) than actual binaries + full sources + whatever. It's just lighter and easier (sometimes!) to make people build their own. Getting documentation on how to setup environments for source code management, packaging and even just getting simple diff/patch programs is still a nightmare. Do you have packet driver emulation enabled in DOSEMU? I never did understand how to get that working (to say the least). Hence my only recent experience with working packet driver is inside (buggy) VirtualBox. I'm curious also. Emulated cards in emulators are the least of worries. Connecting virtual network cards to real networks seems like a horrible configuration issue. P.S. I've also done some packaging repackaging work, and created a few FDNPKG repositories for FreeDOS, containing some development tools, FreeDOS BASE packages, utils, etc (they are all referenced in the default FDNPKG configuration file, so you can browse them using fdnpkg search). Much appreciated. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ISOLINUX - ISOHYBRID
Op 6-10-2012 12:00, nospam schreef: I try to run the ISOHYBRID utility on the fdbasecd.iso file while running I assume under Linux? Or did you find a Windows/DOS compatible version (perl script + interpreter packed together in single binary) ? Linux. ISOHYBRID returns with the error message: boot loader does not have an isolinux.bin hybrid signature. Get a non-debug build of isolinux.bin (version 4.05 recommended, or alternatively 3.86 as that still supports disk image mapping). http://www.kernel.org/pub/linux/utils/boot/syslinux/ The FreeDOS binary is most likely a debug build that I renamed. Already replaced the isolinux.bin file on the fdbasecd.iso with a later version but the message remains. I'm using the Windows isohybrid.exe binary linked from post #5 at [ http://chakra-project.org/bbs/viewtopic.php?id=2090 ] Does anyone know what has to be done to get ISOHYBRID to postprocess the fdbasecd.iso file? For a test I need a bootable FreeDOS version on a hybrid ISO image. Did you get the isolinux menu working on the non-hybrid image you created? BIOS - CD - isolinux.bin - isolinux.cfg - memdisk - 0x80memc.img Perhaps Jeremy's bootdisk/CD builder projects are usefull, I noticed Asus had used it on the motherboard CD on my new machine (instead of floppy emulation only). http://www.fdos.org/bootdisks/ if you're still out of luck I might be able to mail you a 1MB isohybrid ISO file. Bernd -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (no subject)
Op 20-9-2012 0:53, George Brooks schreef: device=c:\net\yuknd.dos I'm not entirely up to date with this subject nor the mail thread, but usually MS Client NDIS drivers are loaded in a slightly different way. You'd have to install MS Client and supply the drivers when MS Client asks for it. Alternatively there might be ready-to-run bootdisks or configuration tricks available on the internet through Google on the subject of providing modern NDIS drivers to MS Client. When stepping thru boot, this line results in the error message Controller not found. What means, if any, are available to get over this? (The laptop also has wireless, but I suspect that is even more highly problematic.) From CONFIG.SYS I can only remember PROTMAN or IFSHLP being loaded, rest goes into AUTOEXEC.BAT or MS Client configuration scripts. Printer mapping to LPT1 (Parallel Port) in VMware should also be an option. -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem running a DOS game requiring EMS inside of VirtualBox
Op 21-9-2012 0:20, Louis Santillan schreef:
Wayback when ('94/'95), I had this running perfectly fine on MS DOS
6.22, Win95, Win98 (boot to DOS).
Then get it working again like this, and additionally/optionally swap
out components (memory drivers, shell, kernel) to see which the culprit
is. Despite all the progress in alternative DOS flavors like DR-DOS and
FreeDOS, behaviour of hardware/software still needs to be checked
against the de-facto standard reference operating system MS-DOS.
Sites like www.bootdisk.com could be usefull. When lacking a real
floppydrive, WinImage might help to extract the self-extracting content
(open WinImage, and browse from within there for the win98se.exe and see
contents, then extract to a directory).
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem running a DOS game requiring EMS inside of VirtualBox
Op 18-9-2012 8:05, Louis Santillan schreef: I verified the game won't run with 64M, 32M, 16M. They all fail with the EMS error. Added LOAD to the JEMMEX line as well. No positive effect. Host is an Apple Mac Mini 2.3GHz C2D with 16GB RAM running the latest Virtual Box 4.2. The VM is configured with VT-X. *If* you're interested, you can find out more about the game here (http://www.fbpro-online.com/). Easiest way usually is to try with a Windows / MSDOS (boot)disk and see if the operating system and associated drivers (HIMEM/EMM386) are compatible with your application/game. Afterwards you might try replacing the memory drivers (HIMEMX, JEMM386 or JEMMEX) and even shell (COMMAND.COM) or kernel (KERNEL.SYS instead of IO.SYS/MSDOS.SYS). This way you're able to verify if your game works at all under the OS that the game should work on anyway (MSDOS). -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos in VirtualBox not a sure thing
Op 16-8-2012 0:46, john s wolter schreef: I spent four days getting FreeDOS to work as a guest OS inside a VirtualBox machine. The path to success was a rocky and time consuming trial and error process. Once the particular console program was running it was not very fast. The customer deemed it to be usable. http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox is a general guide, it's not as network-specific though as http://lazybrowndog.net/freedos/virtualbox/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New XFDOS FreeDOS distribution
Op 5-8-2012 23:35, nospam schreef: yes, Robert also found that the ISO image will not run with VMware and VirtualPC. I had tested it with Bochs and that did work. I agree that you can use Bochs mainly for development because it is slow. QEMU might also be an option, faster than Bochs. Not tried [ http://qemu.weilnetz.de/w32/2012-06-28/ , QEMU v1.1 I think] yet, I'm too lazy to find out how to download an entire web directory in 1 go. Guess some FireFox extension should allow it. The ISO is an ElTorito CD using FAT16 hard disk emulation. BIOS has no problem booting from that. I did expect users to write the ISO image to a (e.g. re-writeable) CD and boot from that. This should work well with your existing PCs also. Like above, I'm lazy hehe. The Zalman VE200/VE300 enclosures are able to represent ISO files as hardware DVD device if booting from USB. Same for the upcoming ISOSTICK [ http://www.kickstarter.com/projects/elegantinvention/isostick-the-optical-drive-in-a-usb-stick ] If you have instructions somewhere how to add my files to your FreeDOS 1.1 ISO and then make a new bootable ISO image from that I will give it a try. Since the BIOS and Bochs have no problems with my ISO image I did not expect problems with VMware and VirtualPC. I'd have to look up my IMGBURN settings for that, and analyse your CD layout as well. Saving that for when I got 3 weeks vacation, away from work. Bernd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (no subject)
Op 5-8-2012 11:57, Mark Brown schreef: how do you set up the c: drive, format, and sys the drive under vmware workstation 8? very short replies are fine. 0) use a FreeDOS bootdisk(-image) or installation CD. 1) run FDISK (and create active primary FAT/FAT32 partition) 2) reboot so BIOS/kernel recognises new partition 3) FORMAT C: 4) SYS C: -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New XFDOS FreeDOS distribution
Op 30-7-2012 19:36, nospam schreef: Please download XFDOS and see how it works for you. I'll have a look once in possession of ordered Zalman Ve200/300 and proper SSD to go in it, so I can test on real hardware. VMware at least still only shows a black screen on all of this. My intention is to have Win8 (Windows-to-go) on this external SSD, along with Syslinux 4.06 (NTFS) and plenty of ISO's including ofcourse various FreeDOS ISO's that people create (and FD 1.2 that I'm still very slowly working on). Bernd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Searching FDBOOTCD.ISO
Op 20-7-2012 15:06, Christian schreef: I downloaded the latest fd11src.iso version too and checked for a bootable dos-image. Again I'm about to be clumsy but within that more recent package I do *not* find some file that looks like a bootable dos-CD-image. What are you expecting as 'dos-CD-image' ? Usually a CD-image is an *.iso file and already represents the entire CD. That probably means you can rightclick the downloaded ISO file and select to burn it. Note that some archivers/compressors (7zip, winrar, winzip) and other tools (WinImage) can access contents of an ISO-9660 file also. Is there really an image ready to boot contained in fd11src.iso? And if so: Can you help me with the file's name, please? The emulated floppy boot image file is FDBOOT.IMG and is 360KB in size, it can be converted to 1.44MB by using WinImage for example. Ready to run floppy disk images can be downloaded from [ https://sites.google.com/site/rugxulo/ ] Boot order for loading FreeDOS from CD is: BIOS - CD - bootsector - bootcatalog - isolinux - memdisk - FDBOOT.IMG (this also means the CD uses non-emulation eltorito bootmode, instead of disk emulation for floppy and/or harddisk). Bernd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] adding executable file to FreeDOS 1.1 installation image
Op 1-7-2012 16:55, Martin T schreef: to find a solution to boot FreeDOS from USB memory stick :) try the RUFUS program (search for RUFUS DOS USB on Google), it creates a FreeDOS bootable USB stick with only the bare required files. Specially created for flashing BIOS now that optical drives are heading the way of the dodo. Note it's a win32 program though. thank you for those commands! Am I technically correct that DEVLOAD ELTORITO.SYS /D:CD loads the CD-ROM driver(is able to read CD's with ISO9660 file system with El-Torito extension) and associates this driver with name CD? And shsucdx /D:CD /Q associates drive C:(or next available) with the driver called CD and presents the C: as a network drive to the rest of the system? Correct, and you can tell SHSUCDX which driveletter to use instead of depending on whatever next one is available. My example used X: -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] adding executable file to FreeDOS 1.1 installation image
Op 26-6-2012 19:39, Martin T schreef: Geraldo, thanks, I'm fine. In case I boot the freedos.iso image with qemu -cdrom freedos.iso -boot d -m 128 and try to access any drive other than A:\, I get the Invalid drive error: @ECHO OFF echo Loading EL-TORITO ISO9660 non-emulation driver as FDCD0001 DEVLOAD ELTORITO.SYS /D:FDCD0001 echo Assigning driveletter X: to block device FDCD0001 SHSUCDX /D:FDCD0001,X DIR X: or: echo Loading ISA/PCI IDE/EIDE/ATA/SATA optical drive device driver DEVLOAD UIDE.SYS /D:FDCD0001 /N3 /B echo Assigning drive X: SHSUCDX /D:FDCD0001,X -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS with MS Client - mem optimization
Op 13-6-2012 0:28, Rugxulo schreef: Just another quick mention, I stumbled upon a website with a very similar set of tips which may be interesting: The problem ofcourse is that MS-Client is a real memory hog, thus making a lot of memory optimisation useless. Perhaps MS Memmaker or QEMM's Optimize were able to take this scenario into consideration? I wonder if VMware's virtual shared folders can be used as an alternative, with on DOS client's side using VMSMOUNT program. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS with MS Client - mem optimization
Op 10-6-2012 20:12, czezz schreef: Now I have have 480 KB of free memory Therefore Im asking here, can anyone please take a look at my autoexec.bat and fdconfig.sys and help me to improve it ? http://dl.dropbox.com/u/3403127/AUTOEXEC.BAT http://dl.dropbox.com/u/3403127/FDCONFIG.SYS FDCONFIG.SYS: 1) add the monochrome area: add I=B000-B7FF (without quotes) at end of JEMMEX line. See JEMM386 line. Please test if this works for you. 2) replace I=TEST X=TEST by I=C800-EFFF and test if this works for you. This kinda bruteforce adds most of the upper memory to your DOS client without much consideration for controller firmware. Additionally there might be some graphical tools to list which exact UMBs are assigned/used/available/unused. I've always liked MS's MSD.EXE program for this. AUTOEXEC.BAT: 1) use ALIAS REBOOT=FDAPM COLDBOOT (same for reset alias). MS-Client seems to require coldboot instead of warmboot, to get eliminated from memory. Or it's yet another VirtualBox flaw, who knows. 2) set the LH lines as follows for MS-Client (netbind/protman isn't LH friendly at all..) LH C:\NET\NET INITIALISE C:\NET\NETBIND.COM LH C:\NET\UMB.COM LH C:\NET\TCPTSR.EXE LH C:\NET\TINYRFC.EXE C:\NET\NMTSR.EXE REM C:\NET\EMSBFR.EXE LH C:\NET\NET START MEM /C /N As the AMD PCNET DOS driver uses 27KB, it might be worthwile considering switching to another network card if you can find drivers for it. Maybe the Intel ones. I seem to remember also that MS-Client had a limited memory mode option somewhere that reduced a bit of functionality and lots of buffers. If that helps, here is also a link to my VBox image file: http://dl.dropbox.com/u/3403127/FreeDOSMSClient.zip This helped quite nicely to experiment quickly, thanks. Legally/technically you'd be in trouble though for distributing Microsoft's copyrighted software. Then again, projects like NWDSK and Netbootdisk also. Bernd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS with MS Client - mem optimization
Op 11-6-2012 23:10, czezz schreef: http://dl.dropbox.com/u/3403127/20120611/error1.PNG http://dl.dropbox.com/u/3403127/20120611/error2.PNG http://dl.dropbox.com/u/3403127/20120611/error3.PNG Any ideas what is that ? Please note: if I revert FDCONFIG.SYS to original (no MS Client) then program starts (MENU 1). You can always try to keep FDCONFIG.SYS's JEMMEX line as it original was. So X=TEST I=TEST Additionally, try I=B000-B7FF. End result for me in your Vbox was 500KB low memory available, which should meet your goal. Only the I=C800-EFFF resulted in lots more upper memory but is likely also the cause for the issues/corruption you're experiencing. The PNG links don't open for me at the moment, no idea why. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and DOSUSB?
Op 6-6-2012 17:08, cordat...@aol.com schreef: On most OHCI drivers (including DOSUSB), the driver will load but then the keyboard starts acting erratically. (I'm using PS2 keyboard not USB) Effectively the computer is not usable at this point - I suppose I could write a batch file to test whether it is strictly a keyboard problem or if there are other problems. I've succesfully used Georg's DOSUSB v2.0 with USB flash drive containing a single active primary FAT32 partition. Problem is my USB keyboard then typically gets disabled as DOSUSB replaces BIOS drivers by its own stack, but a keyboard driver isn't present currently within DOSUSB. My final solution was to get a PCI-express USB 3.0 controller card. As add-in cards aren't bootable (no bootrom, no driver in BIOS) nor seen in DOS, I'm booting from some slow USB flash drive, which loads DOSUSB 3.0 and thus gains access to the fast flash drive connected to the add-in card. As all other devices are on USB1/USB2 ports, they don't get disabled by the USB3-only DOSUSB 3.0 driver. All in all, this works pretty well for me. The downside is that the slow USB stick that I boot from, gets drive C: assigned, which I dislike. Messing around with Syslinux, Memdisk and floppy image files works around this nicely, so I can keep C: available for either a ramdisk drive, or for the USB3.0 flash drive. Alternative options are loading this driver from a floppy drive, or cdrom or something, but that's slower. If this device you're loading from is USB as well, you're in trouble as soon as loading DOSUSB v2.0 (it resets the controller, thus also the connected drives, and you end up with a hung system). DOSUSB will find the device and set up a drive. If I use a FAT16 device I can get things working reasonably well but a directory listing will wind up crashing the system and creating all sorts of bad behavior. (Yes, I understand that directory listing may take a long time but my expectation is that it would not crash the OS) I've experienced that DOSUSB sometimes needs a bit longer initialisation time. You might also want to check the errorcode generated by it. My way of solving it was to load and unload DOSUSB a few times, once no more errorcode, I load USBDISK.SYS so the USB flash disk gets mapped. If I use a FAT32 device all hell breaks loose when trying to access the USB disk, FCB error messages or other scrolling messages pop up and the computer must be reset. Any other older kernels or MSDOS suffering the same behaviour? I've got most luck with JEMMEX combined with DOSUSB. Anyway, I'm hoping my next machine can boot natively from USB3.0 ports/devices in UEFI (and BIOS!) at above-USB2.0 speeds. Heck, Apple even made FireWire (and Thunderbolt?) bootable on years old EFI. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem
Op 22-5-2012 6:21, Rugxulo schreef: Is anybody working on FD 1.2? I haven't heard anything (and don't think we need it just yet anyways). Switching things around is, I guess, that person's ultimate decision (Bernd??). I'm indeed working on a FreeDOS 1.2 as 1.0 and 1.1 didn't meet up to my own expectations ( 1.0, despite Blair and Jeremy's awesome work, lacks some features I'd like, and 1.1 lacks lots of things present in the full 1.0 ISO). I hate to open up a can of worms (so tedious ...), but did Bernd or Jeremy ever publish any scripts to build the .ISOs? Meh, just the idea sounds difficult. Bah. But we can still dream, can't we? ;-) I'm doing stuff manually mostly, in Windows. No source code management system, no compilers, build environments, packing scripts and building scripts. Jeremy's FDOS (FreeDOS Distribution Of Sorts) has more automation behind it, and I guess Blair had lots of automation as well. It already shows the difference between structured approach by programmers versus my own ad-hoc approach. PPS: Heat-wise (VirtualBox Chapter 7) I suggest to add FDAPM to one of the default driver sets in FreeDOS 1.1 config / autoexec. VBox lets you choose how much % of processor to use, so it doesn't have to use 100% all the time. I just wonder whether their bugs are due to their tweaked BIOS or some hidden instruction incompatibility or what. :-/ I've seen some slower performance when FDAPM is active so I'm a bit cautious at installation time. At runtime it's great though. I'm not ready to disclose anything about 1.2 yet as there's still lots of structural stuff to integrate and rewrite. Bernd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem
Op 22-5-2012 16:05, Jack schreef: PCI V2.0C and later versions have all worked just FINE, until the rather poor emulator know as VirtualBox appeared, using its MISERABLE emulation logic for the Intel PIIX3 chipset!! If they DO NOT have such long delay trouble with their ICH9 emulation logic, do you REALLY expect we should believe the PCI BIOS logic is now at fault, after almost 20 years?? The VirtualBox brats should take a long-hard look at their ICH9 v.s. PIIX3 routines, and CORRECT those for the PIIX3!! The easiest case is to have a bootdisk with UIDE on it, and present it to the VirtualBox people as hey this completes in under 7 seconds on all hardware platforms and every popular emulator, except yours. Actually, an autoexec.bat like this should do fine: @ECHO OFF RUNTIME DEVLOAD UIDE.SYS /S5 /H /D:CDROMDRV with a corresponding config.sys of: DEVICE=XMGR.SYS /PA (the /PA is optional but seems to be more stable for A20 on anything Syslinux/Memdisk related, especially in VMs) Simply run the bootdisk under various hardware environments and write down the reported time. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Virtual floppy change problem
Op 20-5-2012 22:40, dmccunney schreef:
So how many people *are* trying to run FreeDOS under Virtual Box?
Page views != unique users.
No idea, the guide acts as a very nice general installation manual.
Combine that with the presence of multiple emulators (QEMU, Bochs,
VMware) as well as some actual installations, and you get inflated
numbers indeed.
But they would still be a tiny fraction of the total number of Virtual
Box users.
True. Lots of people will likely virtualize additional functionality, be
that generated by Linux, Windows, ReactOS or another operating system.
Of course to the developers of VirtualBox those people are a minority, so
known bugs aren't fixed very fast or not fixed at all.
It appears that VirtualBox developers are taking the easy way out,
creating virtual machines that work properly for specific operating
systems instead of being a proper complete virtualisation product. In
other words, the VM is incomplete, not acting like real hardware would.
VMware (Workstation, Fusion and ESXi), Bochs and QEMU appear to do a
better job of complete emulation, with VMware (and to a lesser degree
QEMU) adding optimalisation for specific operating systems ('virt-io'
devices and drivers included..)
I know why a bug in Virtual Box might be important to a FreeDOS user.
Tell me why that bug should be important to a Virtual Box developer,
beyond the fact that it's a bug? All bugs are not created equal, and
some are far more important than others.
What you mention unfortunately is reality indeed. Instead of creating a
proper product with full functionality and afterwards improving, only
just enough functionality is provided to get popular operating systems
going. In some ironic way, this resembles real hardware :)
(specific quirks mentioned at http://mjg59.dreamwidth.org/ )
The question is if those users should be more valuable to the FreeDOS
developers / FreeDOS community.
Unlikely. However any and every bug with regard to machine emulation
should be fixed to get rid of imperfection. Afterwards all that users
can complain about then is performance rather than functionality.
I assume the FreeDOS community considers all users of value. I'm not
sure how having FreeDOS under Virtual Box users seen as more valuable
to the FreeDOS developers/FreeDOS community addresses the issue of
problems running FreeDOS under Virtual Box, unless it's possible to
add code to FreeDOS to work better with Virtual Box and/or work around
Virtual Box bugs..
I know Michael Devore added a feature to FreeDOS-EMM386 (and thus also
present in JEMM/JEMMEX) to exclude a certain UMB memory region if
running in VMware. It was done at my request, as otherwise the VM would
reboot or crash. Not everything can be worked around for in drivers or
operating systems, if the system environment is flawed.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Prevent boot from Floppy?
Op 21-5-2012 0:17, Ralf A. Quint schreef: Is there a way to make FreeDos ignore that there is a floppy present upon boot, i.e. force a boot from the harddrive? Again only a problem when running it in a VM, I think, as on a hard PC, you may set the boot options in the BIOS. Try to think about this for more than a second! How is FreeDOS supposed to decide from which media it is to be booted? (You have heard about the chicken and egg problem before, haven't you?) As Ralf implies, the boot order is something specified by the system firmware (BIOS) that's part of the system environment. In other words, set the boot order in the virtual machine's BIOS (for example F2 in VMware). QEMU uses a batchfile I think (for Windows at least) to specify bootorder (passed on to SeaBIOS), Bochs uses some config file. No idea about VirtualBox though. QEMU is a bit troublesome to learn though, so many options. QEMU Manager is a nice GUI in VirtualBox-style but is a bit older and uses older QEMU versions. Worst coming to worst, you can: 1) remove the floppy drive alltogether from your virtual machine 2) setup a bootmanager on floppydrive (MetaKern for example, or Grub) 3) setup a bootsector to diskette that chains to harddisk. If the VM's BIOS is smart, you can disconnect the contents (image file) from the virtual floppy drive and thus next boot device (harddisk) will be considered. Or maybe it tries floppydrive but only finds a non bootable disk there so jumps to next boot device (harddisk). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] sata drivers for cd, dvd, and hard disk
Op 14-5-2012 19:47, Mark Brown schreef: where are the easiest to install (and use) drivers for freedos? Depends what you need/want. * Modern IDE/PATA/SATA over PCI/PCIe: http://johnson.tmfc.net/dos/driver.html Others: * Ancient PATA over various busses: no idea * Ancient IDE/PATA over ISA/PCI: oakcdrom.sys/vide-cdd.sys (win98) * SCSI/USB/Firewire/Serial/Parallel: no idea * bootCD: Eltorito.sys , part of Syslinux bootloader suite * RAM-CD: no idea. * Disk-CD: no idea (Isohybrid) * CD-images: SHSUCDX suite -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Computer Crashed
Op 6-5-2012 21:31, Kenny Emond schreef: JemmEx v5.75 [05/21/11] JemmEx loaded Kernel: allocated 46 Diskbuffers = 24472 Bytes in HMA JemmEx: exception 06 occured at CS:EIP=12E5:D1D1, ERRC= SS:ESP=12E5:01F4 EBP=0001 EFL=00033A47 CR0=8011 CR2= EAX=0006 EBX=000F ECX: EDX=090D ESI= EDI= DS=090D ES=029B FS=0030 GS=0010 [CS:IP]=FF FF 0F FF FF FF 0F 8B Press ESC to abort program For a starter, remove any and all of the following lines: DOS=HIGH DOS=UMB DOS=HIGH,UMB Bad or missing Command Interpreter: C:\FDOS\BIN\COMMAND.COM http://COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT Enter the full shell command line: Usually it's enough to enter C:\COMMAND.COM or C:\FDOS\BIN\COMMAND.COM when this issue crops up. P.S.- How exactly do I reply to the posts on the FreeDOS-User group? I use gmail. https://lists.sourceforge.net/lists/listinfo/freedos-user Enter your Gmail address there and pick some password, preferably a unique one, thus different from your email password. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Help with loading Freedos on a compact flash card
Op 6-5-2012 22:23, k4...@aol.com schreef: I am new to the list and would appreciate some help loading a bootable version of Freedos on to a 1 GB compact flash card. This is for a small PC-104 system I have. Several years ago I had a version that was on a floppy (1.4 meg). Later I got a CD for loading bootable Freedos on to a hard drive. But this version takes much, much more disk space than what the floppy did. Is there a bootable version of Freedos that will fit on my compact flash card that doesn't require so much space? Usually SYS X: does the trick, where X: is the driveletter assigned to a FAT32 formatted storage device. If you're working on Windows, have a look at RUFUS, found at [ http://rufus.akeo.ie/ ]. Under Windows, it performs all the partitioning, formatting and bootsector manipulation in 1 go. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Next mTCP release (2012) - wish lists and ideas?
Op 21-4-2012 5:51, Michael B. Brutman schreef: If you have an idea let me know. I can't get to everything, but if the idea is good it will definitely get priority. Small tweaks to the existing code are always possible to. * DHCP client that also writes WATTCP.CFG, so 1 dhcp-request keeps both TCP/IP stacks in synch. * Twitter client? Just came to mind, modern communication through ancient operating system ^^ -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.1 install errors...
Op 11-4-2012 20:02, Rugxulo schreef: Users will always need sources, esp. if they share, but they don't necessarily need to unpack them. (Well, anyways, they probably don't have all compilers anyways.) The entire idea of opensource was to be able to modify sources to suit a person's needs. Most people, including me, haven't got enough interest or experience to be a programmer, but still, a bit of messing around and see what happens, should be possible. Keep in mind that outside of FDXMS286, there is no XMSv2 only driver, esp. for 286s that is the only one that (allegedly) works. And obviously XMS doesn't work at all on 8086 or 80186. The combination of 01) System firmware (BIOS/EFI/UEFI/Coreboot) 02) Controller firmware (PCI IDE/SATA/USB controller) 03) Boot Manager (GRUB/Syslinux/Memdisk) 04) Boot Loader (boot sector usually) 05) Kernel (FreeDOS/MSDOS/DRDOS etc) 06) Shell (FreeCOM/4DOS) 07) Memory driver (XMGR/HIMEMX/JEMM386/JEMMEX 08) Other drivers (SHSUCDX etc) 09) Programs (KEYB, DEVLOAD UIDE.SYS) 10) Settings (DOS=HIGH / DOS=UMB / DOSDATA=UMB) can be horribly misbehaving in some cases. With my own testing I found JEMMEX more compatible than XMGR or HIMEMX + JEMM386 in various cases, but on other systems it's different, as Mike mentioned. My preference would be no XMS driver at all, and only load as needed/wanted. If the MEMDISK stuff in FreeDOS kernel 2041 works properly (guess it's not compiled in by default? not sure?) I could offer which memory driver to load already from the Syslinux menu. But I thought the default installer (since on CD) was 386+ anyways? Or at least default requirements. So just use DJGPP UNZIP32.EXE (or whatever it's called), it can run in raw (no mem. managers) just fine. If you really want, you can include both 16-bit and 32-bit UNZIP*.EXE files and choose dynamically at runtime (cpulevel.com, if errorlevel 3 unzip32.exe). At least this way won't be painful unnecessarily for 90% of users. Copy proper decompressor somewhere and set path? Sounds like a nice option. Yes, but some DOS settings are quite limited by default, so sometimes F8 is better. PATH and DIRCMD usually come into my way. For others, language/keyboard stuff might be quite relevant as typing blindly on keyboards with different layouts is confusing. Yay laptops from Belgium :) I agree with Eric, but it's your call, Bernd, obviously. ;-) Only done when needed (no C: present so offer FDISK if possible, or ramdisk which requires XMS which requires loading driver). We hopefully do not have many such programs anyway...? Flashrom is one such program at least. 4DOS might be another. P.S. I guess you know 7zdecode.exe is much smaller than p7zip. Or are you just letting the end user figure out how to unpack it? ;-)Oh wait, p7zip itself can't build (easily?) on FreeDOS, heh, now that's one behemoth of a package (slow to build). Your used extender for 7zdecwat.exe wasn't compatible with public distribution, so I can't use it. A 386+ build of UPX-UCL v3.08 wouldn't hurt either :) -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Programming languages in FreeDOS
Op 11-4-2012 20:25, Rugxulo schreef: (PS: If we have FreeDOS code that doesn't compile under OW I'd be interested in seeing it. A few #defines can fix a lot of problems. The debugging is the hard part.) There is a tcc2wat library by Blair Campbell on iBiblio, if anyone wants to take a look: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/tcc2wat/ http://www.devoresoftware.com/nomyso/ was a script used for converting FD-EMM386's sourcecode back in the days. Might be usefull for other programs as well. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.1 install errors...
Op 10-4-2012 18:21, Eric Auer schreef: it seems even on modern hardware unpacking FreeCOM during install may take VERY long, so we need a fix: This seems to be specific to the old installer (v3.7.8 by Jeremy) I think, as that unpacks entire packages. Sourcecode modification would be required to add a -x source/*. Alternatively, or additionally, if someone modified the new installer (v4.01 by Jim) to switch to destination directory after unpacking files, that would also work. - it is good to have source and binary in one zip There's some disadvantages though, download size being one of them, memory size and loading times in other specific conditions. A 16MB binary-only ISO has its merits also. - but you can use info-zip's command line options (-x source/*) to exclude sources from unzip :-) New installer already does this, reason why this new installer isn't unconditionally enabled yet is that I dislike having to search entire partitions for a single (post-installation) file just to find out where files were installed to. - a default install does not need sources, as the user can always fetch those from the zip later I've never liked programs with many options/switches, so confusing and often also lacking examples. - users should be warned that install without XMS drivers will be horribly slow due to lack of RAM I intend to offer loading of XMS driver at runtime as an option. (JEMMEX LOAD or DEVLOAD XMGR.SYS). However this doesn't solve low memory situation as FreeCOM can't relocate itself. Hence my perhaps decade-old request to have a tiny init shell that spawns, in a loop FreeCOM in a non-permanent way, so FreeCOM can be started a second time automatically if exiting the first FreeCOM instance. With that, automatic relocation to XMS. SHELL=TINYCMD.COM C:\COMMAND.COM C:\AUTOEXEC.BAT - actually I would not even OFFER a boot menu item to skip loading the XMS driver at all: You cannot even boot the install CD / USB on old pre-XMS PC. Excluding sources from unzipping instead of unzipping and then deleting them also saves CPU time and disk activity time and temporarily disk storage space :-) Deleting files can take ages indeed. By the way, I'm considering 7-zipping sourcecode of programs that can't be compiled in DOS. Saves a bit of space. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 32 bit FreeDOS?
Op 8-4-2012 8:17, Michael Robinson schreef: Actually, I wish someone would release a Windows 3.1 driver that can get my ATI Rage 128, XPERT 2000, card to output 256 colors. For that matter, how hard would it be to make a Windows like graphical user interface that can run Windows 3.1 software? There should be some unofficial svga patch for windows 3.1 / 3.1.1 , but it had several limitations. What might make sense is being able to dedicate one core in a multi core 64 bit computer to running freedos via say a hypervisor. A hypervisor is a simplified OS where it's sole purpose to exist is to create a virtual hardware environment for other OS'es. Despite a lot of hardware being capable of it, it's still not simple to setup Citrix Xen or VMware ESXi. Linux-KVM (or QEMU-KVM, whatever) is also not simple, nor vga-passthrough. Dosbox seems to run on any modern computer at this point. Syllable is very interesting from the standpoint of being simple, but the project needs more help. Any tiny operating system that QEMU can run on top of, would be interesting. I'd consider Dosbox a bit too limited. I think the number one source of complexity today in operating systems is that companies which produce computer hardware are Microsoft Windows NT centric. In other words, they develop for a proprietary OS and keep their mouths shut about how their product is actually laid out. Linux gets a bad rap because many modern graphics cards don't work 100%, especially AMD video cards. If there was enough competition like there used to be and people were more aggressive about using open source OSes, companies wouldn't be able to survive keeping their mouths shut and focusing on NT only. AMD and NVIDIA do release Linux drivers, but they are always deficient which I think is on purpose. Things are being kept vague on purpose it seems, nobody considers interesting aspects. For example, my current motherboard inits USB ports (1.1 and 2.0) at 1.1-speeds till an operating system driver is loaded. With recent hardware releases, I'm interested in a new board that can boot (DOS/Windows/Linux) from USB 3.0 (in BIOS-mode, not UEFI-only mode), at 3.0-speeds outside operating systems. I can check motherboard manuals all I want, but no info whatsoever. Same for FireWire booting (which nobody bothered with except Apple). As for graphics Linux drivers, there's manpower to be considered as well as how economical it is to set people to them, thus inherently flawed. At the opensource side there's patents and intellectual properties to consider before transferring features from binary drivers to opensource drivers. If you want to be able to run Windows software, help the ReactOS people. ReactOS has a long ways to go where I think significantly more help would improve the outlook of people who have been working on the project a long time and overall increase productivity. Testing ReactOS is helping. Say you reverse engineer a piece of modern ATI/AMD hardware that a lot of people have which doesn't even work well in Linux. As despicable as Windows 8 appears to be with its interface, I might still get it for the following features: * Native USB3.0 support (hence wanting usb3-booting system) * Windows-To-Go (Windows installed/usable on 32GB+ USB Flash Device) * Able to run Windows software properly. Linux has a bit more issues with that last point, the earlier 2 are already possible. Main desktop might stay Win7 or convert to Linux, who knows :) As for ReactOS I'd hope someone's willing to integrate a Ramdisk-driver with MEMDISK (or GRUB) detection so LiveCD and installCD can be booted from file instead of CDROM. It would create independence from UniATA and troublesome IDE/SATA/AHCI controllers as well. PartedMagic Linux-distro has done this already. FreeDOS also, in a few specific ways. Something I've been mulling over is putting together a company that only produces standards compliant computer hardware where the standards are open ones that are readily available to everyone. It would be a big jump though to go from a B.S. in computer science to a company producing computer hardware that is both cutting edge and OSS compatible. What would the business model for such a company be? You'd be nicely off acting as a Coreboot consultant, implementing it on actual hardware. Asrock E350 motherboard is supported, have fun creating a fully opensource machine. QEMU might be a good way to practice first though. Selling self-made ZFS-boxes (as NAS) might also be something nice, or passive Linux-based HTPCs. Consultancy and support seem to be a few ways to make a living from opensource software. Selling opensource systems might become hard, the Raspberry Pi is around as a nice cheap experiment for people. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor
Re: [Freedos-user] Freedos 1.1 install errors...
Op 8-4-2012 19:44, Michael B. Brutman schreef: Some of us figured out that on ancient hardware (8088, 80286, etc.) the decompression process takes a long time. If you are running in a virtual machine and your underlying hardware/operating system does not fully support virtualization then you are emulating the machine instruction by instruction, and that can take forever too. Yeah Jim Hall insisted on combining source and binary into a single package so I've done that. The advantage is GPL-requirements are easier met this way, disadvantage is unpacking takes longer. Unpacking on a system without XMS-driver loaded from CONFIG.SYS is a nightmare, caused by a lack of memory. As FreeCOM can't relocate itself once XMS is available, we're in trouble and UNZIP gets very small decompression buffers. I've seen this happen with TDSK also taking 100KB low memory. My 2009 vintage Intel quad-core supports virtualzation well so I have very little instruction emulation. But a user with a newer Atom tried it and noticed the horrible slowdown. Apparently the Atom isn't fully capable of virtualization so QEMU was resorting to emulating each instruction, and that is very slow. I think I mentioned somewhere FreeDOS installer unpacking everything in 28 seconds, but that was with C: a RAMDISK and the FreeDOS CD contents also in ramdisk, using SHSUCDRI. That's real hardware, I still have to test in virtual machines and make things more robust. Bernd -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS lists messages
Op 9-4-2012 1:46, jasse...@itelefonica.com.br schreef: 1) there is not any useable .pdf viewer nor editor muPDF was ported a while ago, listed on BTTR forums somewhere. Still not experimented with it, nor anything else announced there. My usual experiments involve VMware but graphics modes isn't its forte. 3) there is no javascript enabled browser, and the only one that supports https/ssl is Lynx. I'm not sure of DILLO's capabilities. 4) Neither there is any CAD program that allows viewing or editing a .dxf file. These are just examples that came to me now. No idea what a dxf file would be, guess there's always ancient AutoCAD. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Concerned about a site...
Op 9-4-2012 22:55, someone schreef: There is a site that is putting out a bootable CD that allows you to reset NT passwords. Problem I see is, the OS used is freedos and the disc costs $34.95 to activate. I don't think they are charging for freedos, but there is a free Linux based password reset available if you google some more. http://www.password-reset.com/ Is the way freedos is being used here legal, or have I discovered an abuse? Perfectly legal, though they're required to provide sourcecode for all GPL components to clients on request. Motherboard vendors often also have a driver CD with FreeDOS included. It tends to be for doing DOS-based system firmware updates. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Website Home Page Suggestion
Op 1-4-2012 18:22, Bob Cochran schreef: Yesterday, I did a lot of work aimed at making a bootable FreeDOS USB key. I looked through the FreeDOS website to find help for creating such a key. Others on this forum have kindly helped me with creating a bootable CD back in January; this time I wanted a bootable USB drive with FreeDOS. The specific reason is to allow flashing of an LSI SAS HBA controller card to what they call IT Mode. If you've got Windows, then the tool RUFUS ( http://rufus.akeo.ie/ ) is a nice starter, as it partitions and formats an USB Flash Drive and puts DOS on it (or something else, if pointing to an ISO file). I'm planning to release the next FreeDOS bootable CD-ROM image file as a so-called iso-hybrid file, which has no disadvantages to a normal ISO (except maybe size increased to nearest megabyte) but can be written to USB-drive (or harddisk) using a raw-writing tool like 'dd' that exists on Linux. The old way I created bootable USB keys was on Windows the HP USB tool (which RUFUS now replaces completely) or otherwise install syslinux to it, together with chain.c32 and kernel.sys / command.com / sys.com and a syslinux.cfg so Syslinux would boot FreeDOS after which I'd run SYS to replace Syslinux by FreeDOS bootsector. I think there's some FreeDOS bootsector perl-script for Linux as well, created by Eric Auer. I would like to suggest that a link to making a bootable USB drive be put on the FreeDOS website -- specifically the home page. This would be a huge help to people like me. I ended up having to Google for instructions, and found a download for a FreeDOS 1.0 usb drive. Interesting, got a link by any chance? ( http://bsd.ee/~hadara/blog/wp-content/uploads/2010/02/dell_freedos-768x1024.jpg, also interesting) Also confusing for me is that the description for the fd11src.iso on the Download page says specifically, Install only, does not include LiveCD but there is no mention of where a LiveCD download might be. You might want to put a link on the Download page to the LiveCD. The older FreeDOS 1.0 included a Live section which I didn't keep for FreeDOS 1.1. I'll add it back sometime, and then the rest as the big FreeDOS 1.0 CD had, which was around 250MB. I succeeded in flashing my LSI card with the help of FreeDOS. It turns out that LSI does support the SAS2FLASH utility on several operating systems, including FreeDOS 1.0. Also supported on several systems is the MegaCLI utility. I am not sure if the Megarec utility is likewise supported. It is possible I could have used SAS2FLASH on FreeBSD, but I also needed Megarec, and I could only find a DOS version of that. So I opted for using FreeDOS. No idea what all these LSI tools are. Specifically for flashing, there's also the flashrom tool (www.flashrom.org) that works on Linux and has a DOS port at http://ra.openbios.org/~idwer/flashrom/dos/ (thanks for making me look that up, it's been updated!). I do hope that someone visiting the FreeDOS website will soon be able to find quick instructions for creating bootable USB drives in addition to the normal install directions. Jim Hall is working on a website change, hopefully he'll include your feedback. Bernd -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS and timing...
Op 29-3-2012 1:20, Zbigniew schreef: Ability to detect heavy CPU load can be important information for me, that e.g. I did something wrong (for example, some loop has to be done differently). In-app profiling, or using a debugger maybe, could help. Otherwise, run DOS and your program inside an emulator (QEMU/Bochs/DosEMU) and get detailed output (timestamped logfiles) from that. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FlWriter - a graphical text processing program
Op 23-3-2012 18:32, nospam schreef: Hi Bernd, thank you for testing FlWriter! I do not have VMWare installed but FlWriter will run (slowly) in Bochs. Maybe you try to change the display to 16 bit color like this: set nanoscr=800 600 565 That didn't work out (entirely black screen in the virtual machine), guess I'll have to try other virtual machines. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FlWriter - a graphical text processing program
Op 18-3-2012 15:40, nospam schreef: I ported a WYSIWYG text processing program called FlWriter to DOS based on my port of the FLTK GUI toolkit. I also added and extended many functions. Georg Georg, thanks for your work on this port/enhancement. Any idea how to run this under VMware Workstation? All I get is a black screen, same for DILLO a while back. Which emulators are working for you? best regards, Bernd Blaauw -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JEMMEX not necessary?
Op 16-3-2012 0:22, Marcos Favero Florence de Barros schreef: I have been using JEMMEX NOEMS, but now I see it is not really necessary. What would you recommend instead? If not needing UMBs that much to optimise conventional memory, an XMS manager like XMGR might be sufficient. In addition, UMBPCI can perhaps be used but it doesn't support the most recent chipsets unfortunately. For a general situation JEMMEX NOEMS might remain the best solution. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers
Op 16-3-2012 0:55, Rugxulo schreef: stuff, esp. not DJGPP/DPMI things, so I would only do JEMM386 LOAD and UNLOAD at runtime if needed (rarely). The ability to dynamically load and unload JEMM386 is a nice benefit indeed. Indeed an XMS/HMA-only environment already provides a pretty decent start. together, and you can't just load at runtime (if XMS already enabled) because it only uses its own XMS manager built-in. So while it saves a few kb of space by combining them, it's slightly less useful if you don't want EMS or UMBs (and/or have a very rare app that refuses to run under V86 mode). Also I very vaguely remember some apps in the old days not working correctly with NOEMS. JEMMEX optionally acting as a 2-stage driver would be nice. Either load it as all-in-one, or starting as an XMS-driver and only allow itself as EMM386 driver, refusing all other UMB/EMS drivers. Then you get: [1]: DEVICE=JEMMEX.EXE NOEMS DOS=HIGH,UMB [2]: DEVICE=JEMMEX.EXE XMS DOS=HIGH [3]: DEVICE=JEMMEX.EXE XMS DEVICE=JEMMEX.EXE NOEMS DOS=HIGH,UMB [4]: DEVICE=JEMMEX.EXE XMS DOS=HIGH @echo off echo Loading EMS driver: jemmex.exe Some XMS managers are also dynamicly loadable, but that has more limited use as it won't enable HMA. Also, (primary) shells typically can't relocate themselves to XMS. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers
Op 16-3-2012 0:50, Jack schreef: To test this, I change the first few lines of my CONFIG.SYS file which are -- DEVICE=C:\BIN\UMBPCI.SYS DEVICE=C:\BIN\XMGR.SYS /W DOS=HIGH,UMB REM DEVICE=C:\BIN\JEMM386.EXE I=B000-B7FF X=C800-EFFF NOEMS Normally, I remark out (REM) JEMM386 and use it only for UIDE/ UIDE2 testing. After editing, my CONFIG.SYS file began with -- DEVICE=C:\BIN\XMGR.SYS /B DOS=HIGH,UMB DEVICE=C:\BIN\JEMM386.EXE I=B000-B7FF I=CC00-DFFF DEVICEHIGH=C:\BIN\XMGR.SYS http://www.vfrazee.com/ms-dos/6.22/help/commands%20for%20defining%20multiple%20configurations.htm ^^ (then again, a bootmenu typically causes delays due to giving the user a chance to make their choice). -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Strange timer-related issue
Op 11-3-2012 17:21, Zbigniew schreef: but as I suggested in a off-list reply to a question that Eric Auer send me, the fact that sound output is effected as well, this seems kind of confirm my suspicion on how JEMM is handling IN/OUT statements when in protected mode, or something along those lines... Then indeed there's something in a need for a little improvement? Please let us know if/when you're able to pinpoint a culprit. You might want to start with a MSDOS/Win9x bootdisk (www.bootdisk.com) to eliminate FreeDOS components as the culprit, and to have a proven reference platform. Once that works, try 4DOS but keep MSDOS's memory manager. Independently, also try JEMMEX (and/or XMGR and/or HIMEMX with/without JEMM386). Your game seems to be the most obvious situation to demonstrate something's not quite right. So things that can vary: [1] KERNEL (MSDOS versions, or various FreeDOS kernels) [2] SHELL (MS-COMMAND, FREECOM, 4DOS) [3] HMA/XMS driver (MS-HIMEM, HIMEMX, XMGR) [4] UMB/EMS driver (MS-EMM386, JEMM386) [5] Combo XMS/UMB driver (JEMMEX) A not so nice challenge is trying Quarterdeck's QEMM, that's one big nightmare :) -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem after updating to FreeDOS 1.1 with writing of environment variables.
Op 8-3-2012 18:43, Mark Gillespie schreef: Thanks, after using all the excellent advice so far, I am **ALMOST** back up and running, the environment variable problem has been worked around, and I have taken onboard the memory saving advice (have about 470k of conventional memory, which should be ample, how much did billyboy say we wouln't need anything more than?). Your config below mentions a bare JEMMEX , for improved amounts of memory you could add one or more of the following settings: * NOEMS (disables EMS almost 100%, and its pageframe entirely) * I=B000-B7FF (use Monochrome area, might work, or not) * I=TEST (test for additional UMBs) * X=TEST (test for additional UMBs) Problem is, now the ghost process is crashing with a read error from the DVD, which I know don't contain any errors. Could this be related to me using UIDE.SYS rather than our previous driver (oakcdrom.sys)? Is there anything I should be aware of? Or any way to help diagnose the error? It's a possibility. Could you try to invoke UIDE in a very basic way? DEVLOAD UIDE.SYS /D:CDROM1 /N1 /N3 /B That way you have a CD-ROM driver without using HMA ( /H switch), without handling harddisk ( /N1 ), without using extended memory ( /N3 ), without using UMBs ( /H option in DEVLOAD , bit unstable with DMA/VDS and some EMM386 flavors). -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ram disk as related to memory managers...
Op 8-3-2012 17:34, Mark Brown schreef: i use the invoked option #1 in freedos 1.1 full install boot menu and it works for me. ( #1 of the four available choices ) There are various ramdisk drivers as freeware, shareware and others (XMSDISK.EXE comes to mind). Also FreeDOS itself carries multiple ramdisk drivers, as none is perfect for all situations. Even with all the memory available to modern systems, it's still a tradeoff on how to allocate it between staying available, ramdisks, caches and drivers. Tempting to assign most to a ramdisk, a bit to a cache and then find out you're out of memory to actually run any program. RAMDISKS: * TDSK is unique in that it can use conventional memory * SRDISK is unique in that it can resize while keeping contents * RDISK is unique in its simple usage, exactly as intended. * SHSURDRV is unique in 4GB support, errorlevels, unloadable, and some other features. CACHES (partial) : * UIDE (IDE/SATA CDROM and harddrives) * CDRCACHE (CDROM) * LBACACHE (harddisks) DRIVERS (full caches/ramdisks): * SHSUCDRD (loads ISO file as read-only CD copy in system memory) * SHSUCDRI (duplicates a CD drive's contents in system memory) DRIVERS (using some XMS) : * XMS memory drivers * shell (XMS-swapping) * a few other drivers using a bit of XMS SYSTEM : * MEMDISK module in Syslinux can load a disk image in system memory and boot from it. DOS has no support for over-4GB memory usage, not through 32bit AWE or PAE, nor 64bit stuff. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
