Reveal MusicSTAR MIDI Piano Keyboard
Picked this up at a local tip shop a while ago for cheapcheap and have finally gotten around to checking it out. It's a short MIDI Keyboard from Reveal, model number MKB02. It turns out the company no longer exists; but Creative did try to save them back in the day.
Anyway, the keyboard is really nice. It has the standard IO: Power plug, power switch and MIDI out. On top you'll find buttons to adjust pitch and octaves.
Mine didn't come with an AC adapter, so I purchased the closest 9v 200ma supply I could find.
I was concerned whilst hooking this up as to the polarity of the plug. Usually you get the little symbol somewhere on the unit to dictate where positive is. Every other MIDI device I've seen lately has positive on the outside... but this does seem to be a Japanese thing.
The best way to solve this was to crack the unit open... it's a keyboard nonetheless, so it probably needed an internal clean anyway!
That last photo is of the IO board. The best bit? The power runs in from the DC jack into a friggen bridge rectifier! Why am I so happy/excited about this? It means the polarity doesn't even matter! It more-or-less treats the input as AC and converts it to its own polarity. How good is that!? All devices should do this.
Anyway, the next step was to simply hook it all together into my SC-55. Of course... it just worked perfectly!
Amstrad CPC6128 – Repairing the internal floppy drive
The internal drives in these machines need their own separate 12v supply. It's really quite a strange setup... as it means the power supply needs a male (positive on the inside) 5v DC jack and a female (positive on the outside) DC socket to get the machine up and running.
It all makes sense once you realise that the power was supplied by the monitor that came with the set. And since you don't want want the user to be able to get the plugs in the wrong order, having them oppositely-sexed means that there's only one-way-round that they can be connected... unless you try to connect the devices to themselves?
Anyway... I built the required power setup in the prevous post. This time around I actually have a set of strangely-sized Amstrad 3" floppies to test!
I bit the bullet and just tried to read the disks as soon as I got them... because, hey, sometimes things just work... Of course, no dice; it was either "no disc present" or "failed to read" each time. What next? Time to pull the thing apart! I really should've taken photos when I first did this as the amount of ... insect (I think?) debris inside the machine was intense. There were quite a few of either ant, moth or some other cocooning insect homes installed around the motherboard and, as expected, right inside the floppy chassis too. These things seemed to like to be near the warmer components.
There was also a very thick and protective layer of dust. The entire machine was pulled apart and 24hours were spent cleaning and drying. Again, I should've taken photos... but I was too scared to move everything on to the workbench. I didn't want a biohazard scene to break out. A lot of soap-suds later and the machine came up much nicer, but still had a pretty mottled outer-case.
Anyway, back to the floppy drive again. The discs weren't reading... so I watched them try to work whilst powered up. The head was happily scanning through the tracks, but the disc wasn't spinning. Turned out to be the age-old totally-trashed-drive-belt trick. Actually, when I first opened the case I should've realised that the 10mm x 5mm shards of black plastic (of which the texture should've been rubber) were chunks of the belt. They were actually so solid that I didn't recognise that they could've ever been elastic or soft!
Yup, those chunks above are the remnants of the belt. What to do? You could go on eBay and find a legit belt... or you could dig in your stationary draw for something like this.
And then, well, just undo all the screws on the underside of the drive, disconnect a cable or two and fit a rubber band. Be careful not to damage the band on sharp edges when you install it as you'll just be creating a weak-spot which'll tear when you least expect it.
Put everything back the way you found it and give it a go. I managed to get past the "no disc found" errors... but I still couldn't list a directory structure. I popped the disc back out and wiped down the head (there's a single-sided head in the drive, but the disks are double and need to be flipped) with alcohol wipes. No luck... but something occurred to me; there was a lot of play in the part of plastic that pushed the disc down onto the head... which meant that it wasn't actually properly being pressed down?
I gently pressed down on the metal plate that the disc actually sits on, just to see if there'd be better contact with the head, of which is under the inserted disc. Damn! It worked! I had no idea how to run LOGO3.COM, but the directory was there, printed in all its glory.
So, not enough downward force once the disc is inserted... how to fix? There happens to be a spring on either side of the 'floating' part of the chassis that the disc is supported on. I assumed that these springs were life-expired and weren't pulling down as hard as they should be. Probably explains why the disc doesn't 'click' in when you insert it either... it goes in and floats around.
Thanks to Jaycar, I purchased a box of springs. Actually, further thanks to Jaycar... they were free... as I received an AUD$25.00 giftcard in the mail for christmas due to my shopping last year!
Finding matchingly-sized springs was easy enough and installing them was pretty straight forward... just use tweezers to hook the inner loop.
From here, the 'click' was intense. Powering it all back up got me the following...
Snap. Just works(tm). Now... how do I even run Logo?
Nope... After a little googlin', turns out that it needs to be run from the CPM operating system... which is on the disk? Or something...
Getting somewhere...
And then... I have no idea how to use logo...
But win! I now have both an internal and external drive!
Amstrad CPC6128
A friend had one of these a very long time ago and I couldn't resist the urge to snap one up online when an auction came up! I'm really impressed with the size and design of this unit. It's quite heavy and solidly built. The keys have a nice tactile feel to them also.
The CPC6128 produces video through a 6-pin RGB DIN video port, so we'll need to convert that to something more usable. Thank fully I have a SCART to HDMI converter from the MSX. It also has a standard 3.5mm stereo output jack, so that can be fed into the SCART port also.
The internal floppy drive is non-standard. It requires 3" disks, as compared to a PC that uses 3.5". They're also slightly longer than usual disks. Fortunately Amstrad put an edge-connector on the rear for 'Drive B' which is pin-identical to old 5.25" PC disk drive plugs and I happen to have a ribbon cable that'll work.
Anyway.. let's get this thing powered up and running!
Power
The CPC6128 needs 5v @ 2A and 12v @ 0.5A. You'll also need power for an internal PC floppy drive.. so I've used an internal hard disk power supply splitter for my source. This was chosen as I have an external USB-IDE power supply which has the right power requirements for the whole setup.
I found a DC plug and quickly hooked up the 5v line (red wire!) to see if the Amstrad would power up.
Yosh! We have activity (red light illuminated in test above)! The 12v line is actually for the internal floppy drive, of which I don't have disks for, so I'm not too concerned with it. I proceeded and soldered on a floppy power plug, 5v DC plug and 12v DC socket.
After the final changes, the red power light was still illuminating, so it was now time to convert the video output.
Amstrad RGB to SCART
This looked similar to my MSX machine, but there's only 6 pins instead of 8. I followed the instructions here at CPC Wiki and created a cable with a 6-pin DIN on one end and a SCART plug on the other.
Initially, I used the first wiring diagram at CPC Wiki, but this didn't work! I got a quick view of the CPC, but the image wouldn't last. I then tried the Alternative RGB Wiring with LUM to SYNC and SYNC to 16 and we got a picture! I must admit that my SCART to HDMI convertor is noisy!
Note that the picture would blink and the OSD for my TV kept appearing telling me that HDMI 4 was connected. It turns out (as per the instructions on CPC Wiki) that you need to install a 10uf Capacitor across pins 16 and 18 to rectify this.
This was installed and fitted nicely in the plug-housing. Audio was then run through to a 3.5mm jack for the side connector.
Using a PC floppy drive
You'll find all the information you need here to connect a PC 3.5" drive to the CPC. Finding a ribbon cable will be the hardest part... but luckily I've had a few old machines pass through my pile'o'junk lately and there were enough older-style cables spare. I actually swapped a few cables out from older machines for standard newer floppy cables that don't have the edge-connector as the other machines won't ever need them.
We've already got the power plug from above, so all we need to do now is correctly plug the data cable through. It's as simple as pushing the edge connector socket onto the port at the back and then pluging the IDC header plug into the floppy drive. Make sure to get the cable on the right way... if your machine fails to boot at this point, then swap it around.
Final step... add a jumper wire between pins 33 and 34.
I must note that, when idle, the floppy drive's reading light was always illuminated. It also then illuminated the internal drive's busy light also!
I tried a standard 3.5" HD Disk.. but it hated it..
Floppy Disk Images
This was a little trickier. You'll find CPCDiskXP. The latter is a very power piece of disk writing software specifically for the CPC.
I tried initially to get CPCDiskXP to write a DSK file straight to my USB floppy drive, but it failed. It wanted to install a 3rd party 'direct access' driver and this then told me it wouldn't work with USB floppy drives. Fortunately, you can get around this by converting all images to 'usb floppy compatible' images.
Open CPCDiskXP and click the bottom-middle DSK Editor button. From here, choose 'New'.
You'll now be provided with a selection of floppy image formats. Select the USB Compatible radio and then choose a format from the drop-down that'll fit the contents of the disk in question.
Once done, hit Add Files From Another Dsk. Open the relevant disk image and select everything.
You should now see your new image populated with the files from the source disk.
Hit the Write USB Floppy button up top and make sure USB Floppy Drive is selected.
Make sure you have your drive connected and a valid disk inserted. (I didn't, so the next shot is dark and full of errors.)
And now... test!
Winner.
Other games: Prince of Persia, Stunt Car Racer, TMNT, Chase HQ, Spy vs Spy, Locomotion
Microtek MDC-1 Parallel Port Camera
This thing just looks cool! Advertised as 'really simple to use' since it only needs your parallel port, it's a true-colour 640x480 webcam for the Windows Millenium era. Well, I say Win ME, but I could be wrong... the drivers I found are for ME though, so it definitely hung around.
It has a lengthy cable with a little bit of 'interesting' at the end. Sure, you have the parallel port.. which we're expecting.. but then you have an 'adapter' that has male PS/2 on one end and a female AT keyboard connector on the rear. Wait... so... If my PC has an AT Keyboard port, I'm screwed because this has male PS/2... BUT I can plug my keyboard in to the back of it? Vice-versa, if I only have PS/2 ports, I then need an AT Keyboard? Maybe it came with an extra adapter when you bought it knew. Fortunately, I happened to find one in my box'o'junk!
So, in my AT case, I converted the AT to PS/2, plugged in the webcam and then plugged in ANOTHER AT to PS/2 to connect my keyboard! Hooked together...
We have power!
Software
Thanks to webarchive, the original page for the camera is here. Unfortunately, the snapshot they've taken doesn't include drivers. Regardless of the list of files here, they all seem to be for their scanners. Fortunately, Driverguide has a Windows Millenium Driver for the MDC-1. (Mirrored locally at this URL)
Downloading and installing was simple enough on Windows 98 SE. The software needed a reboot and then I had a program folder with Camera Test in it... sure! Why not?
Nice... it just worked perfectly. Terrible in low-light, but that's to be expected!
For those running open source software, you may be in luck. Is this a Linux Driver? Is this the same one? Maybe this?
Looks like they made sequels: Microtek Eyestar 2? And a USB version also.
Revolution 3D – Ticket To Ride – AGP Graphics Card
I didn't even know this company existed. I've recently acquired a box'o'crap and there was a really strange-looking AGP graphics card in it.
Turns out it's a Number Nine Visual Technology Ticket To Ride Revolution 3D AGP Graphics Card with 8mb of WRAM? There's more information on it here at the VGA Museum. Vogon's Driver Library has the drivers for it for Windows 9x! (Note that they're always in 7-zip format, so get the Windows 9x version of that here.) Here's Wikipedia's data on Number Nine Visual Technologies.
They actually used Beatles lyrics/song-titles for the names of their chipsets/cards. How very random. The card used the IBM RAMDAC and had WRAM ... of which I'm still trying to understand.
Wait... woah... the wayback machine not only has the original Number Nine Technologies website saved, but you can even download the original HawkEye drivers for this card!
So, crap 3D game performance and 'very good' 2D performance/image quality. The card has a 'VGA Enable' on it, so I assume, like early 3dfx cards, you could have this as a secondary and only use it when the application required it. Which is interesting; if the 3D is crap.. then you'd have a second monitor for crap-ness. Instead they supposedly actually were good enough for their 2D!?
Here's a demo of the 3D performance... browse right to the end to see Unreal. Here's a review of it on Tom's Hardware, pitted against a few other cards of its time. All under Windows 95! Shock, it didn't score good at all for 3D... but for 2D it wiped the field.
VC Collection (Russian) has a review of the card. I was happy to see it not coming last! Then I realised that it was being compared against an S3 Virge DX!
Installation
Software was instead pulled from vogons and running setup produced the following...
Wait, what? Setup won't actually install the drivers? It'll just install the control panel? Time to fight through Device Manager...
And, of course, it wouldn't be Windows 98SE without a reboot...
The desktop then rendered beautifully over VGA at 1600x1200.
Games!
Screamer ran very nicely... but this isn't a true 3D game. It has it's own engine and just renders as standard 2D.
Quake 2 was a different story. It ran 'OK' at 320x240. 'Sluggish' at 640x480 and 'Useless' at 800x600.
But that was to be expected as this is not a powerful 3D card!
Wavetables – PRO32AW
Whilst in Thailand I picked up an ISA card with a daughterboard. It was part of a collection of crap from a market where the SIMMs and card were rusting and .. well ... I took a punt!
Turns out the card was an ESS1868, but the daughterboard was an Avance PRO32AW! Talk about lipstick-on-a-pig! I suppose someone wanted the cheapest SB16 experience with a 'better' MIDI quality? It seems this is a clone of a AdMOS Adwave 32, down to just a simple text modification on the PCB. There's a site (Japanese) here that mentions this fact.
The Wavetable module plugs on the header on the sound card and (usually) then disables midi-out on the joystick port.
After a lot of tinkering, I worked out the following. To get a wavetable to work, you need to adjust the IDSP/ADSP jumpers.. where ADSP seems to be the additional DSP card. If you don't have jumpers (The ESS1868 didn't ... and my Vibra 16S/C also didn't), then you'll probably find a new Gameport Joystick detected when Windows loads... unfortunately, this will conflict with your original joystick port.
To correctly install a wavetable under windows, your best option is to entirely delete the soundcard from windows first! Remove everything from device manager (especially the Gameport Joystick!) and then shut the machine down. In this state, the card will be found a-new when windows loads and you shouldn't get resource conflicts. It seems that jumperless sound-cards disable the joystick output when a wavetable is added and then re-route the midi messages to the wavetable. The main confusing part was that the new 'Gameport Joystick' used the exact same addresses and resources as the conflicting port!
After getting it all to work, I managed to pass the audio through my laptop and record the output of each piece of hardware. Here's the source file from Mr Trachtman's Archive.
Here's the basic ESFM Synth:
Here's the Vibra 16 FM Synth:
And then the PRO32AW wavetable:
And then my beautiful Roland Sound Canvas SC-55.
And finally, a friend's Yamaha PSR (Thanks Nathan!)
...Muhahaha...
I found the wavetable sound to be much better than the internal FM synth on the ESS1868. I actually don't mind the wavetable when compared to the SC-55, but was definitely hoping that the SC-55 would come out on top.
I wonder how I replace the soundfonts!?
Cheap Chinese Gotek Floppy Emulator
It was always going to be too good to be true. I was buying other shit on eBay and found that they also had Goteks. For around AUD$12 I couldn't resist.
For those that don't know, the Gotek is a famous device in the Amiga world for emulating the floppy drive. It's the same size as a normal drive and has the same mounting holes. On the front is (usually) a USB slot, LCD display, buttons and activity lights. The goal is to have numbered disk images on your USB key and swap through them like a jukebox.
As soon as I opened my parcel, I realised I'd bought somewhat of a reduced version. No display, no buttons...
Ok, off-the-cuff this would mean the USB key would have to contain a single disk? Not the worst outcome (for the price I paid), but not what I was expecting. I installed the drive in the 386 I was building and it was detected correctly. It all plugged straight in and there was nothing to set. There is a row of jumpers, but I didn't have any supporting documentation and just left them.
On boot, the green LED lit on BIOS post and I let DOS load from the HDD. I rummaged for a small USB key and found a 4gb lying around.
All good so far... dir a:...
Pretty deep error: Sector not found reading Drive A. This usually indicates that the disk isn't partitioned, let alone formatted. Not really unexpected. I tried FDISK, but it doesn't care for floppies. Format wouldn't handle it either.
I dragged the USB back to my laptop and found that it had a single 4gb partition with a TV series on it. Jumping in to Disk Management, I deleted the only partition on the disk. At this point I chose to leave the partition table empty as I couldn't create a 1.44mb partition under Windows 10; the smallest option was 8mb?
Slapping the USB key back in the 386 saw a much better result. Trying to list the directory gave a warmer error (General failure reading drive A) and so I tried formatting it...
Yes sir, I would love to kill 1.44mb of data!
Taking it back to my laptop, I now found that it had a 1.44mb partition. So this can't be done from Disk Management but the firmware on the drive can partition it via its firmware. It was a standard FAT parition, so I copied HWINFO over. I wanted to check system information on the 386 and this application worked in DOS. Taking that back to the machine saw it load off the disk and work seamlessly.
I'll try out writing disk images to the 1.44mb partition tonight...
AnyDrive – Use bigger drives than your BIOS permits!
I've mentioned this use of this Dynamic Drive Overlay software before, but I just want to go over some of its intricacies. Although 90% of it is totally straight forward, there's a few gotchas that you need to be aware of:
- It only works when the MBR has been 'booted' first
This means that, if you have AnyDrive installed and you want to boot a floppy which can see the drive in full, you need to attempt to boot the HDD first, holding shift, to then boot the floppy straight after. - When installing, use the drive number, not letter
I first installed it on drive C instead of drive 0, this caused all sorts of strange issues.
Installation
The best way to do this is to format your 3 DOS 6.22 installation disks and then copy the ANYDRIVE.EXE file over onto the first disk. Boot your machine into DOS and then hit F3 twice to exit out to the command prompt.
From here, run the ANYDRIVE command to get an idea as to your current scenario. You can use ANYDRIVE S to check an installation, if any exists. Note that if you booted straight off your floppy then ANYDRIVE will tell you that it's not correctly loaded. This is perfectly acceptable if you have booted from a floppy and not let the HDD initialise first.
To get an old 840mb HDD running on my 386, I did the following:
- Build 3 DOS 6.22 floppies
- Copy ANYDRIVE.EXE onto the first disk
- Install the HDD into the computer and then boot the first DOS disk
- Hit F3 twice to get out of DOS Setup
- Run ANYDRIVE [DRIVE_NO] [CYLS] [HEADS] [SECT]
(ANYDRIVE 0 1647 16 63 for my Quantum Trailblazer 840AT as C:) - Remove DOS Disk 1 and Reboot
- Hold down LEFT SHIFT to tell ANYDRIVE that you want to boot from a floppy
- Wait for ANYDRIVE floppy prompt and then insert DOS Disk 1 once again
- Install DOS as per usual (it should format to the new size of your disk)
Usage and Boot-time quirks
Once it's installed, and your OS is installed, it's all happy days. Everything is fine until you try to boot from a floppy. As per every old BIOS, boot will be handed to the floppy drive prior to the HDD and therefore the HDD won't be initialised until later. If this happens, then ANYDRIVE wont be initialised correctly and your actual BIOS settings will be used.
This is a problem. As any attempt to then access C:, which has been partitioned and formatted based on ANYDRIVE settings, could cause all sorts of damage as the geometry will be wrong!
To prevent this, make sure your boot disks are ejected and hold shift when your machine starts... you'll instead see the ANYDRIVE boot line and then a prompt to boot from A:. Booting your boot floppy at this point will ensure that any software afterwards sees your ANYDRIVE settings rather than BIOS settings.
I hope this helps anyone trying to get more storage on their older dinosaurs!
MSX – MegaFlashROM SCC+ SD
The MegaFlashROM SCC+ SD, by Manuel Pazos, is the ultimate cartridge for the MSX. I acquired this and my Sony Hit-Bit F1XD a while ago and finally found time to actually use it!
Basic Concept
The cartridge emulates the A: and B: drives on your MSX. This means that previous A: and B: physical drives will be disabled and ROM/DSK files will be used instead. The cartridge has it's own ROM (kernel.dat) which loads you into the Nextor operating system.
From the shop, your cartridge will be ready to go. Grab a small (1gb? 2gb?) microSD card and put it in, then load up your MSX with the cartridge inserted. You should be at the Nextor prompt and you can then follow instructions as per ¡VAPF!'s brilliant tutorial here. You'll end up partitioning and formatting the SD. From there, you can put it into your computer and copy your DSKs and ROMs over.
The cartridge already has firmware in it containing an enhanced version of MSX-DOS bundled with tools for loading disk images. It also includes Multimente, a file browser which makes loading files very easy! You merely have to hit enter on the disk image you wish to load into ROM.
Above you can see the initial A: disk. Hit the L key to switch disks: Type B and press enter. This is now your SD card. Select your ROM image and you'll get the screen below that Nextor has chained it in to the boot process.
Once chained, you can reset the machine and the cartridge will act as if it's the original game cartridge/disk. Reboot away...
You're next reboot will mention that a ROM Disk was found and then you'll get weird things... they're called games:
This game really needs a post to itself... I'll get back to that... meanwhile, here's the intro.
To unload the ROM, you'll need to know the short-cut keys. Note that the commands to unload images are entirely dependent on how you loaded the files in the first place!
Forgetting how to use it
I had received this cartridge quite a while ago. I quickly configured a 32gb MicroSD (I created a 4GB partition on it) and got a game running. I then packed everything away and quickly forgot all the knowledge required to use an MSX computer. I also never learnt correctly how to unload a game which meant, this time around, that I was stuck with a flash cartridge that continued to load a ROM of which I didn't want to play.
Not knowing how to clear it, I chose all the menu options in the 'Recovery' Menu. You can access this menu by holding the up cursor key at boot. It turns out that, when using the MultiMente (we'll talk more about this below), the ROM is actually tied into the Nextor operating system and not the cartridge boot. Clearing the settings in Recovery really just wiped the cartridge when I didn't need to.
At this point I was stuck... I needed to start from scratch and work out how to unload images. Fortunately, the author of the cartridge responded to emails almost instantaneously! Thanks Manuel!
Unloading ROMs and DSKs
There's two ways to load a ROM: You either flashed a ROM image over the entire Cartridge, or you chain-loaded a disk image from Multimente. Both methods have different ways of unloading the images.
If you've overwritten the ROM, you can hold the UP arrow key when booting the machine. Straight after your MSX logo has appeared you should get the recovery menu. From here, you can use F1 to clear the ROM in memory. (F2 and F3 will clear other portions of the cartridge, if you've done that then see below.)
If you've loaded a DSK file from Multimente, then you need to hold down 0 during the boot process. This will skip loading the disk and bring you back to Multimente. You can then stop the disk from chain-loading by deleting NEXT_DSK.DAT from the SD card. You can also do this file when the SD card is in your PC.
Restoring the Flash Cartridge
If you've done unrecoverable damage to the ROM images, then you can restore the whole thing. Chances are good that, with the cartridge inserted, you'll just get the following BASIC prompt...
Copy the Kernel Image to the base folder of your SD card (note that I had issues with a 32gb card and had to use a 1gb card to make this work...) and then choose F4 from the boot menu.
It'll tick through a counter and then bring you back to the menu when done. Reboot your MSX and the cartridge should bring you back to Multimente. If you see your game loading instead, then Nextor is still chain-loading and you'll need to hold down 0 as per above.
Update: It turns out there's a newer version of the Recovery ROM to allow support for 32gb SD Cards. Grab it from here and then flash it by running OPFXSD RECOVERY.ROM /i34 from the Command Line.
Ok, What games should I play?
Bubble Bobble. A-Ressha-De-Ikou. And the rest of them...
MSX – VGA/HDMI Output
My Sony Hit Bit F1-XD either outputs Composite video via standard RCA plugs or 15khz RGB video via an 8-pin DIN cable. Video quality is poor (at best) via Composite on my LCD, so I purchased an RGB to SCART cable from eBay. Due to this being Australia, I also needed to convert this new SCART plug to something more useful.
The first two failures...
I can guarantee that the following two adapters just don't work. They seem to only convert standard composite video from the SCART and disregard the RGB signals. The worst part is that I able to randomly get video from them... Plugging/unplugging and powering-on/powering-off the devices had the MSX display briefly (but never correctly) on my TV and I therefore kept trying to get them going. In the end they are just not the right components.
Note: It seems that, after reading and learning of the GBS8200 below, the CSYNC from these old consoles is 4.6v which is too high for standard converter chipsets. These devices may well work correctly if you put a 680ohm resistor in-line.
If you see anything like these on eBay, then be very careful. Most of them are knock-offs and you can't be sure that they will work with your retro device that outputs RGB.
Just quickly, here's the composite quality...
For all future references, this is what you'll have to deal with on a new TV if you're using the composite input.
Now onto the conversion!
SDV500
This SDV500 adapter found on eBay, although looking frighteningly similar to the first one above, does work. It even mentions in the description that it'll support the 15khz RGB signal that my MSX (and Amiga 1200, now that I think of it) outputs. I asked the seller, prior to purchase, how his product differs from the first one above and he told me that he couldn't guarantee what the one above contains internally; whereas his was guaranteed to work.
It arrived and looked slightly different to my first chinese-knock-off. I hooked it all together and crossed my fingers.
Well ... YES!
Extremely crispy. Acrually, there's a weird 'sparkle' to it where the pixels seem a little noisy... I'm not fussed. The output is great.
The best part about this upscaling is the ability to read filenames in multimente.
GBS8200
Work in progress...
This GBS8200 (also found on eBay) is really meant for arcade machines, but works perfectly for us as well. I purchased a 8-pin DIN plug from Jaycar and made my own RGB->VGA cable to connect everything up.
Ian Stedman has written up a huge post on this device, specifically mentioning how to enhance it. I'll need to mod it to support SCART. An LM1881 can be found on eBay.
I'll get back to this component when I've tested it out.