liam_on_linux: (Default)
 

My #1 annoyance these days, because it is so egregious, is Electron apps.

I guess because the only language some programmers know is Javascript, of which I know little but what little I know places it marginally above PHP in intrinsic horror.

So people write standalone apps in a language intended for tweaking web pages, meaning that to deploy those apps requires embedding an entire web browser into every app.

And entire popular businesses, for example Slack, do not as far as I can tell have an actual native client. The only way to access the service is via a glorified web page, running inside an embedded browser. Despite which, it can't actually authenticate on its own and needs ANOTHER web browser to be available to do that.

Electron apps make Java ones look lean and mean and efficient.

Apparently, expecting a language that can compile to native machine code that executes directly on a CPU, and which makes API calls to the host OS in order to display a UI, is quaint and retro now.

And it's perfectly acceptable to have a multi-billion-dollar business that requires a local client, but which does not in fact offer native clients of any form for any OS on the market.

It's enough to make me want to go back to DOS, it really is. Never mind "nobody will ever need more than 640kB"... if you can't do it in 640kB and still have enough room for the user's data, maybe you should reconsider what you are doing and how you are doing it.               

liam_on_linux: (Default)
[Another recycled mailing list post]

I was asked what options there were for blind people who wish to use Linux.

The answer is simple but fairly depressing: basically every blind person I know personally or via friends of friends who is a computer user, uses Windows or Mac. There is a significant move from Windows to Mac.

Younger computer users -- by which I mean people who started using computers since the 1990s and widespread internet usage, i.e. most of them -- tend to expect graphical user interfaces, menus and so on, and not to be happy with command-line-driven programs.

This applies every bit as much to blind users.

Linux can work very well for blind users if they use the terminal. The Linux shell is the richest and most powerful command-line environment there is or ever has been, and one can accomplish almost anything one wants to do using it.

But it's still a command line, and a notably unfriendly and unhelpful one at that.

In my experience, for a lot of GUI users, that is just too much.

For instance, a decade or so back, the Register ran some articles I wrote on switching to Linux. They were, completely intentionally, what is sometimes today called "opinionated" -- that is, I did not try to present balance or a spread of options. Instead I presented what was, IMHO, the best choices.


Multiple readers complained that I included a handful of commands to type in. "This is why Linux is not usable! This is why it is not ready for the real world! Ordinary people can't do this weird arcane stuff!" And so on.

Probably some of these remarks are still there in the comments pages.

In vain did some others try to reason with them.

But it was 10x quicker to copy-and-paste these commands!
-> No, it's too hard.

He could give GUI steps but it would take pages.
-> Then that's what he should have done, because we don't do this weird terminal nonsense.

But then the article would have been 10x longer and you wouldn't read it.
-> Well then the OS is not ready, it's not suitable for normal people.

If you just copy-and-paste, it's like 3 mouse clicks and you can't make a typing error.
-> But it's still weird and scary and I DON'T LIKE IT.

You can't win.

This is why Linux Mint succeeded -- partly because when Ubuntu introduced its non-Windows-like desktop after Microsoft threatened to sue, Mint hoovered up those users who wanted it Windows-like.

But also because Mint didn't make you install the optional extras. It bundled them, and so what if that makes it illegal to distribute in some countries? It Just Worked out of the box, and it looked familiar, and that won them millions of fans.

Mac OS X has done extremely well partly because users never ever need to go need a command line, for anything, ever. You can if you want, but you never, ever need to.

If that means you can't move your swap file to another drive, so be it. If that means that a tonne of the classic Unix configuration files are gone, replaced by a networked configuration database, so be it.

Apple is not afraid to break things in order to make something better.

The result has been to become the first trillion-dollar computer company, and hundreds of millions of happy customers.

Linux gives you choices, lets you pick what you want, work the way you want... and despite offering the results for free, the result has been about 1% of the desktop market and basically zero of the tablet and smartphone markets.

Ubuntu made a valiant effort to make a desktop of Mac-like simplicity, and it successfully went from a new entrant in a busy marketplace in 2004 to being the #1 desktop Linux within a decade. It has made virtually no dent on the non-Linux world, though.

After 20 years of this, Google (after *bitter* internal argument) introduced ChromeOS, a Linux which takes away all your choices. It only runs on Google hardware, has no apps, no desktop, no package management, no choices at all. It gives you a dead cheap, virus-proof computer that gets you on the Web.

