Atari-Forum

Hello,

the MicroCosmos devices (ACSI only, no floppy emulation) are now available in store...
http://joo.kie.sk/cosmosex/shop

Jookie

Cyprian wrote:what about skipping screen casting and just create dedicated VDI drivers for Cosmo?

Yes, that could be done, although I agree with what MiKRO said - the ACSI has its limits, and doing lot of graphics through it will slow down hard drive stuff...

dbsys wrote:So, Cosmos EX will simply ignore the +12 volts on the connector?

I just do not want to blow it...

Yeah, it ignores the +12V line - it's not connected in CosmosEx...

Jookie

Hello Gunstick, this is weird, there wasn't any change related to Samba sharing in the last few months... Things you could try: - try to share the the folder from a different machine (if it's now shared from linux, try it from windows) - connect to raspberry through ssh, try to mount your samba fold...

Hello Andrew, the current screencast supports the ST(e) resolutions, so if you're looking into showing just native resolution, it's already there. If you would like to have support for higher resolutions / more colors in Mega STE, it could be done, but even with native resolution the screencast slow...

Main app – 2017-04-13 - some fixes to CE STiNG – by nanard - code refactoring (clean up, less polling, …) – by nanard - fix / improvement for longer transfers than 1 MB - extended key joystick functionality – see this for info: http://joo.kie.sk/?page_id=793 — by mikro - toggle USB Keyboard exclusi...

Hello Daniel, sorry for late reply and inactivity on this, but I got somehow stuck... I wanted to fix a related issue (the RAW drives and large transfer) and got stuck there too... So I wanted to add a simple feature to make myself happy with a little success, and I failed there too. I keep failing ...

If you're able to log in (by using USB keyboard), then you should definitely try running that update command: /ce/ce_update.sh That should download the update from internet, flash the chips, unpack the newest app, and hopefully get it back to life. If you are unsure on how it will end, or if there a...

ccarl84 wrote:Why not ?

I'm not saying it's not possible or won't be done, I've just said that the current HW (without modifications) has no way to output sound

ccarl84 wrote:Afterwards, Alexh's idea is interesting.

Yeah, +1 from me on that

anodyne , thank you for the info, good to know! The maximum transfer size of SCSI READ(10) and WRITE(10) is 65535 sectors (2 bytes / 1 word), so that's 32 MB. So even if the TT DMA could do it, the transfers shouldn't be longer than that... dhedberg , I'm looking at the same issue with RAW (USB) dr...

Interesting idea I wanted to add a beeper, but I considered it to be not very useful, so I didn't add it there.

The floppy sound could be somehow added, but you would have to add a speaker somewhere (to Raspberry?), because currently there's no sound output device from CosmosEx....

The full (ACSI / SCSI) version will be in stock in autumn, the micro version (ACSI only, cheaper), will be available in 2 months...

I saw it, and I like it

Ever thought of making an IDE / CosmosEx Yes, but it's way to much work to be worth it - it would need a completely different firmware for chips, lot of development on the Atari driver side... It would take 6 to 12 months of development, which I consider too much for this, as most people are fine w...

what about using a SCSI-2 connector, they are smaller : http://www.retrotechnology.com/herbs_st ... drives.jpg Yes, but they are also too expensive (like 5 or 8 euro per piece) and they probably still wouldn't fit. The MicroCosmos will be of size of Raspberry Pi, longer sides are taken by other con...

ACSI or ACSI/SCSI-Version? ACSI only... There's no place for the huge 50 pin SCSI connector there... There could be an extension board which would add that SCSI connector, but I'm not sure where it would be placed (next to it, on table?) as it wouldn't be a single nice PCB with the rest of the devi...

Yes, and smaller dimensions, thus smaller case which wouldn't be so easy to mount inside of ST, but it's smaller and cheaper

Hello ccarl84, sorry for not replying for a while, I've been busy with other things (other bugs and sick kids at home). At this moment I can't tell why it works fine with your STE but not with MSTE - there might be some different signal level on some pin of one machine compared to the other machine,...

Just to keep you updated - I didn't manage to do much during the last week - got both kids sick, now they are getting better. Uwe responded quickly (you know, no kids ;) ), it seems that everything is fine from his side. I don't see the obvious issue, I have to think this through, so in the mean tim...

From the survey: MicroCosmos: HDD and IKBD emulator This will be a smaller and cheaper version of CosmosEx, without floppy emulation. If you don't connect Raspberry Pi to it, it will work as HDD emulator (using SD card) - like SatanDisk (but faster), or like UltraSatan (but cheaper). Good for every ...

With such a solution you don't need a web-browser on the ST at all. Just some advanced image viewer. Yes... This is one of the nice projects for CosmosEx - there's no assembler programming required, very little Atari programming, data transfer between Atari and Raspberry Pi is there, the html and i...

How much ST-RAM does your TT have? The TT has 4 MB ST RAM, and 16 MB TT RAM. The TT RAM shouldn't influence this (even in Falcon), because if I remember correctly, DMA transfers can't be done to TT RAM, so only ST RAM is used for DMA transfers and thus hard disk transfers. I've extended the timeout...

OK, got something... On my Falcon, with 14 MB of ST-RAM, when the sectors of the file being read are nicelly one after another, the HDDRIVER issues a large read - 28144 sectors - 13.7 MB of data. That can no way fit in the 3 second timeout. Now the question is: - does HDDRIVER make a large, but inte...

I think this device has great potential and it's amazing work that you are doing with it but I vote that you just make it a bit more reliable first with the features it currently has. You don't have to vote for that, making it more stable & reliable is an everlasting task - we're trying to fix ...

What's the speed of the TT SCSI interface compared to the F030? If data is transferred a lot faster on the Falcon that could explain the results. According to this: http://www.atari-wiki.com/?title=ACSI,_SCSI_and_IDE It's 4MB/s on TT, and 2 MB/s on Falcon. But that's the maximum the computer can go...