Re: [Freedos-user] retro gamer review of FreeDOS 1.3
Hi Eric, all DSI games that use that same engine, Grand Prix Circuit, The Cycles, Test Drive 2 have that issue. You launch the games and you just get a black screen. I commented on the video comment section days before it premiered that he should test Grand Prix Circuit and Test Drive 2 as i was sure those would fail. Somehow my comment is not there anymore, but i'm glad that he did test them. There's also the floppy versions of Alone in the Dark 1 and Alone in the Dark 2: https://github.com/dosemu2/fdpp/issues/107 It's something about corrupted PSP's that somehow do not crash on MS-DOS but crash on FreeDOS. So these Alone in the Dark games might need to be patched to work on FreeDOS. A sexta, 4/03/2022, 20:56, Eric Auer escreveu: > > Let me summarize this ;-) > > >> https://www.youtube.com/watch?v=SNeq-F84Lx4 > > - Lots of games had CD driver issues in FreeDOS 1.2 and are fine now > > - Grand Prix Circuit and Test Drive 2 still do not run > > - most games work best in boot option TWO, which is a sane JEMMEX > config. I guess the default is option ONE, insane JEMMEX tuning? ;-) > > - Wing Commander needs JEMM386 instead, I have no idea why? > > - some games do not like any EMM386, of course > > - the video mentions zero games not liking HIMEM, I think? > > - it sounds like a very bad idea to create a zillion FAT16 partitions > and format only one of them, while using FreeDOS FDISK etc. by hand > made it easy for the reviewer to just create ONE FAT32 drive :-p > > - one of the installers took 20 minutes, but the legacy one was fast? > > - lots of youtube viewers ask whether Windows WfW 3.11 is supported > and I bet they mean 386enh mode (in WfW 3.11, non-386enh is just > left as a sort of safe mode, while in Windows 3.x, standard mode > was still relatively useful for those not supporting 386enh mode) > > Maybe somebody can tell me what is going on with GP Circuit and with > TD2 in FreeDOS? Do we know which compatibility problems they trigger? > > Have any recent kernel updates made WfW 3.11 work in a less convoluted > way in FreeDOS and if yes, which specific tricks are needed to run it? > > I remember you had to disable windows disk drivers to let it use DOS > and/or BIOS instead if your disk is non-tiny? And you had to limit > the size of visible RAM if you had too much of it? HIMEM etc. have > special options for that and you can also tune various things in Win3 > configuration files, such as the swap address space ratio etc. There > also was a FreeDOS tech note long ago, I believe. > > Regards, Eric > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] retro gamer review of FreeDOS 1.3
> On Mar 5, 2022, at 8:49 AM, Eric Auer wrote: > > > Hi! > >>> - it sounds like a very bad idea to create a zillion FAT16 partitions >>> and format only one of them, while using FreeDOS FDISK etc. by hand >>> made it easy for the reviewer to just create ONE FAT32 drive :-p > >> When the installer verifies there is no drive readable to DOS ... it >> asks FDISK to please auto-partition the drive. There are no auto-partition >> options to make only one that uses the entire drive. > > FDISK is open source, so the auto-partition feature could and should > be updated from "100 FAT16 drives" to "1 FAT32 drive" if possible, but Or, at least be ably to specify that from the command line. > >> So, it comes down to making everyone (including novices with no idea how >> to use fdisk) partition the drive manually or let fdisk do what it wants. > > It was a completely normal part of DOS life that when you were planning > to install MS DOS you would have to take the time to understand and use > FDISK, so I would certainly prefer manual partitioning over autocreated > FAT16 C: to ZZZ9: drives of which only C: gets formatted anyway ;-) Yes, I was normal. But, it really isn’t the norm any more. But, there is nothing preventing a knowing user from pre-partitioning their drive prior to installing. In fact, if you plan on dual booting or using a custom partition scheme, you should do that. It isn’t hard to do and the installer will see it is done and be happy to move along without auto-partitioning or throwing the user into FDISK. At least FDISK puts all those other partitions inside an extended partition. You can get rid of them, by simply deleting the extended partition. Thankfully, you don’t have to delete them one at a time. > >> Without such an update to fdisk, I still think the benefits provided by >> auto-partitioning out weigh making everyone manually partition their drive. > > That is the part where I disagree and that youtube reviewer is not the > first person to make fun of that FDISK "feature". We already have the > same discussion on the list :-) As said, remembering that FDISK had a > non-free toolchain and no active maintainers, I would prefer to just > let people use FDISK by hand if no C: is found. There is nothing preventing you from manually partitioning. What I would like to see is the ability for for FDISK to auto-partition 1 drive, with the option of making it FAT16 (2GB) or FAT32 (Whole Drive). With that ability, I think the installer could by default just make a single big FAT32 partition. And for advanced mode, it could offer the choice of whole disk FAT32 or single 2GB FAT16 to provide compatibility with older DOS platforms. > Regards, Eric > > PS: Odd that the youtuber has even tried the floppy installer at all, > as he spends half of his video talking about CD-ROM game support :-o > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FreeDOS in qemu: no internet-connection
Hi altogether, I want to get *FreeDOS* going within *qemu*. Quite a long time ago I downloaded the respective iso-file and the installation went well. In principle *FreeDOS* works fine with the exception of networking. I simply can´t get qemu to let *FreeDOS* connect to the internet. (Formerly I could; see below). My command-line is: qemu-system-i386 -m 32M -drive file=drivec.img,media=disk,format=raw -net nic,model=ne2k_pci -drive file=FD12CD.iso,media=cdrom -boot order=d According to the instructions on http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_Quick_Networking_HowTo I installed FDNET, mTCP and wget in FreeDOS. So things should work. Yet they don´t (any more). When starting FreeDOS everything looks right at first: QEMU network detected DHCP request sent, attempt 1: Offer received, Acknowledged Good news everyone! IPADDR = 10.0.2.15 NETMASK = 255.255.255.0 GATEWAY = 10.0.2.2 NAMESERVER = 10.0.2.3 LEASE_TIME = 86400 seconds That used to work in the past. But things seem to have changed as of late: When trying to use ping or the links browser internet connection doesn´t seem to be established: configuring through DHCP...failed configuring through RARP...failed error loading ... URL Host not found I dont know whether it has something to do with the fact that my means of connecting to the internet has changed in the meantime. I used to use a 3G-umts-stick (Huawei E 1550) , which was recognized as a modem and used "*ppp0*". My new 4G-stick is Huawei E 3372 and this one seems to work as a *router*; so my internet connection is recognized as *LAN* (wired) connection. I´m guessing I have to change some settings in C:\FDOS\WATTCP.CFG, but I´m not quite sure. Can anybody help me , please? Many thanks in advance. Many greetings. Rosika P.S.: my system (host): Linux/Lubuntu 20.04.4 LTS, 64bit FreeDOS 1.2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] retro gamer review of FreeDOS 1.3
Hi! - it sounds like a very bad idea to create a zillion FAT16 partitions and format only one of them, while using FreeDOS FDISK etc. by hand made it easy for the reviewer to just create ONE FAT32 drive :-p When the installer verifies there is no drive readable to DOS ... it asks FDISK to please auto-partition the drive. There are no auto-partition options to make only one that uses the entire drive. FDISK is open source, so the auto-partition feature could and should be updated from "100 FAT16 drives" to "1 FAT32 drive" if possible, but So, it comes down to making everyone (including novices with no idea how to use fdisk) partition the drive manually or let fdisk do what it wants. It was a completely normal part of DOS life that when you were planning to install MS DOS you would have to take the time to understand and use FDISK, so I would certainly prefer manual partitioning over autocreated FAT16 C: to ZZZ9: drives of which only C: gets formatted anyway ;-) Without such an update to fdisk, I still think the benefits provided by auto-partitioning out weigh making everyone manually partition their drive. That is the part where I disagree and that youtube reviewer is not the first person to make fun of that FDISK "feature". We already have the same discussion on the list :-) As said, remembering that FDISK had a non-free toolchain and no active maintainers, I would prefer to just let people use FDISK by hand if no C: is found. Regards, Eric PS: Odd that the youtuber has even tried the floppy installer at all, as he spends half of his video talking about CD-ROM game support :-o ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share
On Fri, 4 Mar 2022 at 19:26, Sean Warner wrote: > > Gmail on my Android phone forces me to be type an answer above a previous > reply. Don't know how change the email to plain text.. Ah, yes. It doesn't work on the mobile client, so I try to avoid ever answering anyone from the mobile client. K9Mail does work for this. > Anyway, thank you so much for all your helpful information! We are currently > running this "dos" program in win 7 32 bit and were using it in Win XP before > that. Yes I'm quite sure it's a dos program.. the only colours are black, > blue, white and yellow. It has no windows and it's all command line in > appearance, no mouse works just all arrow keys to navigate around. That isn't evidence. Win32 Console Apps are a real thing: https://en.wikipedia.org/wiki/Windows_Console Here's how to build one: https://stackoverflow.com/questions/61030578/win32-console-application The best way to check if it's a console app is to try to run it under DOS. Forget the dongle etc., just see if it launches. Because, as others have said, if it needs a USB device then it very probably is *not* a DOS app, because DOS doesn't really support USB. (There are a handful of specialised drivers and things but it's extremely limited.) > I think I read that MS are ending support for XP mode but maybe that's worth > a try if it'll make things easier with networking and usb support which we > need. I'll see if I can keep this ancient program running for another year or > two! I suspect it's already out of support. XP itself is, VirtualPC is, and Win7 is on special paid-for emergency patches only. But then again, FreeDOS is out of support, because it was never *in* support. :-D -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Will freedos running in a Virtual box VM recognise a host attached USB security dongle?
On Fri, 4 Mar 2022 at 20:09, Louis Santillan wrote: > > I wrote a quick guide on how to pass through USB devices to a VirtualBox VM. > > https://sites.google.com/view/lpsantil/home/adding-usb-device-to-a-virtualbox-vm [...] > 5. Pick an appropriate USB spec controller. Very old devices will likely use > "USB 1.1 (OHCI) Controller" (super old web cams, scanners, keyboards, mice, > etc.). Devices and OSes made in the last 15 years will likely be better > suited for "USB 2.0 (OHCI + EHCI) Controller". You are missing a *very* important point in your guide. VirtualBox is FOSS and can be run without restrictions anywhere. The VirtualBox Extension Pack is *not* FOSS and must be licensed. If used in a commercial or business setting, you have to pay for it. It's not that cheap and for multiple users it can be significant. USB 2 and higher need the extension pack. Only USB 1 can be used for free. -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
