I wasn't talking about 16 bit in general. Its that DOS is simply structured and coded. the bits of code could count on being the only thing active in RAM and the CPU when executing. No need to be polite or "well behaved". There was a simple hierarchy of simple calls directly to the hardware. Timing like wait states was critical and something of a voodooish black art. I'm saying some of the new hardware extensions and network protocols are made for more sophisticated OSs and you will have difficulty getting DOS's structure to accept them well. This would happen even if all the hardware met specs. Add wonky specs or hardware that doesn't behave well under any OS and yeah I can see it eating up a lot person years and enthusiasm.
CB On 3/26/14, Bret Johnson <bretj...@juno.com> wrote: >> The point I'm making is DOS is a "duh" dumb as a stick OS. > > Not true. Just because DOS is not multi-tasking or multi-threaded or > doesn't natively use protected mode doesn't make it "dumber" than mainstream > OS's -- just different. In fact, it's vastly superior (aka "smarter") for > certain kinds of applications. > >> For example, its possible your problem is somewhere in dumbing down 32 >> or 64 bit USB to 16 bit DOS a byte is being lost. > > In this particular case, it doesn't have anything to do with 16-bit vs. > 32-bit vs. 64-bit processing. The problem is with BIOS's and/or USB > hardware not complying with published standards and conventions. That's > what you were alluding to earlier, and it hasn't changed. What has changed > is that, for the most part, all the hardware & BIOS manufacturers care about > nowadays is making sure their stuff works with the latest version of > MS-Windows. > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
