Welcome to Xodium Labs, a place where I just...do video thingamabobs. I mostly do retrocomputing stuff, but am known to branch out into other things, like gaming and whatnot. If it's on my mind, good chance it ends up here.
Videos shot on an iPhone 15 Pro Max. Edited on an M1 MacBook Pro.
Restoring one of these tonight. Throwing 2GB of RAM, a 2.2 Ghz processor and some random IDE drive I had laying around. Couldn't find the GeForce4Go with 64Mb VRAM sadly, really rare apparently or an Ultrasharp panel. Going to be a solid Windows XP build, always wanted one in highschool when I was using a Toshiba 486DX2 Satellite T1910 with monochrome screen. These machines were made back in the day when Dells were tanks like Toshibas in the 90s. Shoot it with a shotgun, run it over with an 18 wheeler and leave it out in the rain and the thing will still work. (That's what people were saying about both of them in forums back then)
i love the look of these things but ive only ever drawn them never owned one been trying to find someone to sell one to me but cant find any is a good condition
I can tell you right off that a lot of later 90s games don't run super well on this. Quake 1 will be fine, Quake 3 is dicey as heck due to the lackluster bus speed strangling out higher performing video cards. Diablo runs fine, Diablo II not so much. The 9600's an awesome machine but if you're scoping out machines to acquire from this time and you want something halfway decent at retro games, I'd look toward the beige G3 more than the 9600.
If you’ve been using this workaround for a bit you gotta just trust the process and let it sit for 5-10 minutes. The crash report tool collects logs from your phone and those logs are never cleared, just queued when you kill the crash report tool. So when you finally get a proper sync off it has to go and catch up with *all* the previous logs it never got to collect, and the first proper sync can take a long time, such that it makes you think it’s still broken. At least that’s what happened to me. Decided I’d give it 10 minutes to do something, and sure enough, it did. Took a while, but after that every sync has been fast. (YMMV on this, you may have to let it cook for even longer. I just know for me it was about 10 minutes for it to finally catch up after the 14.4 update)
Gotta love opening some electronics and being able to instantly go "Glad I can instantly identify the failure point, but no way is that working again!" That had to have been an audible failure.
This one hadn’t completely died when I began work on it, it was getting there though. It just required me leaving it plugged in for like 10 minutes before it would turn on and stay on. So maybe there’s hope.
Hey all, glad you found this video helpful! I’m pleased to report that as of Sonoma 14.4 beta 5, it seems to be fixed! It’s going to take a while to transfer the queued diagnostic data, but it does get past “preparing to sync” and finishes a sync without having to kill MDCrashReportTool. Hallelujah!
I no longer own this machine. However I did see the issue with similar era hardware so I can tell you it’s not just the Precision, it’s likely something to do with USB-C alt modes being weird.
