I also have HP t5745 thin clients (Intel Atom 1.66GHz 1C/2T, 1GB-4GB RAM, 2GB DOM) and I very much prefer it's BIOS. You can stick any format USB drive in it and DOS (FreeDOS or MS DOS 6.22 or 7) will mount it. And it has a total of 6 USB ports! I also bought the expansion module for it that adds a PCI or PCIe slot w/a fan, a parallel port and a 2nd serial port. The CPU is obviously much faster than the 365MHz Cyrix/National Semiconductor Geode LX that is in Wyse SX0 S10. However, the integrated Intel GL40/GMA X4500MHD in the HP reports itself as VBE 3.0 compatible and the Wyse has a Geode GX2 VGA VBE 2.0 compatible card. The Wyse seems to be more DOS and Windows 98 friendly though both should also be ok in Windows XP. Both also do very well with lightweight Linux distros like TinyCoreLinux or old Lubuntu 16.04/18.04. Networking wise, the HP has a BCM57780 which requires a hard to track down B57 packet driver from Dell! The Wyse has a Realtek 8139 that works with the same packet drivers that work in VirtualBox or QEMU.
On Fri, Dec 24, 2021 at 3:35 PM Daniel <codehunte...@gmail.com> wrote: > I have a Wyse VX0 V10LE and I admit I haven’t tested FreeDOS on it. If I > am able to get anothe DOM (Disk On Module), I would love to see if it works > on the system. > > The cpu is 1.2ghz, RAM is 1gb, and the DOM is 16gb. > > Originally came with a Windows 98/XP dual boot. Currently running Windows > 98 (mainly in DOS), and a vm running OS/2. > > Although I am unable to natively install OS/2, Windows 98 and DOS runs > perfectly and putting a usb stick is available to DOS without needing any > drivers in DOS which is a plus. One downside is CD off USB is a big issue > when trying to install an OS. > > On Fri, Dec 24, 2021 at 18:02 <freedos-user-requ...@lists.sourceforge.net> > wrote: > >> Send Freedos-user mailing list submissions to >> freedos-user@lists.sourceforge.net >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> or, via email, send a message with subject or body 'help' to >> freedos-user-requ...@lists.sourceforge.net >> >> You can reach the person managing the list at >> freedos-user-ow...@lists.sourceforge.net >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Freedos-user digest..." >> >> >> Today's Topics: >> >> 1. Re: Video complains that DOS should not be maintained (Wengier W) >> 2. Re: Now it gets odd Re: FreeDOS workaround for hidden IDE >> controller? (Louis Santillan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 24 Dec 2021 22:46:34 +0000 (UTC) >> From: Wengier W <wengie...@yahoo.com> >> To: "Discussion and general questions about FreeDOS." >> <freedos-user@lists.sourceforge.net> >> Subject: Re: [Freedos-user] Video complains that DOS should not be >> maintained >> Message-ID: <1457277452.1987137.1640385994...@mail.yahoo.com> >> Content-Type: text/plain; charset="utf-8" >> >> I certainly hope to see more people using DOS/FreeDOS as the only (or >> primary) operating system. However, without things like full support for >> Internet and modern hardware (modern sound card, USB devices, etc) this >> cannot occur, unfortunately. IMO, DOS/FreeDOS need to support things just >> like a typical "modern" OS (e.g. Linux) does, so that the general public >> won't consider DOS a "legacy" OS, or a system that is limited to very >> specific uses. >> Wengier >> On Friday, December 24, 2021, 05:35:06 p.m. EST, John Vella < >> john.ve...@gmail.com> wrote: >> >> I'm going to make it my new year project to finish getting the 80486 pc >> working, and once I've upgraded the memory, (4 Meg isn't going to be >> enough, is it?) I'll be using freedos as the only operating system for my >> distraction free writing pc.? >> On Fri, 24 Dec 2021, 22:00 Jim Hall, <jh...@freedos.org> wrote: >> >> On Fri, Dec 24, 2021 at 2:11 PM Jon Brase <jon.br...@gmail.com> wrote: >> > They're not talking about it in the context of log4j itself, they're >> > talking about it in the context of other open source projects, that >> > don't have something like the Apache foundation behind them, that >> > are critical infrastructure, but have one or two maintainers working >> > on them as a labor of love alongside a day job, and the potential, >> > as such projects become legacy software, for them to still be >> > half-maintained (and maybe maintain a significant user base) long >> > after an institutionally maintained project would have officially >> > been EOLed. >> > >> > And there is something of that kind of risk with any DOS variety >> > still in use. Any remote execution vulnerability, through any >> > network-aware DOS software, is basically automatically a remote root >> > vulnerability by the nature of the system. Now, most FreeDOS users >> > are probably using it for retrogaming and such and not for anything >> > business-critical, but anybody using it in an embedded setting needs >> > to be really careful about exposing it to the network. >> > >> > I really wonder how that would effect DOS, after all there is no >> > web interface, nor any Java in (Free)DOS. So (without having watched >> > this rather long video yet), any such conclusion seems to be a bit >> > far fetch IMHO... >> >> >> The statement in the video (starts at about 24:00, for others who want >> to watch it) was awkwardly made. This person makes the statement that >> some open source projects should just shut down rather than keep going >> (I'm paraphrasing broadly here). And gives the example of "If MS-DOS >> were open source" he opines that it shouldn't go on. >> >> Putting aside the fact that Microsoft did eventually release (early >> versions of) MS-DOS under an open source license, this guy is just >> wrong. Lots of people use DOS and FreeDOS to do useful things, like >> running classic DOS games or applications, and supporting some >> embedded systems or control systems. >> >> I usually try to see the other person's point of view - but in this >> case, he's off base. Whatever. >> >> Jim >> >> >> _______________________________________________ >> 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 >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Fri, 24 Dec 2021 15:02:02 -0800 >> From: Louis Santillan <lpsan...@gmail.com> >> To: "Discussion and general questions about FreeDOS." >> <freedos-user@lists.sourceforge.net> >> Subject: Re: [Freedos-user] Now it gets odd Re: FreeDOS workaround for >> hidden IDE controller? >> Message-ID: >> <CAB9Rao_FpYxmAH33xZ4wP95YSeRLLS3fkN2hO=v70tUtEwcr= >> w...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Apologies for the zombie thread revival. >> >> I recently bought 3 of these Wyse SX0 thin clients and I can confirm that >> FreeDOS 1.3-RC5 (and worse!) and FDISK are buggy on it. I think the >> reality is that BIOS and USB boot code is only partially complete and just >> enough to boot into a more modern OS (ThinOS/Linux, Linux, Windows XPe, >> Windows CE, etc). >> >> The only FreeDOS image this BIOS is able to boot is a converted to RAW >> VMDK >> image from the LiteUSB zip. FullUSB slowly prints 2 dots but then gets >> seems to get stuck there. >> >> However, MS DOS 7 exhibits the same behavior. Floppy Images, Bootable ISO >> images do not boot on the Wyse SX0 BIOS. It is probably more accurate to >> say this BIOS seems to have a heavy preference for HD based booting (USB >> or >> 44-pin IDE). >> >> As for HD hiding, FreeDOS, FD FDISK, MS DOS 7, MS FDISK are confused by >> what the BIOS presents as the drive info usually found in lower areas of >> memory and/or what is presented via BIOS calls. When FD boots from the >> VMDK image via USB drive, FDISK will say that there are no fixed disks >> present...which is physically true though as users, we would like the USB >> drive to be treated as a fixed disk. Worse, Gregg was correct in that 44 >> pin IDE DOM HDD is hidden or atleast obscured from being completely >> visible >> to FDISK. FDISK still complains there are no fixed disks and the DOM >> should definitely be marked a fixed disk by the BIOS. And there may be a >> drive enumeration error there when booting off USB with a 44-pin IDE DOM >> HDD together. USB is mounted as C: while the DOM becomes D:. >> >> I say there is a bug above because while MS DOS 7 and tools like MSD & >> HWiNFO get all kinds of facts about the system incorrect, MS DOS 7 FDISK, >> FORMAT, SYS are still able to complete the tasks of initializing a drive >> partition table, formatting, and transferring a bootable MBR, and then >> transferring the minimal set of files required to boot a system. You >> can't >> quite boot & install from USB as a casual DOS user would expect. Instead, >> you need to initialize the drive, transfer setup files to the new drive, >> reboot w/o USB, then install with a half baked drive. Having MS DOS 7 >> still be able to install with a half working BIOS while FreeDOS (or >> atleast >> FD FDISK) is not able to is the bug. >> >> I'll do some testing with MS DOS 6.22 and see if it is an LBA vs. BIOS >> partition type thing, or maybe a FAT32 vs. FAT16 thing. >> >> >> >> On Sat, Jan 13, 2018 at 4:08 AM Eric Auer <e.a...@jpberlin.de> wrote: >> >> > >> > Hi! As said, I can imagine that the BIOS of your >> > system has problems if the USB stick and DOM both >> > count as harddisks. But you already have bootable >> > DOS installed from floppy now, so I suggest ways >> > which are easier: >> > >> > You can connect the DOM instead of the normal disk >> > to a "bigger" PC with CD-ROM and powerful BIOS and >> > install there, then put the DOM into the small PC >> > again. >> > >> > You can use the ability of FreeDOS drivers to use >> > ISO files instead of physical CD/DVD drives and >> > then run the installer from that virtual CD ROM. >> > >> > Read the SHSU* driver documentation or check the >> > contents of the normal ISO for examples of how to >> > load and configure the drivers. >> > >> > You can use older versions of FreeDOS boot images >> > because those only use FLOPPY type boot areas and >> > avoid the conflict of the current virtual HARDDISK >> > boot image. Then, upgrade to a newer version using >> > the installed version, or just keep things as-is. >> > >> > So there are many ways to have a guilt-free DOS :-) >> > >> > Regards, Eric >> > >> > PS: Yes, you can use USB drives formatted ZIP style >> > to boot from with various - but not all - BIOSes. >> > >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> > _______________________________________________ >> > Freedos-user mailing list >> > Freedos-user@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/freedos-user >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> >> >> ------------------------------ >> >> End of Freedos-user Digest, Vol 2142, Issue 5 >> ********************************************* >> > _______________________________________________ > 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
