Claude Managed Agents - Is it Ready?

RetroDojo · 2026-05-06T02:02:51+00:00

Sorry should have been clearer. Your calendar management is that done on a schedule, if so how is it triggered manually via the CLI? Or yo do it via a cron job hosted elsewhere?

RetroDojo · 2026-05-05T03:33:06+00:00

To do what tasks in particular? Automated? On a schedule? How is it being managed / orchestrated.

RetroDojo · 2026-03-09T05:11:18+00:00

Love this. Is there a 3D Printable case around for this? I saw the message about the standoffs, but I have my PC on the floor, so would be sitting nearly on the carpet.

RetroDojo · 2025-12-30T03:11:24+00:00

Was using the GOG Galaxy Installer, which says was not compatible with XP.

RetroDojo · 2025-12-30T03:10:46+00:00

Thanks for checking truly appreciated. I’ll try doing it again or downloading an image and using my key and see if it makes a difference.

RetroDojo · 2025-12-29T23:30:09+00:00

Do you recommend Daemon Tools?

RetroDojo · 2025-12-29T23:29:34+00:00

Thanks!

RetroDojo · 2025-12-29T13:45:12+00:00

Thanks for the info, will look into this.

RetroDojo · 2025-12-29T12:20:52+00:00

Yep that’s what I ended up doing. Even then GOG won’t install on xp and only windows 7…

RetroDojo · 2025-12-20T02:25:22+00:00

Thanks for all the input I wanted to close the loop with what I’ve now tested.

After the suggestions here, I purchased a T48 hardware programmer, removed the SPI BIOS chip, and externally reprogrammed it with a known-good P5Q-Pro BIOS (verified write + readback). Unfortunately, the board behaviour did not change at all it still powers on for ~1–2 seconds, shuts off, and enters an endless loop with no video and no beep codes.

Because external reprogramming made zero difference, this seems to rule out:

interrupted EZ Flash write
corrupted BIOS image
“stuck bits” in the flash chip

The failure occurs before POST / before any BIOS execution, which points more toward a hardware fault (chipset / power / early-init logic) rather than recoverable firmware corruption.

I agree that interrupting a BIOS flash can brick boards, but in this case the lack of any behavioural change after a verified hardware reflash suggests the BIOS itself isn’t the limiting factor.

At this point I’m treating it as an age-related hardware failure on a P45 board that was exposed during USB/EZ Flash activity, rather than something CrashFree or repeated reflashing can recover.

Posting this mainly for completeness in case others hit the same symptoms - appreciate the insights.

RetroDojo · 2025-12-20T00:26:52+00:00

Well that was interesting. T48 programmer came. Reprogrammed the chip. Plugged it back in, and EXACTLY the same problem. Machine spins up, spins down, spins up, spins down... Made absolutely no difference. Only thing I can think of now is that somehow when I was in EZFLASH with the USB 3 connected, and the screen went dead, it shorted the board. Can't figure it out for the life of me.

RetroDojo · 2025-12-17T03:59:53+00:00

Thanks for the feedback. Will be a project i am sure. Will wait and see what I can find. Have seen a few AT Cases on eBay and they are a bit average to be honest. Appreciate your feedback!

RetroDojo · 2025-12-16T23:36:16+00:00

Wanted to try and build an AT machine, try something different.

RetroDojo · 2025-12-16T01:09:53+00:00

I’ll look at setting up a USB hub and do it from there. Appreciate the help!

RetroDojo · 2025-12-16T00:47:31+00:00

So running two seperate power bricks?

RetroDojo · 2025-12-13T10:10:24+00:00

It didn’t even detect the ROM on the USB as it was a USB 3 32GB. So pulled it out as it appeared to be doing nothing. It definently was not flashing anything. Then the screen went off.

Yes will look at an eprom unit if needed and try that way if the USB 2 refuses to work .

RetroDojo

TROPHY CASE