In less time than Ubuntu took to win about 1% of the Windows market over to Linux, ChromeBooks persuaded about one third of the world laptop buying market to switch to Linux. More Chromebooks sell every year -- tens of millions -- than Ubuntu users in total since it lauched.

What effect has this had on desktop Linux? Zero. None at all. If that is the price of success, they are not willing to pay it. What Google has done is so unspeakable foul, so wrong, so blasphemous, they don't even talk about it.

What effect has it had on Microsoft? A lot. Cheaper Windows laptops than ever, new low-end editions of Windows, serious efforts to reduce the disk and memory usage...

And little success. The cheap editions lose what makes Windows desirable, and ultra-cheap Windows laptops make poorer slower Chromebooks than actual Chromebooks.

Apple isn't playing. It makes its money in the high-end.

Unfortunately a lot of people are very technologically conservative. Once they find something they like, they will stay with it at all costs.

This attitude is what has kept Microsoft immensely profitable.

A similar one is what has kept Linux as the most successful server OS in the world. It is just a modernised version of a quick and dirty hack of an OS from the 1960s, but it's capable and it's free. "Good enough" is the enemy of better.

There are hundreds of other operating systems out there. I listed 25 non-Linux FOSS OSes in this piece, and yes, FreeDOS was included.

There are dozens that are better in various ways than Unix and Linux.

  • Minix 3 is a better FOSS Unix than Linux: a true microkernel which can cope with parts of itself failing without crashing the computer.

  • Plan 9 is a better UNIX than Unix. Everything really is a file and the network is the computer.

  • Inferno is a better Plan 9 than Plan 9: the network is your computer, with full processor and OS-independence.

  • Plan 9's UI is based on Oberon: an entire mouse-driven OS in 10,000 lines of rigorous, type-safe code, including the compiler and IDE.

  • A2 is the modern descendant of Oberon: real-time capable, a full GUI, multiprocessor-aware, internet- and Web-capable.

(And before anyone snarks at me: they are all niche projects, direly lacking polish and not ready for the mass market. So was Linux until the 21st century. So was Windows until version 3. So was the Mac until at the very least the Mac Plus with a hard disk. None of this in any way invalidates their potential.)

But almost everyone is too invested in the way they know and like to be willing to start over.

So we are trapped, the monkey with its hand stuck in a coconut shell full of rice, even though it can see the grinning hunter coming to kill and eat it.

We are facing catastrophic climate change that will kill most of humanity and most species of life on Earth, this century. To find any solutions, we need better computers that can help us to think better and work out better ways to live, better cleaner technologies, better systems of employment and housing and everything else.

But we can't let go of the single lousy handful of rice that we are clutching. We can't let go of our broken political and economic and military-industrial systems. We can't even let go of our broken 1960s and 1970s computer operating systems.

And every day, the hunter gets closer and his smile gets bigger.
liam_on_linux: (Default)
Someone asked me if I could describe how to perform DOS memory allocation. It's not the first time, either. It's a nearly lost art. To try to illustrate that it's a non-trivial job, I decided to do something simpler: describe how DOS allocates drive letters.

I have a feeling I've done this before somewhere, but I couldn't find it, so I tried writing it up as an exercise.

Axioms:

  • DOS only understands FAT12, FAT16 and in later versions FAT32. HPFS, NTFS and all *nix filesystems will be skipped.

  • We are only considering MBR partitioning.

