Search results

Made another attempt, this time within the ~/afp-data directory. This time I got "ad[58969] {unix.c:619} (error:AFPDaemon): initgroups(saybur, 1000): Operation not permitted". Adding sudo to each ad command made them complete without error and I did see a burst of activity in the Netatalk log...

I tried this again and unfortunately ran into the same issue. Commands ran on an empty share with dbd -f /srv/netboot ran on it immediately beforehand (lightly edited for brevity): $:/srv/netboot$ 7z x ~/NetBoot.pax $:/srv/netboot$ chmod +x NetBootInstallation $:/srv/netboot$ cd...

@slipperygrey I definitely see the bugginess, ad has some weird behavior. It gets quite unhappy if [Homes] is not defined for one thing. Setting equal permissions on source and destination unfortunately did not work, it emits the following (partial) error for ad cp -R ~/NetBootInstallation...

Thank you! I'll give that a try later today and report back.

I'm trying to add files into a Netatalk share manually via the console. Each has a dot file (._) associated with it. The dot files seem to be well formed, 'addump' shows an AppleDouble format with reasonable looking data to my untrained eye. However, running 'dbd' on the share after the files...

What programming languages (if any) are you familiar with? You'll already have plenty to learn due to the quirky Mac environment so if you have something to build from it will likely make your life easier, and help tailor advice here to your skills.

I have nothing to contribute on the IWM project but thank you for keeping notes there on this and your other projects, they have been super useful!

Yeah I wouldn't be shocked if either the G3 or the cache was being driven too hard too instead of the bus. I'm not sure how common it was for them but this unit is on a green PCB, most of the pictures I've seen of Newer's stuff had black/dark brown soldermask: maybe a cost-reduction step taken...

Okay I think I have this fixed. Tl;dr version is I needed to set DIP switch 3 on the CPU upgrade to ON. To explain here's a long(ish) narrative of the troubleshooting, along with the red herrings I ran into along the way. The "incompatible" message from the driver in my previous post was fixed...

Found it in Gauge PRO. It is active, listed as "Enabled (I/O Incompatible)", which isn't an encouraging way of describing it.

That's a great question; I honestly don't know. I have the MAXpowr 2.0.5 extension installed but some Googling seems to indicate that Newer was addressing that via ROM updates that required an RMA (see here) rather than software. Is there a way to check if this is applied?

I've got a Newer Tech MAXpowr G3 upgrade card (400/200 DT351) on a PowerTower Pro logic board. When verifying checksums on larger DiskCopy self-mounting images, each time the calculation ends with different (and wrong) checksum values. Swapping RAM or loading the .smi files off the network...

Glad this got bumped, I missed it initially. Will be adding this to my systems to zap that prompt. Thank you for putting this together and sharing the source!

Feels like it is very dependent on how the computer was stored. Drives that work fine seem to be more common in computers that are clean, less yellowed, etc... climate controlled storage basically. Most of the drives in systems I've gotten out of sheds/barns/whatever are dead. Obviously there...

Unfortunately I do not have any for sale myself. To be completely candid, I do this kind of hardware tinkering just as a hobby and I have lots of other work/life/project pressures that will cause me to stop working on things for fairly long periods at a time (ask anyone with a scuznet, heh). A...

Support has been added for emulating different varieties of Kensington Turbo Mice, which can now be toggled in the configuration system. This has been letting me use my 5.0 with the Turbo Mouse 4.0 driver. I also fixed up a major bug with the config so it should now actually be usable. Release...

Agreed. Also consider older 4:3 Dell LCDs, they frequently supported sync on green. This list looks pretty comprehensive if you want specific models: http://ps-2.kev009.com/sog/

Development work is slowly continuing. Highlights of recent items: Experimental support added for Kensington Turbo Mouse trackballs, enough for 5.0 (4-button) models to be recognized by Mouse Works 5.7. This is early and there certainly are bugs present, but I figured some users might want to...

What I've got so far can be found here for now. Comments welcome. I'll continue to flesh this out further.

It is! 😁 Plus I figured the community would benefit from other devices being able to emulate these trackballs, the Kensington drivers seem pretty good. Goal was to document well enough it could fit in with the superb ADB protocol documentation @Tashtari has already collected GitHub.