Atari-Forum

I'm here.

I could use another pair of hands, but everytime that happens, it ends up sucking more of my time.

I'll get there.

Still here, and getting there.....

I'd probably let mine go, it's fully cased with the grey colour. What did the last one go for ?

Soon, is all I can say

Should be fine. Need to solder the MonSTer on top of the 68000, and potentially remove the metal sheilding or cut it.

It's running 1.03c right ?

If it's running 2.x then there are issues with that on various Falcons.

Yes, nice job. Be interesting to see how some of the overscan demos work with this.

I have two, need to dig them out.

The MonSTer LED just comes from the IDE pins, so it sounds like there's something wrong on your IDE-CF interface.

The only reason the blitter would be greyed out is if you removed the jumper on the MonSTer board across the BLITTER pins.

pin20 isn't used on the MonSTer or connected, so it can't affect the CF cards LED.

BigDOS only allows FAT16 partitions to be used, these are not TOS partitions. You need to create the type field as $06 to use them with BigDOS, but they can be up to 2GB. BigDOS also disables <32MB partitions, so make sure any partition is bigger than that. Well, it's certainly good that my BigDOS ...

BigDOS only allows FAT16 partitions to be used, these are not TOS partitions.

You need to create the type field as $06 to use them with BigDOS, but they can be up to 2GB.

BigDOS also disables <32MB partitions, so make sure any partition is bigger than that.

If you can see the device then it should work. Therefore it should be 1.1 compatible.

How are you powering the Unicorn, and can you check you are getting 5V to it.

What version of HDDRUTIL ?

If the Unicorn doesn't see the USB drive, then there's either something wrong with the USB flash drive or the Unicorn itself. Have you tried another USB flash drive ? or even a USB mouse ? Just something USB ? Just load USB.PRG and UNICORN.PRG and see if it scans anything on the bus to confirm that...

Fortunately, the offending instruction is 0x1686 or MOVE.B D6,(A3), a rare instruction that occurs only once in the Unicorn drivers, more precisely in USB.PRG. So I guess this is the location of the crash. At this location we have ... [...] move.w #$48,-(sp) ; Malloc [...] However, it is not normal...

If the Unicorn doesn't see the USB drive, then there's either something wrong with the USB flash drive or the Unicorn itself. Have you tried another USB flash drive ? or even a USB mouse ? Just something USB ? Just load USB.PRG and UNICORN.PRG and see if it scans anything on the bus to confirm that ...

Fujiyama wrote: EDIT: it looks like I might have mixed up the wire colours. I'm doing a double-check now, but feel free to comment the above.

Yes, it looks like your header connector is completely reversed, making all the connections wrong. Please double check them.

I do have another problem (though this may be at my own ignorance): when I run M_ALTRAM.PRG from the AUTO folder I get these strange black boxes replacing icons and other window elements. This happens whenever I select one of the memory options (2 MB ALT-RAM, 4 MB ALT-RAM or 6 MB ALT-RAM) then rebo...

Sorry, no idea. It's not my board so I'm not sure what those pins are for.

Yes.

Fujiyama wrote: There was some talk about USB up-/downstream a while back, and incompatibilities with certain USB hubs. Not sure about the details, but this was straightened out with later versions of the Unicorn which had some additional circuitry to resolve this, wasn't it?

Correct.

Yes, I've used a USB DVD drive myself with Anodyne Softwares ExtenDOS v4 software.

Powered hub is better. And multiple USB devices can be used just fine. There is no keyboard driver.