Search results

If you have a need for a browser, I presume the network is up and running. If so, I suggest using Netatalk or Services for Macintosh on Windows Server and make a file share that way. (with an older System, AppleTalk over IP might not be an option, so you need a version of Windows or Netatalk...

It's more the fact that 10 year old hardware isn't retro, it's in the trailing edge of modern. The really old stuff will struggle to do the things people expect today (mostly internet stuff, and internet stuff uses modern crypto and protocols) without a helper machine or phone, either of which...

That, and VNC is slow at the best of times.

IIRC, it doesn't matter about 2FA or passwords. The only safe mechanism right now is the temporary number ID.

Uhhhh, bad idea?

2008 R1 is Vista based and the last 32-bit Windows Server. R2 is 7 based.

I vote for run Windows.

You know, it'd be awful if it happened that they didn't fit properly...

That and the facts Macs are miserably slow compared to even a low end Cube. Support HW and DMA matters a LOT.

brb porting AmigaOS to a TI-89.

A Mac Plus might have a 1.44 MB drive. Apple called them FDHD, IIRC. To write images, for PC drives you can write a disk image - otherwise Disk Copy on a classic Mac is a safe bet,

Just get a Floppy Emu and you can mount any 400K/800K/whatever image you like. Put them on an SD card, it'll work.

A Mac 128k only has a 400K drive, which uses a different encoding than PC-like encoded floppies that Macs with 1.44MB drives use. You need a "bridge" Mac - one old enough that it can write 400K disks, but still transfer files with newer systems somehow. (like 1.44MB disks or the network.)

Are you sure they're not stored directly in the folder itself? Also check extensions like Appearance Manager.

If you want to use CSS, load it externally. If browsers don't know what to do with it, they'll just ignore it. Same story for JS. This is a case of graceful degradation to the extreme.

PHP won't have anything to do with how accessible it is to older browsers, its what it shunts to the client. Autoindex in a web server is handled on the server end, and likely outputs simple HTML and is written in native code. Gopher is read-only. If your system is too slow to handle a browser...

Except that's SSHv1, which is being killed. MacSSH will get you SSHv2 though, albeit without a lot of modern Kex/Ciphers.

Uploads aren't too hard. Old browsers can do them, but on the Mac, you need to pickle the resource fork somehow before hand. (MacBinary/BinHex to the rescue.) PHP makes me :( though.

The audio seems to be working better now, but I haven't poked it in a while.

IIRC, wasn't that copy known to be corrupt?