Jump to content


  • Content Count

  • Joined

  • Last visited


About Gorgonops

Profile Information

  • Gender
    Not Telling

Profile Fields

    Board-Certified Kvetcher

Recent Profile Visitors

2496 profile views
  1. Mod Hat: It's possible there could be something of use to *somebody* on the MLA since some of these tools could be useful for generic bare-metal 68000 development, but it does seem like it's a bit of a stretch. It would probably be preferable if the OP would stash these somewhere else, maybe stuff them on Github or whatever, and link to it with a coherently titled thread about "68000 cross-assemblers for Windows RT" or whatever.
  2. In case anyone is confused, apparently rmac and rln are cross-assembly tools for developing 68000 and other binaries, mostly targeted at Atari machines: http://rmac.is-slick.com/about/about/
  3. Mod note: I went ahead and moved this to "Compact Mac"; the auto-redirect link in the Mac II forum will expire in 30 days.
  4. If we want to be super-pedantic according to the spec CompactFlash cards should also support several alternate addressing modes, one of which is access via an 8-bit subset of the data pins. This is to make the format easier to use in some embedded applications. (And it's also used by some homebrew retrocomputing storage devices, like the XT-CF card for 8-bit bus PC compatibles.) But CF cards running in IDE adapters or plugged into a full PCMCIA slot will be running in normal 16 bit IDE mode. (They usually even support DMA modes.)
  5. BasiliskII's SCSI passthrough worked well for me the last time I tried it on Linux, but that was 20 years ago so I'm hesitant to promise anything. You *might* actually be a better off with Sheepshaver, the PowerPC emulator; I *think* it also supports SCSI passthrough, and from the last time I looked at both it seemed like SheepShaver might be being slightly better maintained at this point. With BasiliskII I actually got it to drive a Microtek scanner, so I know it doesn't just work on disks.
  6. “25hz” on a conventional phosphor CRT would blink like a strobe light, it wouldn’t be remotely usable. Ask anyone who had an old Commodore Amiga how much fun the interlaced 400 line mode was; the lines flickering were visible to most humans at 30hz and could give you a roaring headache, but this would be worse not just because of the even slower update speed but because a progressive scan that slow would mean that there would be a perceptible “rolling” effect across the entire screen. (An interlaced scan at least keeps the total brightness across the screen more consistent because it’s getting
  7. Yes, anyone who says "25hz" is on crack. They're probably confusing it with the (roughly) 25khz horizontal scan rate of the 512x384 mode. I'm actually somewhat skeptical that this is usually a root cause of their issue because they're obviously going to be trying to use a generic monitor with a DB15-to-HD15 adapter, and I wouldn't *think* there'd be many in circulation that have the sense lines set up for that mode because there were never very many monitors that supported it. (Pretty much be restricted to early generation "Multisyncs"; monitors that will happily sync with sub-31.5khz sources
  8. @olePigeon I know it's probably pointless to volunteer this until you can sort out the mechanical issues, but if you actually get it running do you want to upgrade it to an Applewriter Plus? Last time I went to a library book dump I found, mysteriously mixed in with the computer books, a NIB "Laserwriter Plus Kit". If memory serves inside it should have a new set of ROMs, some font disks, and a replacement label sticker. I say "should have" because it's still in the unbroken shrink wrap, so I don't *actually* know if it has the whole shebang in it. All it gives you is more built in fonts
  9. I have a real soft spot for the "baby" of the Canon line, the LX engine, myself. (As used in the HP IIp/IIIp, Apple's Personal Laserwriters, etc.) My first laser printer was an oddball little Postscript Clone printer that was sold under various OEM names that used that engine, and despite the engine being quoted as 4ppm instead of 8ppm like the SX printers that little printer would run rings around an HP LaserJet or Apple Laserwriter on the "first page out" benchmark because it had an AMD 29000 RISC CPU in it instead of a 68000... So, I dunno, maybe I actually liked that *printer* in spit
  10. Then you should be good good to go. I probably should have mentioned that myself since I have first-hand experience that my 512k-no-e can boot from a IIgs drive connected externally.
  11. Yes, that particular drive works because Apple did some "magic" the tach signal that sidesteps the bug in the 64k ROM. The internal 800k drive mechanisms (or the "original" Mac-styled 800k drive) are the ones with the problem.
  12. The IWM isn't a problem, but the ROM is. To make a long story short trying to use an 800k drive with the original 64k Mac ROMs results in a divide-by-zero error because a bug in said ROMs gets triggered if there isn't a constant slight variance in the tachometer readings, which the 800k drive doesn't provide. (Remember, the 400k drive's speed was directly controlled by a PWM signal generated by the Mac and adjusted based on tach feedback, while the 800k drive self-regulates its speed based on what track the head's on.) You could slap a set of Plus ROMs into the boards for testing, if need
  13. One thing to be careful of if you sub a green or amber CRT into a Mac is the longer persistence phosphors in them are somewhat more prone to burn-in than the white TV phosphor the Mac came with. Probably not a big deal considering how much use a toaster Mac is likely to get in the real world today, but definitely consider turning the brightness down if you walk off for a while. Unless the Mac had other specific "Tempest" modifications there really isn't a lot of reason to suspect the military was involved in the CRT swap, but it is at least *possible* that it was swapped because of some g
  14. I didn't see this answered earlier, I apologize if I'm blind. Asterisks like that usually mean "active low". (IE, the line is pulled to zero to activate the named function. This is usually the case for chip selects. Not universally so, but usually, because TTL process chips in particular tend to float to "1" if they're left disconnected so it's the slightly safer choice.) Another common convention is to put a /slash in front of the name.
  • Create New...