Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 9 10
21
Storage / Re: Adaptec PowerDomain 2940UW files are no longer available :(
« Last post by joevt on May 11, 2024, 07:04:48 PM »
The 'Rom' resource in the v4.1 flasher is 64783 bytes.
There's 'Crc' resource that probably should be modified as well as 'cfrg' resource. Maybe something else too.
Even if you manage to hack the flasher and squeeze in compressed ROM, then there's PowerDomain control panel, that, I think, changes card settings in the ROM and not in some preferences file. It is uncertain whether the CP will play along with compressed ROM.

v4.1 flasher is attached to the 2nd post.
The Rom resources appear to be compressed. There's a mention of lzo compression in the PEF of the datafork so I'll try that.
22
Hardware / Re: AcBel PSU / Quicksilver
« Last post by aBc on May 11, 2024, 06:46:24 PM »
PM sent. ;) 



*Example images. Clickable for larger views.

23
Video Cards, Monitors & Displays / Re: Mac Mini R9200 Fcode
« Last post by joevt on May 11, 2024, 06:27:11 PM »
Hang on.. is that a 'flashrom' build for Mac? Can it be used to dump Mac Mini onboard ROMs? If so, it could be very useful to compare "original" and "silent upgrade" ROMs to figure out what they've screwed improved in graphics department with later one.
Yes and Yes.

https://github.com/joevt/flashrom/blob/bb1afb074b2dc64aeb3bf5667ab05e731db4aaf1/doc/classic_cli_manpage.rst#L309

Try the anymem programmer first. One of the scripts in the zip file uses that method to get the Mac rom.

There's an internal programmer but it hangs my B&W G3 - it might work on later Macs but I haven't tried it. If it works without crashing then compare the result with the anymem result. You probably need to hold the power button at boot until you hear a chime to get into programmer mode.

The anypci programmer can get the option rom from any PCI card that has an option rom. Some PCI cards hide their option rom after boot (may return bad data). If it has an Open Firmware option ROM image, then DumpPCIRom.sh will convert it to Forth and verify the checksum.
24
Hardware / Re: AcBel PSU / Quicksilver
« Last post by gert79 on May 11, 2024, 02:00:13 PM »
Hello everybody

Sorry I couldn't follow the forum for a while due to real life priorities.

I still have all the photos of my QS PSU disassembly but I am a fan of decent resolution images and don't want to go thru the annoying work of resizing them for upload and furthermore have a loss of detail.

Sequence Of Events photos are the only way for me to be able to reassemble the PSU, so I will not post any single image. It is not my way of working.

Factually I was even a bit annoyed that my photos were scales down for "conformity". Imho we live in the age were it does not cost you much to shoot proper photos and also storage is available. You can always delete redundant photos later but you can never generate a missing photo when the work is done. And most of the time disassembly photos are assembly photos if you swap the order ...

I come from control cabinet wiring. Usually I shot thousands of photos each year in the highest resolution that was available on mobile device at the given time.

Currently 4000x3000 is good enough for me, and my intent was to have a photo that clearly shows the Apple Partnumber while being so high res that you could reproduce the PCB from that photo or even reverse engineer the schematics if you have good nerves. I like to think about the future, solve issues before s*it hits the fan.

Furthermore I am a bit stuck since I have to find the caps somewhere in Europe and I don't know with which substance I can replace the white goo, since it is needed to protect against mechanical stress, to prevent unwanted movement of caps closer to heat sources, but also to dampen any kind of coil noise. I had to break the hardened goo in some places and a full clean and re-goo later on has to be done once I have the caps sourced and mounted.

Going a bit OT as usual, I can share my photos via Google photo gallery but I absolutely don't take any responsibility if someone wants to do it like I did.

I don't want to come across as rude or arrogant but too many times in my life people thought I am an eejit and I am tired of it, being treated like that. So everything I explained above is just to add some more depth to my avatar gert79, which is actually a male name in Europe.

