Search results

per the hardware devnotes the IIci indeed disables the NMI keystroke and requires a control panel to turn it back on. No idea where to find that control panel, of course. Maybe someone else can help there?

i *think* either some ROMs or some OS versions go about disabling the NMI key at the ADB controller level (where it is processed) but we don't remember where we read that...

I'm interested in the second run, definitely :)

Hi y'all, For SCSI hacking purposes, we picked up an Ancot Ultra2000 SCSI analyzer. It works alright, but it's got firmware 2.1 on it, and we know from searching that there exists a 2.2 upgrade. Unfortunately, Ancot itself underwent Total Existence Failure and all of their property is locked...

Oh _dear_ that's some incredibly cursed arcana. Wew.

sorry to double-post, but, some other random tidbits floated to the top of our mind just before we fell asleep - on a lot of UNIX systems, the kernel debugger is fairly likely to communicate via serial port. in emulation this is less of a problem because you can tell qemu to connect the serial...

qemu-system-ppc just doesn't do anything when you type nmi. we'd be upset too if it crashed the thing.

NB: we forget the exact key that maps into cmd-pwr. Might be Meta_R and not Super_R. unfortunately we can't find anything salient on Bitsavers. I can probably help if you get into the debugger though.

I dunno of any documentation for the kernel debugger itself, other than the fact that it exists, unfortunately. We would figure the A/UX kernel debugger to be broadly similar to other SysV kernel debuggers of the era, though. With qemu-system-ppc we know that typing nmi at the "qemu monitor...

haven't seen that _particular_ error, if we had to look, we would probably break out the kernel debugger and set a breakpoint on that return code.

So i think what's going on here is that the "ROM Map" files are distinct from the "ROM Symbol File". The ROM maps are indeed text-only and intended for human consumption, and the "ROM Symbol File" is likely to be debugging information output from the compiler.

Hi! I'm new here and have spent a bit of time playing with MacNosy to try and reverse-engineer the QT 150 drivers. However, we're hitting some roadblocks - the drivers seem to use GeoPort calls, which aren't very well documented, and also the drivers seem to work by way of Foreign File Access...

personally: Mac OS 9 on the G4 series, with Carracho Client, and an IRC client running under screen in MacSSH.

@Crutch I called him earlier this month, it turns out that he's much more of a phone guy. He sent the latest version (2.95) via email after we sent him $100 via PayPal. I don't know if he's still got boxed copies available, though.

coincidentally, we just read through the first issue of Develop which has opinions on just this topic: Hope this helps :)