stardot.org.uk

sweh wrote: ↑

Sun Nov 18, 2018 3:06 pm

Hmm, displays OK for me on Chromium 70; it warns me "connection to this site is not fully secure", but displays the picture.

Version 70.0.3538.102 (Official Build) (64-bit) - Chrome != Chromium it would seem, in that mixed content appears to be blocked by default.

d.

Ah - it's because it's on a non-ssl site. Chrome is refusing to display it. Apologies! As you were

d.

Hi, and welcome to the forum - pretty please can you put the post back as it was originally with the embedded image? It's very confusing when things get deleted, threads no longer make sense.

That's Kingdom which is on the BBC Micro's welcome tape. It runs in mode 7 so won't work on the electron unfortunately.

d.

Very well done

It'll boot if you hold delete, but you'll have to reconfigure it for a hard drive every time you turn it on.

d.

Ah, OK - my bad - I didn't check in detail - I was expecting to see lines all the way down the screen!

d.

Those mode 0 screens look to be pointing to some memory corruption- check this video:

https://www.youtube.com/watch?v=ookuXJd ... e=youtu.be

d.

I've never known the caps in the elk to need replacing.

d.

The metal head cover actually adds some weight to the head so it works properly. I think you need to get it refixed with some new foam (best one to use, I'm not sure)

d.

It's the first link I found - you can look on aliexpress too

d.

You'd have to get a few, but $10 ain't too bad for 100!

https://www.alibaba.com/product-detail/ ... 19499.html#

d.

You're pressing shift/caps lock to turn it on and off, yes?

Assuming you don't have desoldering gear: If you have replacement ICs available, snip the legs with side-cutters close to the body of the chip, then desolder the remaining legs one at a time, whisking them out with tweezers. Finally use desoldering braid/sucker to clean out the holes. If you don't h...

IDE-CF adaptors are passive - they're literally just changing the size of the connector to CF-size (CF is basically an IDE interface). It'll be the specific 32GB card that gets on with the unpatched ADFS and the 16GB one that doesn't. It's very very hit-and-miss, so using the advice in Jon's post: h...

Isn't prime's board at proper vga levels? Not ttl? You'd want no resistors in that case!

Pleased to see that ROOL agree about the Dev tools being an issue at odds with open source development and that something is going to happen! I am watching with interest.

That's floppy mould right there. Couple of methods - split the jacket and wash off in soapy water, let dry, then re-insert. Alternatively q-tip and isopropanol (don't rub too hard! it's a bit more of an aggressive method!)

d.

Press break

d.

Check the disc surfaces - if there's mould, clean them, if they're "gouged" then don't use them as they will defo gunk things up.

d.

I tend to find that a *FX200,2 followed by control break sorts out all but the most daft of memory muckups. That should wipe the ram completely clean on break.

d.

@Tricky - there's a firmware for testing there!

d.

I'd say if you're happy to pay that then that's OK! If you want it now, the only other option is more expensive

d.

It's the fastest "Archimedes" out of the box, although I think the A540/A260 etc could be run with a 33MHz ARM3? RiscPC ran the ARM610 at 33MHz, and the 710 at 40MHz, then the StrongARM was 160MHz+

If you fit the rotary encoder/OLED display to the gotek, you just scroll through and select by name (much as you would on a menu on the beeb) - it depends what you want really. It has the advantage of appearing to the beeb as a proper floppy dive so there are no compatibility issues. I know that mov...

+1 for the gotek + disc interface. Details here:

https://github.com/keirf/FlashFloppy/wiki

Lardo, you can pm him with your email address and communicate that way if you wish!

Hey gang, unfortunately not going to be able to make this now Hopefully someone else can use my space. Real world obligations need attention!

d.

tricky wrote: ↑

Sat Nov 03, 2018 9:21 pm

Have you heard anything about single density meta data access via track 254?

Did you raise it as an issue on github? Might be worth giving it a bump.

Ouch. Feasible I guess? Get that repaired and see if it improves anything. If it doesn't then I'm still thinking it's IC8.

d.