DOSBOX wouldn't be the only useful purpose as you could remain in the Windows 3.1 environment and remove the USB drive without worry. DOS doesn't consume much space nor Windows 3.1 as far as bloat. This is why I was going for a streamlined approach. I even parsed down DOSBOX to its bare minimum files for use in a portable format without installation. I also do a lot of code shaving as I parsed down bloated nVidia drivers to its bare minimum from the hundreds of megabytes it would have consumed. You could run the same DOSBOX code for 2K and 9X and as long as the OS worked on modern hardware it was irrelevant to DOSBOX if you ran it on a P4 or a Z390. Obviously I understand how much code is necessary but that didn't stop them from attempting the impossible then. "Every piece of code" is not far from truth, because you don't understand how much code is actually written to support modern OSes on modern hardware and programs such as DOSBox on top of modern OSes. It's pretty high up in the charts of crazy ideas trying to solve imaginary problems that I've seen on these forums, and that's saying a lot. All other DOS files could be stored onto the 2GB Ramdrive and accessed from within Windows 3.1 without problems. The USB drive could be removed leaving the Windows 3.1 system still intact. Now the method I had used allowed booting to DOS and transferring Windows 3.1 to the Ramdrive and then running it off the Ramdrive. I suppose Windows doesn't like removing the USB drive after copying all the files to a Ramdrive if that were possible on this version. It is also possible to encrypt a Windows To Go drive using BitLocker. If the drive is not inserted in that time-frame, the computer shuts down to prevent possible confidential or sensitive information being displayed on the screen or stored in RAM. Windows To Go has several significant differences compared to a standard installation of Windows 8 on a non-removable storage (such as hard disk drives or solid-state drives).Īs a safety measure designed to prevent data loss, Windows pauses the entire system if the USB drive is removed, and resumes operation immediately when the drive is inserted within 60 seconds of removal. A WTG would be an interesting approach if all you were going for was a DOSBOX type setup removing the real DOS interface but I'm sure this method has some caveats: Now of all the worst Windows OSes to mention there is some sliver of hope in your answer. Granted that limits the choices of flash drive a bit, but gives a consistent experience. Or any modern version of Windows, if one doesn't like Linux. and after I learned the first expansion card remake, then 386 motherboards become precious to me, again. The ISA bus some experiments are quite enough advanced still to begin with as first project, but there are many other things related to LPT port. Atleast with something, or begin with the minimal, but constantly learning. well, this is the latest trend, everyone should do that? (atleast here) Why not, it is so relaxing. To them it is great about finding 386/486 CPUs, but oh boy THIS now really makes their day when they find a rosty XT from a garbage or get the faulty 5.25" drive repaired or get the 286 alive. Some people here are not concerned about PCI soundcards, but make 8-bit ISA bus expansion card remakes (IDE-CF, USB controllers and soundcards). You're in right place with this talk I think. and I'm sure at one point in time it was considered junk but I find it better to preserve these when possible. Avoid if possible.Well I still got a hoard of mint condition XT motherboards. (IIRC, OS2008 doesn't have all the stuff for loopback mounts, so this may be a bit more challenging than portrayed. If it's finicky and requires a genuine block special file, you'll need to use a loopback device, like:losetup /dev/loop0 /media/mmc1/my_sd_card Then, it depends on BasiliskII if you're lucky, it will work with that image file directly, so you can:ln -s /media/mmc1/my_sd_card /dev/cdrom If you don't have a CD-ROM drive, you'll need to dump the CDROM to a file (on your PC):dd if=/dev/cdrom of=/media/my_sd_card/ It should be /dev/sr0, and then you can do ln -s /dev/sr0 /dev/cdrom and basiliskII should get it. If you have a USB CD-ROM drive, get that working (powered hub, probably) with OTG. So, I'm gonna say you should do one of two things. (No, Apples used a different filesystem for CDs, didn't they. I'm guessing here that it doesn't look for a directory /dev/cdrom, but looks for a device file /dev/cdrom, with an ISO9660 filesystem on it. Well, I'm not a user of Macs (old or new), BasiliskII, or Ubuntu8.04 (that's "Hard o' Hearin'", isn't it? :p), but I don't think that's quite right.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |