Jump to content

powermax

6502
  • Content count

    86
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    Software Development, Vintage Computing

Recent Profile Visitors

286 profile views
  1. Hello crews, I hope to find someone here who has a working PowerBook/iBook G3/G4 running Mac OS 9.x and who could help me with the hibernation feature in pre-OS X Mac OS. Mac OS 9 does support system hibernation like OS X does ("Safe Sleep"). It seems to work on laptops only - I wasn't able to activate it in my iMac G3 indigo. This feature can be supposedly enabled in the Energie saver control panel. There should be a check box "Preserve memory contents on sleep" in the "Advanced settings" tab. Can someone running Mac OS 8-9 verify if the above mentioned option is present in the Energie saver CP? This task is a part of my personal project trying to modernize and run Mac OS 9 on the later PPC hardware. Thank you in advance! Cheers Max
  2. powermax

    CUDA, EGRET, HC6805 Hacking

    Hi crews, I've just started uploading a commented assembly for the Cuda Firmware v2.37, see this Github repository. To my knowledge, that's the latest firmware available but we need to re-check it. In the next days, I'm going to put even more docs on Cuda - so stay tuned!
  3. powermax

    LC TDK PSU issues

    Maybe FEP16CT?
  4. powermax

    LC TDK PSU issues

    Is it correct that this TDK PSU is more than 20 years old? If so, getting another old unit doesn't guarantee it won't fail, too...
  5. powermax

    LC TDK PSU issues

    Well, if you can get a replacement PSU of the same type for little money, go ahead! If not, it's worth trying to fix the existing one as I did with my old Astec PSU (still working after been fixed). BTW, a quick ebay search reveals a used TDK 699-0153 for 79,95 € + shipping from Germany to Italy. I bet the fix is cheaper... Another attractive option is to attach a modern PSU with compatible voltages and wattage...
  6. powermax

    LC TDK PSU issues

    The badcaps forum (what a funny name) has a board dedicated to PSU troubleshooting and repair. You could ask there if they can identify that mysterious component. There are several people around there skilled in the art...
  7. powermax

    CUDA, EGRET, HC6805 Hacking

    Never heard anything about it. Can you supply some more information on that CUDA Lite chip? Well, CUDA as well as its predecessors (Bit-bang, Egret) is basically a multipurpose MCU that emulates some peripheral bus protocol using the bit banging approach. In other words, all required functionality is implemented in software. To recreate the chip, we thus need to download and understand its firmware. IIRC, Arbee from MAME project may have already obtained a dump of CUDA Lite as he did for other CUDA versions. I'm going to ask him...
  8. powermax

    CUDA, EGRET, HC6805 Hacking

    Glad to know, thanks! IIUC, I'd need an extra account to access the Wiki, right? Is there any ASIC-related Wiki section there? I didn't see any. Where may I post such information to?
  9. Frankly spoken, I'm out of my depth now. I think you need to gather more data on the failure of your Quadra board. Can you do some electrical analysis of your board and compare the signals it generates with a known working board? That would be very helpful. Otherwise, we won't be able to go a step beyond guessing. Moreover, I don't think that any blind IC replacement would be a good idea, especially when the ICs in question are vintage ASICs you'll probably not be able to find any replacement for...
  10. powermax

    Free 68k (dis)assembler for Mac?

    Thank you for pointing me to FDisasm that I'm aware of. I personally never considered to give it a try because I don't use Mini vMac emulator I never seen any ROM formatting files for the ROMs of my interest (PowerMacintosh 6100 and newer) MAME/MESS offered me anything I need in just one package. Moreover, MAME's source code is a superb and the most complete documentation on the proprietary Macintosh hardware ever available I'm glad to hear that your disassembler offers some annotation functions one could find in only few advanced tools like IDA Pro. It looks like we need to consolidate our efforts on MacROM-related tools. BTW, are you aware of the cdg5 ("countdown to G5") project started by a small team off the macos9lives forum? The goal of this project is to hack Mac OS 9 to run on unsupported Macintosh hardware (PowerMac with newer G4/G5 processors). These guys have created their own toolchain, vaguely similar to yours (Python-based disassembler/annotator + MPW for rebuilding the ROM). You can take a look at this repository. Sure! My preferred workflow is to use a debugger coupled with an annotated assembly. Some tricks like memory mirroring simply cannot be coped with by the static analysis alone...
  11. This would be possible if your board had EEPROM or Flash storage. It's a well-known fact that all Apple desktops in the 90s use 3.6V lithium batteries to maintain non-volatile memory. That means that PRAM (NVRAM) is actually a small amount of CMOS RAM powered either by the mains or the battery. In the case ALL power is lost (that's it - the battery was pulled and the power supply is off), the whole PRAM content is also lost. It's difficult to imagine what kind of magic TechToll can do beyond that... FYI, PRAM is a part of the RTC IC (U92). Its part number is either 343S0042 (Motorola-made) or 344S042 (VLSI-made). I don't know which one sits on your board...
  12. powermax

    CUDA, EGRET, HC6805 Hacking

    What's about the 68kmla Wiki?
  13. powermax

    Free 68k (dis)assembler for Mac?

    If you're going to gather some knowledge about a specific ROM or ROMs, the question is if the static analysis (i.e. disassembly/hex dump) would be the right tool for the job. You can surely run a disassembler over your ROM dumps. The problem is that the most disassemblers are just dumb tools (the older the worse) - you'll get a lot of night-impossible-to-understand garbage out of them for a couple of reasons, among them: disassemblers cannot fully automatically distinguish between data and code (and Mac ROMs mix them a lot!). This problem has been proven unsolvable, see this discussion on the Halting problem. That's why all modern disassemblers implement various pattern matching based heuristics to identify code and offer interactive features as a last resort so humans can step in and guide the disassembler. IDA is a good example of such a tool. ROM dumps don't contain any human-readable function and variable names. Memory-mapped hardware can vary greatly between machines. One ROM usually has support for a group of machines and contain a lot of machine-dependent code. a whole bunch of old Mac hardware remains fully or partially undocumented. I therefore recommend you to try some sort of dynamic analysis - that is, an interactive debugger with disassembling capability. Because you're targeting 68k ROMs, you can try out MAME/MESS emulator. It's capable of emulation practically every 68k Macintosh including its hardware. The best part - it contains an integrated low-level debugger so you can even set breakpoints in ROM (that's what you cannot do in a real Mac!!!), dump hardware's internal state etc. You'll need a fast modern host computer (Linux, Mac or Windows) but that's the price for its almost luxurious RE features. Just ping me if you need any additional information on MESS (what a stupid name ) and its tools. Cheers Max
  14. Yes, I agree. Mouse movements involve interrupt signals. That's indeed smth you want to check next...
  15. I don't think it's possible. It's true that the ADB as a single-line bus requires precise time slices. But this leads to the following logical conclusion: if this timing is somehow broken, the whole ADB communication will become broken. Any partial failure can only happen after the ADB transceiver/decoder, either in hardware (between the ADB decoder and the CPU) or in software. BTW, the mouse you're using, is it a compatible one? Does it work with the other Q700 board as expected? Do you have an oscilloscope/logic analyzer?
×