Re: [Freedos-user] USB hard drive support (non-booting) under FreeDOS?
Eric Auer wrote: Hi again :-) Hi! An USB flash drive was made bootable for FreeDOS with the tool 'HP Drive Key'. Booting from that device works well if the BIOS supports USB booting. After loading the USB driver under FreeDOS device C:\ could be no longer read. FreeDOS asked for a command.com location. So you should not load the driver Indeed. Doing so causes problems. If you want use other USB devices you have a problem. (1) - C: was accessible thanks to the BIOS driver anyway :-p. Yes. Or was C: something else than the USB drive? No. If so, why did it become inaccessible when you loaded the DOS USB driver?? I don`t think it would happen with a normal harddisk. Did you try without EMM386? No. If your C: was something USB, SCSI, SATA or UDMA-IDE, then it is quite possible that some UMB conflicts spoil your C:. Yep. And this was my experience what I just described here. I don`t think FreeDOS provides a feature to change the drive letter? Why would you want to do that? In case of (1). 1. booted from an USB drive (without drivers, BIOS int) 2. load USB driver 3. C:\ will become D:\ (or w/e) 4. loosing connection to C:\ 5. removing letter C:\ (because no longer accessible) 6. moving D:\ to C:\ You can try SUBST JOIN and ASSIGN but those are not always very intuitive to use... I see. :) Greetings Michael Reichenabch - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] create PDF from TXT files with HX EXTENDER
Hi at all, i suggest to try txt2pdf.exe using hx extender. Txt2pdf it's a 32 bit executable (also via commans line) for create .pdf from text files. Graphic effect s can be added via special command insert on simole.TXT file. The pestub work, but during the execution the program stop 2 time and require the close of server, then create the pdf files. ie. txt2pdf test.txt create a test.pdf file Someone Know hoe to eliminate this problem during running of txt2pdf under hx extender? Download txt2pdf from : http://www.sanface.com/txt2pdf.html -- View this message in context: http://www.nabble.com/create-PDF-from-TXT-files-with-HX-EXTENDER-tp17272814p17272814.html Sent from the FreeDOS - User mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] create PDF from TXT files with HX EXTENDER
iw2evk wrote: Txt2pdf it's a 32 bit executable (also via commans line) for create .pdf from text files. And it's shareware. :-/ Alternatively you could try my DOS build (http://www.bttr-software.de/misc/halibut-r7622-dos.zip) of Halibut (http://www.chiark.greenend.org.uk/~sgtatham/halibut/). Robert Riebisch -- BTTR Software http://www.bttr-software.de/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to start network auto detection again?
Michael Reichenbach wrote: How can I start this wizzard again? Try to run Crynwr.bat in FDOS directory. Robert Riebisch -- BTTR Software http://www.bttr-software.de/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] display problems with Lotus
I have FreeDos running under VirtualBox and it seems to run OK except that when I copied in a previously running Lotus system and try to run 123R23.exe the program doesn't display the numbers I type nor the function menus after I type /. Some sort of display issue obviously but I don't remember enough about DOS display stuff to know how to correct the situation. I'm running a Dell LCD display connected to a Dell Pentium PC running Windows XP Pro. I ran the Lotus Install program and chose the VGA display. Can anyone suggest what I need to do to get 123R23 to execute and display properly under FreeDOS/VirtualBox? Larry - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] display problems with Lotus
On Fri, May 16, 2008 at 8:53 AM, Larry Nolan [EMAIL PROTECTED] wrote: I have FreeDos running under VirtualBox and it seems to run OK except that when I copied in a previously running Lotus system and try to run 123R23.exe the program doesn't display the numbers I type nor the function menus after I type /. Some sort of display issue obviously but I don't remember enough about DOS display stuff to know how to correct the situation. I'm running a Dell LCD display connected to a Dell Pentium PC running Windows XP Pro. I ran the Lotus Install program and chose the VGA display. Can anyone suggest what I need to do to get 123R23 to execute and display properly under FreeDOS/VirtualBox? Larry I have absolutely NO experience with VirtualBox but to me this sounds more like a VB problem. I'm presuming that there's some sort of switching that should be happening with the graphic adapter to make character sets available and it sounds to me like that isn't happening. You might be able to switch character sets yourself using ANSI.SYS: http://en.wikipedia.org/wiki/ANSI.SYS I've not tried that one myself. I have seen some problems with character sets in Linux consoles that sound similar to what you're seeing. In those cases there was some escape sequence I was able to use that set the character set back to default. Hope this helps, Mark - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New Freedos and Linux user. Trouble with PPPoE. Please help !
At home it is OK, no trouble with Mandriva or Ubuntu. At the office we have, among others, a PC with a hard disk with 2 GB of memory and its RAM is of 128 GB. I Decided to run ROSLIMS from the live CD, but Freedos would also be useful. Under Ubuntu I could use only DOSBOX, under Mandriva there is trouble, I cannot install a valid Dosemu. Does Dosemu have drivers for Realtek ethernet cards on the live CD ? Alex J Unless you have a specific need to boot your PC with FreeDOS, I would recommend running FreeDOS inside Linux DOSEmu. This is mostly how I use FreeDOS these days. It works great. -jh - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Trouble with PPPoE and ethernet card
excuse me, 128 mb of RAM - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to start network auto detection again?
I also tried to install it at the ofice and there was the same problem. I could not configure anything Alex Michael Reichenbach [EMAIL PROTECTED] wrote: I mean the following sreenshot or 1 step before http://img135.imageshack.us/img135/9076/20080516143930xh4.jpg The FreeDOS setup start at the very end, after copying all files to harddisk something to auto configure the network card. How can I start this wizzard again? Installing FreeDOS again is not possible in my case. It would help me a lot if I could start it again from an already installed FreeDOS. Greetings Michael Reichenbach - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to start network auto detection again?
It's just my preference but why do *any* of this with the installation program? Maybe you'd be better off installing FreeDOS by hand, from scratch, making sure that works, and then installing just the components you really need. I'm new to FreeDOS. My first install was using gparted to create a FAT32 partition and then using the basic system installer and copying over an autoexec.bat and config.sys. It was quick, easy and best of all I felt like I had a basic picture of what was going on. I then tried the FreeDOS installer that you are speaking of. It took 20-30 minutes and at the end I didn't have a clue why I was installing any of this stuff. Sometimes, for some of us, the most basic simple way is actually pretty good. Just an idea, Mark On Fri, May 16, 2008 at 2:40 PM, Alexandru Fira [EMAIL PROTECTED] wrote: I also tried to install it at the ofice and there was the same problem. I could not configure anything Alex Michael Reichenbach [EMAIL PROTECTED] wrote: I mean the following sreenshot or 1 step before http://img135.imageshack.us/img135/9076/20080516143930xh4.jpg The FreeDOS setup start at the very end, after copying all files to harddisk something to auto configure the network card. How can I start this wizzard again? Installing FreeDOS again is not possible in my case. It would help me a lot if I could start it again from an already installed FreeDOS. Greetings Michael Reichenbach - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New Freedos and Linux user. Trouble with PPPoE. Please help !
Unless you have a specific need to boot your PC with FreeDOS, I would recommend running FreeDOS inside Linux DOSEmu. This is mostly how I use FreeDOS these days. It works great. Por favor... don't write such words here - because the chief should not make it official, that there should be used another operating system for FreeDOS ;-P Better: Booting FreeDOS shows how fast and powerfull it is, but for beginners it could be easier to test it first under Linux... ;-P Hasta luego Flo -- Passts auf, seits vuasichtig losst eich nix gfoin! (Kurt Ostbahn) http://www.drdos.org - http://www.flox.at.tf - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New Freedos and Linux user. Trouble with PPPoE. Please help !
Florian Xaver schrieb: Unless you have a specific need to boot your PC with FreeDOS, I would recommend running FreeDOS inside Linux DOSEmu. This is mostly how I use FreeDOS these days. It works great. Por favor... don't write such words here - because the chief should not make it official, that there should be used another operating system for FreeDOS ;-P Better: Booting FreeDOS shows how fast and powerfull it is, but for beginners it could be easier to test it first under Linux... ;-P Hasta luego Flo It`s quite problematic to run FreeDOS on modern hardware. (lack hardware and driver support) In the long run emulation will be the way to keep DOS alive. Greetings Michael Reichenbach - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] USB hard drive support (non-booting) under FreeDOS?
Hi Michael, - C: was accessible thanks to the BIOS driver anyway :-p. Yes. If so, why did it become inaccessible when you loaded the DOS USB driver?? I don`t think it would happen with a normal harddisk. Well you loaded a driver which created a new int13 gateway to the SAME drive, which is a very bad idea in the first place... You should probably be glad you lost access to USB BIOS disk is C: at the moment when you loaded the driver which says DOS USB disk is D: because otherwise C: and D: would share the same physical drive and partition. Did you try without EMM386? No. Would be a good idea :-) 4. loosing connection to C:\ 5. removing letter C:\ (because no longer accessible) 6. moving D:\ to C:\ You can do something like ASSIGN C=D which makes all files on D: visible as C: and all things on your original C: invisible... Using ASSIGN does not have the bad side effects I mentioned above: Only if you have 2 *lowlevel* ways to access the same physical partition you get troubles ;-). After using ASSIGN, your inaccessible C: is no longer visible and your new way to access the drive as D: is also visible as C:, so you now have two drive letters for the same drive... Still you can have a problem: If you have written to C: before you loaded the DOS driver, then the writes may be aborted early at the moment when BIOS access is lost. Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New Freedos and Linux user. Trouble with PPPoE. Please help !
Hi Michael, It`s quite problematic to run FreeDOS on modern hardware. (lack hardware and driver support) I disagree... For example somebody recently asked me how he could remove a preinstalled FreeDOS from his PC, as he wanted to install Windows. It turned out that his SATA harddisk was supported by BIOS (and DOS) but not by the default install of Windows, so he had to use some driver disk to be able to install Windows on that computer. Keyboard, mouse and harddisk are almost always DOS compatible. If you can boot from it, it is DOS compatible. And USB mouse and keyboard are often supported via some legacy BIOS option which makes them look like PS2 mouse and keyboard for DOS. Next aspects are graphics and network: Graphics almost always supports VGA or even VESA VBE BIOS functions, and often has hardware VGA compatibility, so DOS text mode and DOS games should work just fine. Sometimes new functions take too much space and old functions are dropped: A typical aspect is the 8x14 EGA font. Luckily you can load a TSR which contains such a font, so EGA games will work even if your BIOS has no 8x14. Network can be more tricky. Either you get a network card with a classic chip, like Realtek rtl8139, and use a DOS packet driver from crynwr or similar sources for that. Or you check if there is an ODI or NDIS driver for your network card and then you use a wrapper from ODI/NDIS to packet. You should find HOWTOs about this online. Even my current nForce board uses a GBit LAN chip for which official nVidia ODI/NDIS DOS drivers exist. I believe this is because GHOST with network drives is still a popular DOS app and this somehow likes the network drive related ODI/NDIS drivers? The CPU and RAM of a modern PC are still trivially supported by DOS. Of course my dual core AMD Athlon64EE (energy efficient, now also available as BE which uses even less energy) is quite under-used in DOS: there are no 64bit calculations in DOS, you cannot use more than 4 GB RAM in DOS, and you can only use one of the cores. But still DOS is happy to run on this hardware. In the long run emulation will be the way to keep DOS alive. I only agree for one aspect: an emulated soundblaster so old DOS games can play sound while you really have AC97 or HDA :-). There were some discussions about this on the BTTR forum recently: you could use AC97 drivers from MPXPLAY (a DOS media player) or from Linux Alsa-Project and the emulated soundblaster of DOSEMU (or Bochs, Qemu, similar...) to create a DOS driver which uses virtualization functions from, for example JEMM386 to trap all access from games to soundblaster, simulate a soundblaster, get all the audio data, and play it using the real AC97 hardware. A similar project already exists from somebody in Russia: Virtual Sound Blaster is here: zap.eltrast.ru/en/dldos.html VSB sources are here, Assembly: cs.ozerki.net/zap/pub/vsb/ (found by Spiro, thanks :-)) www.bttr-software.de/forum/board_entry.php?id=3174page=0order=timecategory=all (this also discusses whether there can be a bounty - we can collect some funds to motivate volunteers to write a JLM sound driver module) Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FreeDOS on modern hardware
Ok, I didn`t really wanted to hijack this topic so I use another topic for this interesting discussion. What are the reason why someone would use DOS? - just some of my first thoughts, perhaps what I planed to do - classic DOS games - legacy applications - nostalgia - interesting for programmers - easy hardware access - very lightweight, starts very fast - special purpose (backup, scan virus...) Eric Auer wrote: It`s quite problematic to run FreeDOS on modern hardware. (lack hardware and driver support) I disagree... For example somebody recently asked me how he could remove a preinstalled FreeDOS from his PC, as he wanted to install Windows. It turned out that his SATA harddisk was supported by BIOS (and DOS) but not by the default install of Windows, so he had to use some driver disk to be able to install Windows on that computer. Never encountered this problem. But seams in this case you are forces to mess with vista, xp might be a bit to outdated to get this working out of the box. Keyboard, mouse and harddisk are almost always DOS compatible. If you can boot from it, it is DOS compatible. And USB mouse and keyboard are often supported via some legacy BIOS option which makes them look like PS2 mouse and keyboard for DOS. Some BIOS are stupid like mine. It has really no legacy emulation, neither keyboard/mouse nor soundblaster. Blame legacy BIOS, I hope for a good replacement (EFI) will full legacy support. The lucky thing is: I still had adapters. If this is not the case, then FreeDOS isn`t a good choice. That`s why I meant with problematic. Next aspects are graphics and network: Graphics almost always supports VGA or even VESA VBE BIOS functions, and often has hardware VGA compatibility, so DOS text mode and DOS games should work just fine. Sometimes new functions take too much space and old functions are dropped: A typical aspect is the 8x14 EGA font. Luckily you can load a TSR which contains such a font, so EGA games will work even if your BIOS has no 8x14. My graphic card (Nvida Geforce FX) has VGA and VESA. There are not DOS drivers from Nvida. Neither univbe nor freevbe are working. If I do some stress test like scitech display doctor it will crash. Also the benchmark is very slow (only 5-15 frames per second). The web browser arachne runs with 1024*768 with 2 MB VESA very slow. When I start some classic game like [1] the graphic is pretty messed up. [1] http://www.abandonia.com/en/games/574/International+Karate.html Other games also look messed up. Some games are working (perhaps the better programmed ones) well. Also other strange behavior. The system hangs or applications crash randomly. I am not sure if this is only related to the graphic board or what... But if I look on google I find that most people recommend dosbox or dosemu for legacy applications. Very much don`t recommend to mess with DOS on new hardware. DOS compatible hardware is recommend. Not much success storys about running on hardware like P3. I try it anyway. :) Network can be more tricky. Either you get a network card with a classic chip, like Realtek rtl8139, and use a DOS packet driver from crynwr or similar sources for that. Or you check if there is an ODI or NDIS driver for your network card and then you use a wrapper from ODI/NDIS to packet. You should find HOWTOs about this online. Even my current nForce board uses a GBit LAN chip for which official nVidia ODI/NDIS DOS drivers exist. I believe this is because GHOST with network drives is still a popular DOS app and this somehow likes the network drive related ODI/NDIS drivers? Can`t comment on this yet. The CPU and RAM of a modern PC are still trivially supported by DOS. Of course my dual core AMD Athlon64EE (energy efficient, now also available as BE which uses even less energy) is quite under-used in DOS: there are no 64bit calculations in DOS, you cannot use more than 4 GB RAM in DOS, and you can only use one of the cores. But still DOS is happy to run on this hardware. In the long run emulation will be the way to keep DOS alive. I only agree for one aspect: an emulated soundblaster so old DOS games can play sound while you really have AC97 or HDA :-). Yes, sound is one of the biggest issues currently. My AC97 is not even detected in quickview. What a shame, it was a nice imagination not to boot a full windows just to watch some media. There were some discussions about this on the BTTR forum recently: you could use AC97 drivers from MPXPLAY (a DOS media player) or from Linux Alsa-Project and the emulated soundblaster of DOSEMU (or Bochs, Qemu, similar...) to create a DOS driver which uses virtualization functions from, for example JEMM386 to trap all access from games to soundblaster, simulate a soundblaster, get all the audio data, and play it using the real AC97 hardware. www.bttr-software.de/forum/board_entry.php?id=3174page=0order=timecategory=all (this also discusses
Re: [Freedos-user] New Freedos and Linux user. Trouble with PPPoE. Please help !
Michael Reichenbach escreveu: It`s quite problematic to run FreeDOS on modern hardware. Amazingly it is not. Runs very well in on any machine, I use it professionaly! Alain - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
