FujiNET firmware v1.3.0 Nowa wersja oprogramowania do interfejsu sieciowego FujiNET. Tym razem z obsługą TCP! hatari 2.5.0 Od dwóch dni dostępna jest najnowsza (2.5.0) wersja Hatari. Grawitacja 2024 Czas na kolejną edycję 8 bitowego GameJamu. Tenebra na Atari ST/STE Wersja gry na duże atari. Wyniki FujiCup 2023 Wyniki konkursu FujiCup na najlepszą grę dla 8-bit Atari w 2023 roku zostały ogłoszone!
Na razie ciekawie się zapowiada. W kwestii GUI to chyba wzorcem jest to co zrobił FJC w fdisku do APT, uflash i innych. Nie tylko menu, ale także listy, okienka dialogowe, przyciski, pola tekstowe, pola wyboru. W dodatku responsywne - działa w 40 i 80 kolumnach (VBXE lub soft. GR8). Pytałem go nawet, czy kiedyś udostępni ten framework - owszem, jak będzie miał go kiedyś czas ogarnąć :/
Perhaps in the current circumstances, I will have time to address this request, finally. :)
Problem with my library is definitely code size, but once you start handling dialog boxes and file selectors with event-based callbacks (which is what is going on in FDISK, UFLASH, etc) and every control existing as a self-contained object, it takes a lot of code. GUIs are by their nature quite code-heavy.
Error code 132 ($84) means 'No device handler installed', so perhaps the SDX ROM is entirely corrupted at the moment. I have no idea; one would not normally see such an error message under any circumstances.
Może tak było naście lat temu, gdy "gołe" Atari 8-bit dało się kupić za 50 zł, ale obecnie?
...obecnie nadal można kupić sprawne Atari za mniejsza lub podobną kwotę. Więc wkładanie 2gie tyle w coś co umożliwi uruchomienie dodatkowych kilku procent dem i gier (które można sobie odpalić na emulatorze) jest mało racjonalne.
Z kolei dla kolekcjonera, więcej wart jest komputer w oryginalnym stanie, niż z takim współczesnym rozszerzeniem... U1MB pod tym względem jest w miarę ok, bo daje się wymontować bez śladu, nie wymaga "twardych" ingerencji w płytę główną.
Read feature list of U1MB; there's a reason it sold four figure units and it's not because it provides 1MB of RAM. If extra features aren't for you, SIMM 1MB expansion exists. I cannot understand the argument over a device what provides value for users who actually want what it offers. Market decides what rises to the top, and thousands of users seem to think it was a good investment. U1MB is by no means mandatory, though, if you prefer to use something else.
Why would Sophia and VBXE not work together in the same machine? If there's space for a DVI connector on the back of your Mini-ATX case, you can have DVI out from Sophia and 15KHz RGB out via DIN13 from VBXE. No problem.
Rapidus, meanwhile, will fit if you use ebiguy's alternative XEL-CF3 adapter PCB. Contact him via AtariAge about it.
Unfortunately Rapidus cold-started my machine on RESET after five minutes of use (just like every other machine I put it in), so I took it out again, but I still use ebiguy's board, since it has handy connection points for VBXE.
mate, Zaxon added four 100nF capacitors and the CF3 magically started to work with the cards that failed to work before, so maybe there is something to improve in hardware design (CF3) to make it working better (in terms of cards compatibility).
Quite possibly: this is exactly the point I was trying to make. Any improvements should be fed back to mytek.
dely napisał/a:
Is XEL-CF3 will boot with unmodfied XL/XE ROM?
It will. It's driven by a PBI BIOS, so works seamlessly with stock operating systems. It even works alongside external PBI devices providing bus IDs do not clash.
@tooloudtoowide - jeśli to klon MyIDE (co podejżewam), to wolę sprawdzone rozwiązania które notabene działają praktycznie z dowolnymi kartami CF, czy dyskami ATA. Nie można porównywać MyIDE do pełnowymiarowego urządzenia NewDev - IDE, bo to jest trochę tak jakby porównać protezę nogi do prawdziwej nogi :)
If MYIDE could be driven by the U1MB PBI BIOS, it would be functionally identical to any Newdev IDE device, since that's exactly what is implemented. XEL-CF3 registers are in the $D1xx region, doesn't interfere with cartridges or block the cart port, and operates 100 per cent as a Newdev PBI HDD. Whether buffering and stabilisation methods of the hardware allow it to work with a particular card is another matter entirely.
New firmware works perfectly well with the CPLD code supplied on all Lotharek boards. Only the very old (v.1) JED requires an update prior to flashing my firmware, since it relies on IORAM at $D1xx and $D5xx which is not present in the v.1 JED. If you have a black U1MB board without RD4/RD5 current limiting resistors on the PCB, check first.
My firmware has no issues booting the machine in 1088K mode, so certainly look to the hardware or CPLD programming for issues.
Boogie Nights is a simple fix. Using the new U1MB/Incognito firmware, enable the PBI BIOS, and then set 'BASIC state' to 'disabled' on the first menu. It seems the demo simply fails to disable internal BASIC, but I have no explanation for why it works without holding down 'Option' on stock machines. In any case, it booted perfectly via SIO2SD on my U1MB 600XL, even using the high-speed SIO driver built into the newer U1MB firmware. :)
Of course regardless of BIOS settings, it loads from SIO2SD if you just hold down the Option key too.
It would be useful to know which Incognito firmware is being used and whether or not internal (PBI) high-speed SIO is enabled for those titles which fail to load via SIO2xxx devices. Regarding the problem titles, most or all exhibit identical behaviour on U1MB systems (which is hardly surprising given that Incognito's XL/XE mode emulates exactly the same operating environment).
1. Boogie Nights (XEX) may be incompatible with the SIO2SD boot loader. I don't have SIO2SD to hand right now, so can't confirm. 2. Overmind (ATR) hangs on an U1MB when run from the CF card too. Possibly it relies on some property of being loaded from a serial peripheral. 3. Bitter reality (ATR) encounters a disk error on an U1MB machine when run from the CF card, probably also because it provides its own built-in serial loader. 4. Phantasy (ATR) crashes when loaded from the CF card on an U1MB machine (reasons unknown).
Any ATR which chooses to load itself via a custom SIO loader will always fail when launched from the CF card. The ATR handler is only compatible with software which employs standard calls to DSKINV/SIOV.
I take it this board ships with the stock ROM? Speed appears to be ~38K and SDX reports a parameter error when formatting 80 Track DS/DD, although it DOES format at this density:
In the interests of clarity: I have NOT released this version of UFLASH yet since using the external SIDE banking register was not as easy as made out, at least in the context of this particular tool and the way it operates.
I suspect BASIC is switched off somewhere else, perhaps by ATRs themselves, MyPicoDOS, etc. Possibly even a patched OS with reverse Option logic? I even searched Google and in all articles I found, it was said that Option must be held to disable BASIC with SDrive, unless the ATRs themselves have provision for automatically disabling BASIC.