So:

  • Hard disks support 2 partition types: primary and logical. Logical drives must go inside an extended partition.

  • MBR supports a legal max of 4 primaries per drive.

  • Only 1 primary partition on the 1st drive can be marked "active" and the BIOS will boot that one _unless_ you have a *nix bootloader installed.

  • You can only have 1 extended partition per drive. It counts as a primary partition.

  • To be "legal" and to support early versions of NT and OS/2, only 1 DOS-readable primary partition per drive is allowed. All other partitions should go inside an extended partition.

  • MS-DOS, PC DOS and NT will only boot from a primary partition. (I think DR-DOS is more flexible and  I don't know for FreeDOS.)

Those are our "givens". Now, after all that, how does DOS (including Win9x) assign drive letters?

  1. It starts with drive letter C.

  2. It enumerates all available hard drives visible to the BIOS.

  3. The first *primary* partition on each drive is assigned a letter.

  4. Then it goes back to the start and starts going through all the physical hard disks a 2nd time.

  5. Now it enumerates all *logical* partitions on each drive and assigns them letters.

  6. So, all the logicals on the 1st drive get sequential letters.

  7. Then all the logicals on the next drive.

  8. And so on through all logicals on all hard disks.

  9. Then drivers in CONFIG.SYS are processed and if they create drives (e.g. DRIVER.SYS) those letters are assigned next.

  10. Then drivers in AUTOEXEC.BAT are processed and if they create drives (e.g. MSCDEX) those are assigned next.

So you see... it's quite complicated. :-)

Assigning upper memory blocks is more complicated.

NT changes this and I am not 100% sure of the details. From observation:

  • NT 3 did the same, but with the addition of HPFS and NTFS (NT 3.1 & 3.5) and NTFS (3.51) drives.

  • NT 4 does not recognise HPFS at all but the 3.51 driver can be retrofitted.

  • NT 3, 4 & 5 (Win2K) *require* that partitions are in sequential order.

Numbers may be missing but you can't have, say:
[part № 1] [part № 2] [part № 4] [part № 3]

They will blue-screen on boot if you have this. Linux doesn't care.

Riders:

  1. The NT booloader must be on the first primary partition on the first drive.

  2. (A 3rd party boot-loader can override this and, for instance, multi-boot several different installations on different drives.)

  3. The rest of the OS can be anywhere, including a logical drive.

NT 6 (Vista) & later can handle it, but this is because MS rewrote the drive-letter allocation algorithm. (At least I think this is why but I do not know for sure; it could be a coincidence.)

Conditions:

  • The NT 6+ bootloader must be in the same drive as the rest of the OS.

  • The bootloader must be on a primary partition.

  • Therefore, NT 6+ must be in a primary partition, a new restriction.

  • NT 6+ must be installed on an NTFS volume, therefore, it can no longer dual-boot with DOS on its own & a 3rd party bootloader is needed.

NT 6+ just does this:

  1. The drive where the NT bootloader is becomes C:

  2. Then it allocates all readable partitions on drive 1, then all those on drive 2, then all those on drive 3, etc.

So just listing the rules is quite complicated. Turning into a step-by-step how-to guide is significantly longer and more complex. As an example, the much simpler process of cleaning up Windows 7/8.x/10 if preparing to dual-boot took me several thousand words, and I skipped some entire considerations to keep it that "short".

Errors & omissions excepted, as they say. Corrections and clarifications very welcome. To comment, you don't need an account — you can sign in with any OpenID, including Facebook, Twitter, UbuntuOne, etc.
liam_on_linux: (Default)
Interested in running DOS programs on 64-bit Windows (or x86 macOS or Linux)? Would you like to run classic DOS applications such as WordPerfect, natively and without emulation on a modern OS? Would you like to get an MS-DOS prompt back under Windows 10 on AMD64?

I found a copy of the IBM PC DOS 2000 VM from Connectix VirtualPC for Mac, and converted it into a format that VirtualBox can open and run.


This was bundled for free with Connectix VirtualPC. VirtualPC is now owned by Microsoft and is a free download.

Old versions are out there for free download, e.g. the Mac version 4.

Just the PC DOS 2000 disk image, converted to VirtualBox VDI format, compressed in Zip format, is here. It's about 10MB.

Note: this is the complete, unmodified Connectix VirtualPC DOS image. It contains DOS integration tools for VirtualPC which do not work with VirtualBox. Unfortunately, VirtualBox does not offer guest additions for DOS. You will see some minor errors as it boots due to this. How to fix them is below.

If you actually want to try this, here are a few things you will need to know.

This is PC DOS 2000, AKA PC DOS 7.01. It's PC-DOS 7 plus bugfixes and
Y2K compatibility. It is not FAT32-capable: for that, you need PC DOS 7.1. Here is how to get and install that – it too is a free download. This VHD is the ideal basis for building a PC DOS 7.1 VM and that is why I created it.

PC DOS 7 is from the same code-base as MS-DOS 6.22, but with updates. It has IBM's E editor instead of the Microsoft full-screen editor, and IBM's Rexx programming language instead of QBASIC. It does not support DoubleSpace or DriveSpace disk compression. It does include IBM's licensed-in antivirus and backup tools, but to be honest I have not investigated these. It is installed on a 2GB FAT16 partition which is the single primary active partition on the virtual hard disk, just as Connectix shipped it.

PC DOS 2000 does support power-management, but it is not enabled by default. Without it, this means that the VM will take (and waste) 100% CPU. (Unlike MS-DOS 6.22, PC DOS also has native PCMCIA card
support, but that is no use in a VM – however, it may be helpful if you want an OS for a very old laptop.) To enable power management, you should add a line to the CONFIG.SYS file that says:

device=c:\dos\power.exe

That should be enough – afterwards, your DOS VM will only take the tiny amount of CPU that it needs.
DOS needs only 32MB of RAM and will run fine in 1MB. Yes, one megabyte, not one gigabyte.

You might also want to remove the AUTOEXEC.BAT line that references a FSHARE program in the CNTX directory, as that won't work under VirtualBox. Type the following:

e autoexec.bat

Look for the line that says:

C:\CNTX\FSHARE.EXE

Insert the word REM at the beginning of the line, so it says:

REM C:\CNTX\FSHARE.EXE

Press F2 to save the file. Press F3 to exit. Reboot the VM with [Host]+[R].

PC DOS 2000 was the bundled demo virtual machine with Connectix's VirtualPC. VirtualPC is, for now, obsolete – it does not work correctly under any version of Windows after Win7. Its last hurrah was as the basis for the XP Mode feature in Win7, which did not work on Windows 8 (although there is an easy fix to run it under Win8 or 8.1) or at all under Windows 10.

(I say "obsolete for now" as the original purpose of VirtualPC was as a way to run x86 DOS and Windows on PowerMacs, which did not have x86 processors and could not natively run x86 binaries. Now that Apple is transitioning to processors with the ARM instruction set, newer Macs can again not natively run x86 binaries. Yes, there is a built-in emulator, but Rosetta 2 will not work well on a hypervisor. So, there is once again an opening in the market
for a PC emulator for Macs, if Microsoft chose to resurrect the application. I personally would like to see that – VirtualPC was a good tool and the easiest, least-complicated way to run guest OSes on top of those it ran on, simpler to use than VMware or VirtualBox.)

Yes, this does mean that there is a legal, activated copy of Windows XP Professional for free download that you can run under Win7/8/8.1. And yes, you can extract it and run it under VirtualBox if you wish. I wrote an article for the Register describing how to do that. The snag is that the activation only works for a VirtualPC VM and it will fail on any other hypervisor. You will need a license key or to crack this ancient, obsolete version of Windows. Obviously I cannot help you with that. None of this is needed for PC DOS: it has no activation, copy protection or anything like it.

Microsoft acquired Connectix in 2003 and VirtualPC provided the basis for Microsoft Hyper-V (just as QEMU provides the basis for KVM on Linux) – file formats, management tools and so on. In theory, VirtualBox can attach a Hyper-V virtual hard disk to a VirtualBox VM and boot from it, but in my testing, this did not work with this ~20-year-old Apple VirtualPC file. I had to use command-line tools to convert it to VMware format, and then from VMware format to native VirtualBox format. Apart from testing, that is all I have done.

For my own use, I have of course slightly tweaked and updated the VM. I have configured memory management, added a few useful tools from from a WinME boot diskette:

  • the MS IDE CD device driver

  • the MS mouse driver

  • the MS full-screen editor

  • the MS SCANDISK disk-checking tool

... and a few more, simply because I'm more familiar with them. I've disabled the Connectix guest additions but I have not replaced them – I run it under Linux, where I can just mount the disk image to get files on or off it. I also have a modernized version with the FAT32-capable PC DOS 7.1.

If you are interested in these changes, please leave a comment on the blog and I will help you reproduce them for yourself. Please also let me know of any errors, corrections, additional info or any help you want with getting this working.

You can log in to LiveJournal to comment with any OpenID, including Facebook, Twitter or Google accounts.


I emphasize that this is an unmodified disk image. I have not in any way altered the contents of the VM image, just converted it from one format to another. These files remain the property of their original copyright holders.
liam_on_linux: (Default)
I tried to leave a helpful, constructive answer to this interesting blog post:
https://www.forsure.dev/-/2020/05/19/640-kilobytes-of-ram-and-why-i-bought-an-ibm-5160/

In case it helps, there are a few things that you could fix or improve on this machine. Please feel free to contact me if you would like more explanation.

> No HISTORY. You can repeat the last command by pressing the right-arrow.

This is incorrect. You say that you have IBM PC DOS 5. If so, this includes the DOSKEY command. This will give you a command-line history with editing. Just type `dos\doskey` to load it.

> For a starters, on IBM DOS (version 5.0) there is no $PATH.

There certainly should be! DOS has 2 configuration files, which live in the root directory of the boot drive (A: or C:). They are called [1] CONFIG.SYS and [2] AUTOEXEC.BAT. In the 2nd, there should be a line:
PATH=C:\DOS; C:\
If you don't have them, email me and I can help you write some. I am easy to find on Google.

> Trying to exit QBASIC. Epic fail

That is *not* QBASIC; QBASIC has a GUI. You were in either BASICA or GWBASIC. The command to quit is `system`, if I remember correctly after 30 years.

> but there is no scrolling

Yes there is. Type `dir /p` for page-by-page. `dir /w` gives a wide listing. You can combine these: `dir /w /p`. You can also do `dir | more`.

> the monitor only is 25 lines.

This depends on the graphics card. If you have an MDA card, no, 25 lines is all. Try `mode con: lines=43` or `mode con: lines=50`. This will only work on a VGA-compatible card, though, and you will need ANSI.SYS installed, I think.

> wppreview, I totally miss the point of this program.

It is not part of DOS. Sounds like a WordPerfect preview program for use with mailmerge.

> I will have to remap my function key in i3, because I am currently using the windows key for this.

It is easy to remap CapsLock to be a “Windows” (Super) key. This is how I use my IBM Model M in Linux. I suggest `xmodmap`.

> Besides that, I found this great archive with manuals and bootdisks and even PC DOS 5.02.

If you are willing to change the DOS version, I suggest DR DOS 3.41. The reason is this: MS/PC DOS 5, 6 & later are designed for 386 memory management. This is impossible on an 8088 chip, and as a result, you will have very little free memory. Many DOS programs won’t work.

DR-DOS is a better 3rd party clone of DOS, by the company that wrote the original OS (CP/M) that MS-DOS was ripped-off from. The first version is 3.41 (before that it had different names) and it is far more memory-efficient.

https://winworldpc.com/product/dr-dos/3x

But if you want to stay with an IBM original DOS, then IBM developed PC DOS all the way to version 7.1, which supports EIDE hard disks over 8GB, FAT32 and some other nice features. It is a free download.

I have described how to get it here:
https://liam-on-linux.livejournal.com/59703.html

PC DOS 7 is a bit strange; IBM removed Microsoft’s GUI editor and replaced it with an OS/2-derived one called E, which has a weird UI. IBM also removed GWBASIC and replaced it with the Rexx scripting language.

Personally, I combine bits of PC-DOS 7.1 with Microsoft’s editor, Microsoft’s diagnostics, Scandisk disk-repair tool and some other bits, but that is more than I can cover in a comment!

There is a lot you can do to upgrade a 5160 if you wish. Here is a crazy example:

https://sites.google.com/site/misterzeropage/

I would not go that far, but a VGA card, VGA CRT, a serial mouse and an XTIDE card with a CF card in it, and it would be a lot easier to use…
liam_on_linux: (Default)
From a Quora answer.

Windows 10 is Windows NT version 10. Windows NT copied the patterns of MS-DOS, because DOS was the dominant OS when NT was launched in 1993.

DOS copies its disk assignment methods from Digital Research CP/M, because DOS started out as a copy of CP/M.
https://en.wikipedia.org/wiki/CP/M

What Microsoft bought was originally called QDOS, Quick and Dirty OS, from Seattle Computer Products.
https://en.wikipedia.org/wiki/Seattle_Computer_Products

The way IBM PC-compatibles assign disk drives is copied from the way the IBM PC running PC DOS assigned them. PC DOS is IBM’s brand of MS-DOS. See the answer about Apricot computers for how (some) non-IBM-compatible DOS computers assign drive letters.

The way that CP/M and MS-DOS originally assigned drive letters was simple.
The drive you booted from was the first, so it was called A. It doesn’t matter what kind of drive. But floppy drives were expensive and hard drives were very expensive, so in the late 1970s when this stuff was standardized, most machines only had a floppy drive or 2.

If you only had 1 drive, which was common, then the OS called it both A and B. This is so that you could copy files from one disk to another; otherwise there would be no way.

So, you copied from A: to a the virtual drive B: and the OS prompted you to swap disks as necessary.
Floppy drives got cheaper, and it became common to have 2. So, the one you booted from was A, and the second drive was B.

So far, so simple. If you were rich and added more floppy drives, you got A, B, C, D etc. and if you were lucky enough to have good firmware that let you boot from any of them, the one you booted off was A and the rest were simply enumerated.

It is common to read that "certain drive letters are reserved for floppies". This is wrong. Nothing was reserved for anything.

If you had a floppy and a hard disk, then if you booted off the floppy, the floppy drive was A and the hard disk was B. If you booted off the hard disk — and early hard disks were often not bootable — then the hard disk became A and the floppy became B.

You didn't need the virtual drive thing any more; to copy from one floppy to another, you copy from floppy to hard disk, then swap floppies, then copy back.

However, having drives change letter depending on which you booted from was confusing — again, see the Apricot comment — so later firmware started changing this. So, for instance, in the Amstrad PCW range, the last new CP/M computers made, Amstrad hard-wired the drive letters.
https://en.wikipedia.org/wiki/Amstrad_PCW

The first floppy was A. The second, if you had one, was B. And the rest of the machine's RAM aside from the 64 kB that CP/M used was made into a RAMdisk called drive M: "M" for Memory.

The IBM PC hard-wired some letters too. Floppy 1, A. Floppy 2, B, even if not there. Partition 1 on hard disk 1, C. Partition 1 on hard disk 2, D. Partitions 2+ on HD #1, E/F etc. Partitions 2+ on HD #2, G/H etc.

This was very common as up to and including MS-DOS 3.3, DOS only supported partitions of up to 32 MB. So, for instance, in 1989 I installed an IBM PS/2 Model 80 with a 330MB hard disk as a server running the DOS-based 3Com 3+Share NOS.
https://en.wikipedia.org/wiki/3%2BShare

It had hard disk partitions lettered C, D, E, F, G, H, I, J, K, L and M. (!)

DOS has a setting called LASTDRIVE. This tells it how many drive letters to reserve for assignment. Each takes some memory and you only had 640 kB to use, no matter how much was fitted. https://en.wikipedia.org/wiki/Conventional_memory

The default value for LASTDRIVE is E. Thus, the rival Novell Netware OS used the first drive after that as the "network drive" with the login command and so on: F.
https://en.wikipedia.org/wiki/NetWare

So, drive letters are not "reserved". They were originally assigned sequentially starting with the boot drive, and then by hardware ID number, and later by that and partition number, according to a slightly complex scheme that several people have linked to.

It is a convention that A was the first floppy and C was the first hard disk, and everything else was assigned at boot time.
liam_on_linux: (Default)
My previous post was an improvised and unplanned comment. I could have structured it better, and it caused some confusion on https://lobste.rs/

Dave Cutler did not write OS/2. AFAIK he never worked on OS/2 at all in the days of the MS-IBM pact -- he was still at DEC then.

Many sources focus on only one side of the story -- the DEC side, This is important but only half the tale.

IBM and MS got very rich working together on x86 PCs and MS-DOS. They carefully planned its successor: OS/2. IBM placed restrictions on this which crippled it, but it wasn't apparent at the time just how bad this would turn out to be.

In the early-to-mid 1980s, it seemed apparent to everyone that the most important next step in microcomputers would be multitasking.

Even small players like Sinclair thought so -- the QL was designed as the first cheap 68000-based home computer. No GUI, but multitasking.

I discussed this a bit in a blog post a while ago: http://liam-on-linux.livejournal.com/46833.html

Apple's Lisa was a sideline: too expensive. Nobody picked up on its true significance.

Then, 2 weeks after the QL, came the Mac. Everything clever but expensive in the Lisa stripped out: no multitasking, little RAM, no hard disk, no slots or expansion. All that was left was the GUI. But that was the most important bit, as Steve Jobs saw and nobody much else did.

So, a year later, the ST had a DOS-like OS but a bolted-on GUI. No shell, just a GUI. Fast-for-the-time CPU, no fancy chips, and it did great. It had the original, uncrippled version of DR GEM. Apple's lawsuit meant that PC GEM was crippled: no overlapping windows, no desktop drive icons or trashcan, etc.

Read more... )
liam_on_linux: (Default)
Not only do I have recent, decent-performance, still-perfectly-usable PC hardware that can't boot off USB, or can but can't remember the setting* so that it has to be done every time you need it, but I also note that the BIOS in the current shipping versions of both VirtualBox and VMware cannot boot from USB devices.

It is not a rare or uncommon problem.

Yes, I have had dozens of techies say they've never seen it. Well, tough. It's not rare; it just means that they've had a lot less breadth of experience than I have.

Read more... )

June 2025

S M T W T F S
1234567
891011121314
15161718192021
22 232425262728
2930     

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 25th, 2025 01:51 pm
Powered by Dreamwidth Studios