@aBc - please send personal message here in the forum and I will prepare the photos for you. Please handle with care like you usually do, I guess you just want to compare types of layouts anyways. If you have any special ideas which components I could replace, as the PSU is still disassembled, I would be very grateful :)
25
Development & Programming / Re: Debugging ATI drivers for Mac Mini
« Last post by ssp3 on May 11, 2024, 09:14:11 AM »
An update.
I now think that ATI Resource Manager also plays a role here. I've changed back to 3.1.6 Resource Manager as an experiment and now the Mini hangs at start-up with previously working f63 ATI driver in a similar way it does with f100 ATI driver and 3.2.1 Resource Manager
26
Video Cards, Monitors & Displays / Re: Mac Mini R9200 Fcode
« Last post by ssp3 on May 11, 2024, 09:08:53 AM »
You can get the Mac mini boot rom using https://forums.macrumors.com/threads/question-how-powerful-of-a-graphics-card-will-work-in-a-beige-power-macintosh-g3.2303689/post-32937887
If you post it here, then I can see if there's fcode for R9200 in there.

Hang on.. is that a 'flashrom' build for Mac? Can it be used to dump Mac Mini onboard ROMs? If so, it could be very useful to compare "original" and "silent upgrade" ROMs to figure out what they've screwed improved in graphics department with later one.
27
Storage / Re: Adaptec PowerDomain 2940UW files are no longer available :(
« Last post by ssp3 on May 11, 2024, 08:58:04 AM »
The 'Rom' resource in the v4.1 flasher is 64783 bytes.
There's 'Crc' resource that probably should be modified as well as 'cfrg' resource. Maybe something else too.
Even if you manage to hack the flasher and squeeze in compressed ROM, then there's PowerDomain control panel, that, I think, changes card settings in the ROM and not in some preferences file. It is uncertain whether the CP will play along with compressed ROM.

v4.1 flasher is attached to the 2nd post.
28
Mac OS 9 on Unsupported Hardware / Re: Mac OS 9 booting on: Mac mini G4
« Last post by gregbuchner on May 11, 2024, 08:45:13 AM »
Good luck. ;)

Thanks!

I did them all, just in case. I have in-game sound now. This is fantastic. So no idea what fixed it, but it is working so I don't care which point did fix it.

29
Storage / Re: Adaptec PowerDomain 2940UW files are no longer available :(
« Last post by joevt on May 10, 2024, 06:20:29 PM »
@ssp3, well I can't help with protection if it is a thing that needs to be considered.

To extract the ndrv PEF from an Open Firmware PCI option ROM, you need to first detokenize the ROM or convert it to Forth, because the ndrv is encoded as a series of hex strings with encode-bytes encode+ fcodes between each string.
The PEF you created has 45302 bytes but the correctly extracted PEF has 43029 bytes.

Only part of a PEF contains compressed data. The 43029 byte PEF can be compressed to 24457 bytes.

The entire ROM is 46080 bytes and can be compressed to 25762 bytes but this is the v2.5 rom (the stripped-down version?) and we want to work with the later unmodified rom.

I don't know about ARM firmware. Maybe there's some documentation somewhere? You can PM me the details.
30
Storage / Re: Adaptec PowerDomain 2940UW files are no longer available :(
« Last post by ssp3 on May 10, 2024, 07:48:38 AM »
joevt, I don't think it is worth it.  ;)
It was looong time ago, but, if I remember correctly, flashing Adaptecs was "one way ticket". Protection or something like that.
Also, it looks to me that the firmware is already compressed. I moved the v2.5 rom part from resources to data, chopped off extras before Joy!peffpwpc, so that certain disassembler could recognize it as pef file, but was greeted with "illegal compressed data" alert. If you're curious, try it for yourself (attached).

* A bit OT. Can you help me with figuring out what kind of checksum method is used in one particular firmware file? It is ARM.
Pages: 1 2 [3] 4 5 6 7 8 9 10