Crashed

Crashed

@crashedfiesta.bsky.social

Vintage computer nut. Biased towards Amiga. https://crashedfiesta.blogspot.com

119 followers187 following311 posts

It's Sunday. Don't think about work tomorrow. Think about an ancient computer that no-one has ever heard of... unless you follow me on BlueSky in which case you will have heard of it because I won't stop banging on about it. crashedfiesta.blogspot.com/2026/10/if-t...

crashedfiesta.blogspot.comIf a Torch beeps in a forest, does it make a sound? - Torch Emulator Part 4So, the Torch emulator is ticking along nicely. But silently. It's fair to say that the Torch is not exactly endowed with an extensive sound...

Completely reworked the terminal 'wrapper' on the Torch. It's more 'front end' now as it runs a single sh instance with additional functionality rather than running a new sh instance for every command (hey, I'm not a professional developer - it seemed a good idea at the time!). #torchtriplex

Torch Triple X emulator update. I've been working hard on the wrapper for the 'sh' terminal. Added 100 entry history per user, lines can now edited, exe and folders are identified by * and / respectively, prompt includes username & current folder. ๐Ÿ˜ All that for a user base of 1 (maybe 2).

How big is big enough? Managed to make a 1gb Torch Triplex disk image. Not sure I can go much bigger with the filesystem limitations of the day... ๐Ÿ˜†

Must be getting old. The only person who I have heard of in the Strictly lineup this year is Delta Goodrem. Not that I follow it. It's just the first sign that winter is coming (and the 'C' word).

FFS Google. I only asked 'who said that they were standing on the shoulders of giants?'. Apparently you think that Isaac Newton, who famously lived in the 1700's and died in 1727, sent a letter to his buddy in 1975. JFC.

And for my next trick (or descent into insanity), a text based web browser on the Torch Triple X emulator. Ta-daa! It's barely more than a 'get html' function at the moment but I'm learning lots. And it's something to do as I wait for my new man cave (shed) to be installed..

It's Monday. The summer is almost over. You know what you need. A superficial description of of an ancient Unix PC emulator, and how I've fiddled with it after standing on the shoulders of the most excellent person who actually originally wrote it. crashedfiesta.blogspot.com/2026/08/when...

crashedfiesta.blogspot.comWhen is a Torch not a Torch? When it's an emulator....The old hardware of the Torch Triple X is proving to be a little bit bothersome (it's a right old pain the rear) and I've made little progre...

So, Mrs Crashed's phone just emitted the national alert tones with a warning about the high risk of fire, given the current weather. My Motorola Edge 50 Pro was silent, clearly content to let me burn..... ๐Ÿ˜ฌ๐Ÿ˜„

Been a bit quiet as we're on the move from Crashed Towers to Crashed Twouptwodown and discovering that 18 years in one location is a great way to accumulate enough pointless crap (i.e. non-retro computing related) to fill a small stadium. Warm, dry storage has been procured for the important stuff.

I have survived another orbit of the local star. To celebrate here's a list of stuff I've done to the Torch emulator: -vi now works(ish) -serial no. retained after first key disk boot -aspect ratio corrected -floppy .img support -improved terminal (tsh) -boot sequence colours corrected cont..

cont... -code compiles in Linux or Windows -time date picked up from local host (not y2k compliant so year set to 1998 for 2026) Still to do: -palette controls not working -'make' crashes every time

More fiddling with the Torch Emulator. Now it's just like the real thing! Well, booting up looks right now anyway. ๐Ÿ˜ #torchtriplex #stillnotfixedtherealone

A great evening writing a wrapper for the very basic Unix terminal on the Torch emulator. Added some history functionality (previous commands etc) and managed to get su working via a tiny script (called tsu), and cd works properly too. It behaves a lot more like bash but isn't actually... ๐Ÿ˜

I got a PS4 on day 1. I asked the man in the Sony Centre when I pre-ordered if they were doing a midnight launch. "Good god, no." came the unguarded reply. ๐Ÿ˜‚ Anyway, I skipped PS5 for reasons. But I won't be doing PS6 with no disc drive. Licensing is not owning. See Sony/StudioCanal for details.

Checkup on the Cifer to make sure he's still working before I pop him into storage for a little while. I hope the Retro Overlords will forgive my use of hot glue to stick the front panel in. I spent hours 3D printing it but got the lugs in the wrong place and I was desperate. Don't judge me.

So. Good news and bad news. Good news - new limpet works and I managed to boot all the way in. Wa-hoo! ๐Ÿ˜๐Ÿฅณ Bad news - my motherboard requires a startlingly big concave bend in it to work.... ๐Ÿ˜ฌ By chance I found if I wedged something under the right side it would boot. A weird mechanical bug....

Torch Triplex Limpet board looks great. And I found the second error. I missed a whole track that should link all the write enable lines on the DRAM. Oops. Bodge wire installed but it still doesn't work. ๐Ÿ™

I might've caught the coding bug for vintage computers... After several hours I have managed to get 'vi' working on the Torch Triple X emulator. The stack is too small for when vi starts (something funky happens) so by making it bigger, vi then works. Nice. Next stop, proper floppy support.

Managed to hand one of these to @binarydinosaurs.co.uk as the only other person I know in the country with a Torch Triple X. ๐Ÿ˜ One of the four left is about to start receiving capacitors and sockets.... ๐Ÿ™‚ ...and I found the first error. Oops. Capacitor C45 has both legs against ground. Darnit.

Away from Crashed Towers for a few days so I can't connect to my pi-hole. The internet is a completely unusable pile of smelly brown stuff these days, isn't it?

It's official. My Torch Triple X is no more. There is some fault with the limpet board which I can't track down. All RAM is OK. All tracks are OK (or repaired). I suspect a failure of one of the PAL chips which did get quite warm. Ultimate unobtanium. Without it, the Torch won't boot. Arse. ๐Ÿ˜ข

Oh. My. Gosh. The Torch is playing with me now. I had about six hours of flawless operation. Then I started compiling uemacs code. Two minutes later, kernel panic with memory management error. And I'm back to where it was before. At startup, a single flash from the limpet and then nothing. Gahh!

Annnd were back in the room. I have spent hours going over this bloody computer. Beeped out every trace on mobo and limpet. Nothing missing. Then I moved the black plastic down a bit on the new long pins to keep them more together. Booted first time. ๐Ÿ™„ That bloody connector... ๐Ÿคฌ But, yay! ๐Ÿ˜

F*CK. F*CK. F*CK. F*CK. F*CK. Torch is dead. After battling intermittent RAM issues for months I think the Limpet board has died. My last resort is to de-socket the motherboard RAM and see if it's actually the sockets causing issues there. #bugger

Couldn't work out why I couldn't mount the disk image on the Gotek once I'd formatted it. I am an idiot. Should've remembered that 'format' is low-level and I still needed to 'mkfs'. Doh! But now I can copy files and create disk images til the cows come home. Moo.

Uemacs porting efforts to the Torch are on hold due to a persistent RAM fault. I am removing the sockets I installed on the limpet and putting the chips directly on the board as they're a liability (the sockets). Things like this don't help though...

Darnit. I'm 99% certain the Torch issue is the limpet connector. The question is, do I persevere with the constant kernel panics and crashes or do I install a fixed arrangement that is permanent? ๐Ÿค” It would make maintenance a pain in the arse. But, if I'm right, it would solve the RAM issue.

Found the cause of the memory issue In the Torch (more or less). I'd used multiple turned pin sockets stacked to create a connector to the limpet. But with the motherboard and limpet removed it was obvious I'd used one too many. With it removed, the Torch boots far more reliably...not 100% though.