Jump to content

mikro

Members
  • Content Count

    97
  • Joined

  • Last visited

Community Reputation

27 Excellent

About mikro

  • Rank
    Star Raider

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Košice / Slovakia

Recent Profile Visitors

4,293 profile views
  1. flashjazzcat, I didn't mean to imply that there is something wrong with your firmware. I just wanted to mention it, in case someone else falls into the same issue. Which seems not reproducible anyway (this leaves me really wondering how on earth is that possible - the only explanation I have is that 2016 FW and/or SDX had some feature missing which prevented SDX from booting with active QMEG). My non-standard approach was due to the fact that I have QMEG active all the time and since there wasn't any warning about it in the manual, I expected it work out of the box, or, to be more precise, be independent on the OS installed. Thank you for your test and detailed response, I really admire what you have done with this beautiful hardware addon.
  2. Actually, my desire to use QMEG is maybe totally anecdotal - I simple love its ability to recover from any state (SELECT+RESET) but sure, this is what U1MB BIOS offers as well (HELP+RESET). Then there's the inverted BASIC option (IIRC this is offered by U1MB BIOS as well) and then finally, its ability to boot from different disk drives with one (ok, two) key strokes. Back in the day I loved to use its built-in ram disk for disk copying as well as its ability to boot from such ramdisk as with normal disk drive. Oh yes, and the built-in monitor for software inspection. So it can be still pretty useful, even with its 256K limitation.
  3. Well, it does start with classic Atari ROM, right? So when QMEG offers its replacement, I would assume it still boots. To be honest, I don't know how SDX actually boots, is it some form of cartridge emulation or RAM disk? To me, as an average Atari user, it was very confusing -- I booted the ATR, saw "Error: no DOS" and that was it. So I opened the manual and it said "Enable SDX and it will boot", so I did and it didn't work. I guess I can create an ATR with QMEG on it somehow, just wanted to make sure I'm not going to do something more complicated than needed.
  4. Hi, I apologise in advance if this has been discussed or even announced before but nowadays I'm mostly a passive 8-bit user so I don't follow all the news so closely. Basically - I had the U1MB from Lotharek with firmware from 2016. Worked great, had a lot of fun with it. Today I wanted to update it (saw the news somewhere). Everything went smoothly except two QMEG-related issues: firmware.atr wont boot with QMEG enabled, regardless of SpartaDOX X option. It isn't mentioned anywhere, I think it should be. since I had so old firmware flashed, it seemed like a good idea to reflash everything (it's nice to have SDX from 2020!) however ... I lost my QMEG! For a world I can't remember how it got there in the first place. Was it default and changed sometime during the past years? (I guess replaced by Altirra OS?) Is there some ATR image with all the OSes available? firmware.atr focuses only on SDX versions as far as I can see.
  5. Hi guys, would be someone interested? It's my oldest MegaSTE, honestly I don't remember what happened to it, just one day around 2000 I'd put it into box and never opened again. It doesn't boot (just white screen) but it does boot into diagnostic cartridge -- keyboard works, display works, ROM reads OK, ... so there's a good chance you can repair it. Blitter tests hang so this could be a good hint where to start. SCSI adaptor included, RAM (4 MB) included, IF I find the original TOS 2.05 GER ROMs, I will include them too. NOT included: PSU, floppy drive, case, keyboard. Actually, if you desperately want keyboard, I can offer you some (I have spare both MegaST and MegaSTE ones). Price: 75 EUR + shipping, if you are someone contributing to the scene, I'll let it just for the shipping. Located in Slovakia, Europe.
  6. One of the reasons why SIO2USB works so nice is that there is only one I/O connector. But on ST/Falcon you have at least two: floppy and ACSI and/or SCSI and/or IDE. So in that sense CosmosEx is really the closest because it handles both in one device. It's quite easy to actually make a RPi application similar to RespeQt running on CE itself or even to make a RespeQt-like application for PC which communicates with the CE and selects floppy images. If you were after standalone project, I guess you could go after pure USB -> floppy transfer, reuse HxC's firmware (on the fly conversion to streaming-friendly HFE format) and just output the data similarly as Gotek or HxC do. EDIT: Oh I see you have specifically asked about ACSI. In that case it should be still possible with USB 2.0+ but you have to ask yourself what would you expect from such software? Hard drive images? Emulated hard disk on given folder? In that way CosmosEx is really the closest. If I were to do it, I wouldn't bother with HD emulation (like CE or Hatari does) but created a hd image in memory and streamed that directly to USB -> ACSI.
  7. I like how you can say that apps like Omikron Basic or Prince of Persia use dirty/faulty programming techniques and give you headache when patching on one hand and on the other hand trash EmuTOS authors when they refuse to implement such workarounds.
  8. I'd imagine they had some kind of TSR (maybe a cart) which represented the GEMDOS/VDI part and the other team was just developing AES/Desktop as a standalone app in Alcyon C, along with libraries etc. And then the final product was merged together with the few bridges in memory as needed.
  9. I would be much more careful if I were you. There is a long thread on AF where various aspects of such adapters are discussed. Most of the cheap China-made ones are just "pass trough" circuits, i.e. you LCD must support 15 kHz horizontal refresh rate. Then there are well proven solutions like Open Source Scan Converter (OSSC) which work well but are quite expensive. Everything inbetween has offered inferior quality and/or had issues for overscan resolutions (demos, games). Not saying that this is the case here but judging from his YT comments (where he admits he hasn't tested it with ANYTHING ELSE than a few games) I would be very catious to spend $100+ on this. EDIT: start reading here: http://www.atari-forum.com/viewtopic.php?f=15&t=20971#p346101 (see especially evil's posts with his results and test prg).
  10. If you trust the seller, it's possible some capacitor and/or potentiometer has just a cold solder joint, i.e. it got damaged / twisted / disconnected during the transport.
  11. There is a lot of ways to do that but since you have asked about the best way https://www.alza.cz/auto/powerplus-powx1704-d5471371.htm
  12. Almost. I wouldn't trust FB/AF very much these days. There's a lot of "old schoolers" who fell into this trap, only to see their stuff relisted for double price few months later.
  13. Interesting. Anyway, fix should be easy in this case, one NOP before the read should flush the whole pipeline. I can imagine how much fun was this pipelining behaviour to discover. :)
  14. I presume it is not but - isn't this just a CPU cache issue? I have never heard of 68030 not being able to run SMC code with caches off.
×
×
  • Create New...