Rolls-Royce don't sell many cars either, but they (usually!) make a profit.

There's a market out there for people who want the best, no matter what the cost... and that includes the X1000.

Welcome to the fold!
The Amiga community isn't actually as divided as it seems - most of us only wish well to the other flavours. The problem is that the black sheep are the most vocal, so it seems a lot worse than it is.

Sure you'll enjoy your Amiga when you get one; you'll find a lot of helpful and knowledgable people on this site particularly!

I noticed looking at the Slashdot link there was a lot of disinformation being spread about. I think people are confusing Hyperion with our dear friends C=USA, as they are saying things like "it'll end up a re-badged Dell", when we know that's impossible.

That said, some of the people there are just pure bona-fide morons, especially the people who seem to think that just because they've stopped using AmigaOS, it should somehow deserve to die entirely and that Hyperion are some kind of criminal organisation for keeping it alive.

I think things will change when the netbook actually comes out though... but at the moment people outside the community associate Amiga with Commodore (USA) and are fed up of vapourware and empty announcements.

I used Envoy for a while. I had my A1500 sharing out files to my A1200 and A600. It worked quite well but I don't think Envoy plays nicely with other TCP/IP stacks. I should look into it again...!

It's already there :)

I think I accidentally didn't re-merge the PegII fix so if you're using a PegII you either need to use the old catweasel.device before using the new (just once), or stick to the old for now. Will fix it later tonight!

Also just made some changes to the 3" drive code as my EME-156 wasn't playing nicely. Strange things, them Amstrad drives...

I don't think I've changed anything very fundamental but feel free to send me sashimi logs if you have trouble!

Look! An update has appeared on http://www.retroreview.com/iang/Catweasel/ !

Just the AmigaOS version, at the moment, this has changes for the disk detection code. I've juggled it around a lot so I have no idea if I've broken anything, so my old version is still there, but it seems ok.

If you have Update 3 and mount TD0: in your DEVS:DOSdrivers/ this version will fix your black screen on boot-up!

Please send me bug-reports (in my sig!) :)

Welcome to the site. :)
You've come to the right place for AOS 4 stuff!

Not entirely true - I do have USB sound on my OS 4 machine....

.. but that's because it's using a Deneb and the 3.x drivers.

I need sound on my Sam440 though, so it has to be 3.3V PCI. Currently looking at M-Audio Audiophile cards like the 24/96 or the 192...

Hi everybody,

while trying to hear my record over the jet-engine noise that is my PC (that I use for recording), I once again pondered the idea of using my normally unused Sam440ep.

Having wired up the front audio jumper to the headphone socket (as there's no line-in on the Sam itself and the case had no line-in, only mic which is mono), I managed to record a track (Dr. Hook, if anyone's interested).

It did seem to be very quiet though and there was a notable DC offset in the track when I looked at it in Audacity. I need something a bit better, I think, than the on-board Sam chipset.
I tried the Audigy2 Platinum that normally lives in my PC too but it didn't fit the case so that was no good.

What's the best sound card (bang/buck) I can get for recording under AmigaOS 4? Any suggestions please? Thanks!

I got it recording but it clicks between buffers. Same code works fine in AROS, so I wonder if OS4 isn't fast enough to cope, or am I doing something wrong....

Need to look into it more!

I think I sorted the problem.

Under AROS and even I think AmigaOS with a PCI card, AHI always returned the same buffer size, which was a factor of the max buffer size sent to AHI. With the USB one, the size of each chunk varied so I was over-running the end of my buffer.

Now I fixed that, the only problem was that I had to whack up the size of the buffer in my code otherwise I got a lot of clicking. I got it to record seemingly ok, though. :) Not bad for a £5 sound card on a 17 year old machine, really.

Hi people,

I'm puzzled... I've just ported my QuickRecord program to OS4 to test on my A4000 with a USB audio stick.
I'm getting a crash in my code and I think it's because ahirm_length is 30 - this seems stupidly small - and it's running too slowly in the callback, meaning the buffer gets too big and then splat.

Is there a way to increase the buffer size recorded before the callback is called? I don't care too much about latency.

Thanks for any help!

It's an IDCMP_RAWKEY message - nothing to do with Atari800 itself.

It's either a problem in Atari800's GUI, or a problem with AmigaOS 4.1 on the Peg2. If it's the former, then for some reason it keeps sending itself this message with a code of 0xFF, but I don't see why it would do that. If it's the latter, goodness knows what else it could affect.

I've told Dr. Hirudo of this and he's going to look into improving it.

I think I tracked down the error.

The keyboard handling loop is receiving many IDCMP_RAWKEY pressed with a key code of $FF. Filtering out those keycodes seems to help.
No idea why this happens though yet...

I've been using Atari800Win to test my tape images.. all is fine there...

Thanks Dax,

That's the version I tried though - I tried the Dr. Hirudo version and the OS4 depot version and they're the same codebase - and neither work...

Are we without a working 8-bit Atari emulator then..?

Hi people,

As part of my continuing work on UberCassette, I've managed to make a .cas image of an Atari 800 tape. However, looking for Atari800 for AmigaOS reveals a very old (2004) version 2.3.0 on OS4Depot. Googling it finds even older versions.

I tried running it but it doesn't work in BASIC (and probably not anywhere else, but it's BASIC I need). I'm not sure if it's running horrendously slowly or whether it's the input that's not getting through (though it certainly crippled OWB so it's probably some kind of hiccup in running).

System is an OS 4.1 Pegasos2 G3.

Anybody have any advice?

IMHO...

having a single key-press which closes your program without confirmation is brain-dead, and shows that the program has never been used properly. Bad, bad, bad, bad, bad. Especially in an app like Calculator which looks like any other calculator app, except other apps use Esc to clear the window (a very common command), so anyone using more than just AmigaOS Calculator will get very frustrated very quickly.

Multiview and things aren't too bad - they're viewers. There's no work to lose. But in any app which maintains a state which would be lost by quitting, the app should never quit on a single keypress.

Rant over. :)