stardot.org.uk

345FE799-745A-4974-B139-3523A63C67A9.jpeg Even the fuse holder is Acorn green! When were these actually sold? I can’t find a mention in any price lists, dealer ads in magazines, or any reviews. The only mention I’ve ever found was in “The Acorn Guide to the Micro” magazine supplement. Edit: Dec ‘82...

It now works! Renaming the existing .dat file to scsi* worked fine, once I'd worked out where I then needed to put it. For some bizarre reason, it wants the scsi*.dat files in \User\*\AppData\Roaming\b-em.exe\scsi, but then creates scsi* files (no extension, should it be .dsc?) in the main B-Em\scsi...

Or you could run the file through: and then it would be suitable for use as a SCSI image and can be used with unpatched ADFS. If it is useful I could look to make the SCSI disc driver handle the IDE format files. My original intention was compatibility with BeebSCSI but it sounds like it would be u...

I *think* that's what I've been doing. I renamed ADFS0.dat to hd4.hdf, tried locating it in B-Em's folder and/or ~\AppData\Roaming\b-em.exe folder. Tried running B-Em with IDE HD selected and ADFS 1.53 loaded (or 1.50, just in case). Still no joy, whereas BeebEm with IDE HD selected and ADFS 1.53 ju...

I have a pair of images of my CF card disc partitions - ADFS0.dat & ADFS1.dat. These read fine in ADFS Explorer, and BeebEm. In B-Em, it's a different story. Best I can get is "Broken Directory" when trying to *MOUNT them. And I'm not too sure it's really reading them, even then. How do I get them t...

If you can find out what CPC’s latest special offer code is (two more digits to go on the end of the order code, so it’s 7 characters rather than 5), it’s always worthwhile trying them on the end of anything you order from CPC - quite often what you want is also on offer but they don’t tell you on t...

I’ve got the same model. Extremely useful and usable, even in my ham-fists.

Don’t mention The Scottish Drive!!!

‘Tis terrible bad luck. A curse on all your data!

Boydie, Not your fault in the case of B-Em. Some random junk (keybaord malfunction) had crept into Makefile.win. I have pushed a change to fix that. I am not sure I have ever compiled Allegro on Windows. I have downloaded release packages from the Allegro GitHub and, when I needed to patch it, cros...

This is turning into quite a voyage of discovery! I'm trying to compile the lastest version of b-em-master from github, on Win10. I've downloaded and installed MinGW (all the Basic Setup), and downloaded and compiled allegro-5.2.2.0. All of which was considerably above my usual skillset, but I think...

But they don’t count (at least not any more)?

I've got an unused Z80B (part no Z8400BB1) from 1990 or thereabouts, if that's any use.

Alternatively, I can always just upload my M5000 and M5000-4 Issue discs, with passcode and rom id (and rom image) when I get time!

Then effort can be focussed on other discs in the series.

108801 in Base 9 converts to &FFFA, so it just works as a 16-bit romid. Presumably, for any given release of issue disc, all the modules on the disc are pre-coded to give the same checksum, so the same passcode will mod all modules in that software release version to the same romid. It may be reason...

That’d be my guess, although I can’t comment on your checksum generator. The only benefit from working out how to back-engineer the passcode from the offset would be the convenience of just putting it into the Issue disc and getting it to make all the correct modules, instead of having to create the...

Both my passcodes are 5-digit numbers. I have codes for M5000 and M5000-4 issue discs, both for the same rom id. These codes are different, which is unsurprising as they will generate different checksums by default, and so will need different offsets to match the rom id. I’d guess this applies to an...

Don’t know if this has been pointed out before, but the ROM ID printed on the ROM (and hence known to the user) is actually in Base 9. This explains how a >16bit number can be stored in two bytes of rom. This may, or may not, help in reverse engineering how the passcode/rom id generator works. Edit:...

16.5 X 9.6 X 3.3 cm

One here, please.

Please could you put me down for:

1 x RGBtoHDMI kit
1 x Analog board kit

Now have a new owner

Or bad home; I’m pretty indifferent.

1 x DS 80T HH, door latch needs repair. Functional status unknown
1 x DS 80T HH, last worked intermittently
1 x PC 1.2M (I think) HH. Never used

Collection only, from Wigan area.

Please add me to the queue, if it’s not too late.

Coincidentally, I’ve been suffering random restarts on my latest project. The DDR4-3200 was overclocking to 3600 (with relaxed timings), and passing Memtest86 absolutely fine, so that couldn’t possibly be the issue, right? The rest of the system hadn’t been altered, but Intel BurnTool was no longer ...

One please

The IMC question was speculative on my part - if the cpu has a slightly weak/elderly integrated memory controller it may be okay for two sticks but unstable with four. Checking the forums out, this can indeed be an issue, more so if the ram is being overclocked, but also at stock. What is your cpu? ...

Try 24hrs Prime95 on Blend? Since you don’t know which (if any) component is flakey, Blend will test all of them. If it throws up errors, the culprit FFT size will help track down if it’s memory/cpu etc... Then try individual sticks if it looks like memory. How long did you run memtest for (and I pr...

May be as well to check the voltage supplied to the memory as well. If your bios is selecting that from the new memory’s profile as well, and it’s only asking for 1.35V then the old stuff won’t be happy...

Just to muddy the waters slightly... Back in the early 90s, I managed to get hold of several System 3s and 8-10 Atoms that the Experimental Psychology Dept in Cambridge didn’t want any more. These were all just bog-standard machines, not custom oem jobs. I remember one of them stood out because it h...

Try googling “trigger finger” and “tendon nodules” to see if they match your symptoms.