A więc włożyłem 74LS08 i w space harrier w.formacie rom kaszanka na ekranie od samego początku. Mam też 2.wersje w.fomacie car i tam menu główne gry wyswietla się już poprawnie, potem kaszanka.
Hmm, no to nie wiem jak pomóc. Ja mam fw 0.69 w SIDE3, ale z tego co pamiętam to Space Harrier działał mi od samego początku też na wcześniejszych wersjach fw.
For those who like to live dangerously, it's possible this might alleviate timing issues otherwise apparent with JED 1.1/1.3. Note the loader will report a spurious JED version number with this firmware, owing in part to a JED version workaround for Altirra. I'll come up with a fix for that presently. Re-running the XEX JED updater a second time, however (and then bailing out) will show that the JED was downgraded to version 1.0.
Don't try this unless you have to, and don't apply JED 1.0 to a SIDE 3.1 (black PCB), since JED 1.0 has no awareness of the extra SRAM and other features introduced in SIDE 3.1.
Trochę późno odpisuję, ale lepiej późno niż wcale. Wgranie jed 1.0 naprawiło wszystkie problemy z odpalaniem Space Harrier oraz z kilkoma innymi grami.
@moulder Dobrze, że u Ciebie też pomogło :-) Ja miałem problemy po aktualizacji jed, a po powrocie do starej wersji już znów było OK.
@as Nie przesadzałbym z tym zachłyśnięciem się AVG/SUB. Sam mam SubCarta, ale to jednak inny produkt, bo z założenia miał być takim kombajnem. SIDE3 spaliło się przez 3.1 i niestabilność,ale firmware FJC tandemu U1MB i SIDE rządzi, w SUB to jest jednak dość toporne, choć funkcji multum (i skrótów do zapamiętania). Ja tam SIDE3 bardzo lubię, jest naprawdę pro do używania.
Presenting a good-faith review of the AVG and SUB Carts does nothing to promote nuance in some quarters, I see. :) Great products and very cost-effective, particurly for those who prefer not to modify the host machine. However, neither of them interact with U1MB (for those who would like this) in any way unless switched into SIDE emulation mode, and interestingly enough the single most common complaint I hear about AVG/SUB is that the firmware isn't more like that of SIDE3. :)
However, if it has to be a contest, it's clear AVG/SUB 'won', for better or worse. Naturally I still use U1MB/SIDE3 and they do everything I need (don't have a SUB Cart since I had to return it after reviewing it), but it became clear to me some years ago that the esoteric and decorative features fo the SIDE3 loader are important to less than ten per cent of users.
One of the chief advantages of AVG/SUB is that the hardware is designed by the same person who developed the software, thereby eliminating a lot of communication issues where important stuff gets 'phoned in' by one party or another. Tmp does a fantastic job, anyway.
The given examples are programs that are "SIO only". These will not work with PBI/ECI and since the SIDE3 does not have a SIO-cable they will not work with it.
Thats why I have created two folders on my SUB cart SD-card, one is named SIO (for programs that only work with SIO) and the other is named PBI (for programs that take so long to load, that it is better to load them with PBI). A folder named CAS does however not exist on my SUB cart, since I am much too impatient to load programs with tape speed.
Not many A8 programs in that SIO-only folder yet, at the moment only some demos and no games. Will have to enhance it with more programs asap (some Lucasfilm programs, A.R. City and Dungeon, Seven Cities of Gold, etc.)...
I can confirm that Bitter Reality only works with SIO.
Regarding Loaded Brain, there exist several versions, think the original version came on two disksides. But I do own the single-sided version since several years now and therefore removed the double-sided version from my collection. This single-sided version can be loaded with PBI.
To make it work, I simply had to replace a hi-SIO DOS version (BDOS.SYS = Bibo DOS, either XF551 or Happy/Speedy version) with a standard DOS (Atari DOS 2.5) version, since hi-SIO DOS versions almost never work with PBI/ECI.
Fun fact: In the past I replaced many slow/standard DOS versions with hi-SIO DOS versions, so that they work with highspeed on my Speedy 1050 floppy drive. Nowadays I am doing the opposite, replacing many hi-SIO DOS versions with slow/standard ones, so that they work with PBI from my SUB cart...
So does AVG/SUB automagically know when to use the SIO bus to load those titles which rely on custom SIO-only loaders (titles which I never once claimed worked with PBI/ECI-based ATR support, since it's self-evident that they won't)?
And if you have both SIO-cable and PBI/ECI cable connected then the SUB cart would not know what method to use. But you can configure in the setup (CAPS key) what loader method (SIO, PBI, high-speed SIO via alternative OS, highspeed SIO via PBI, etc.) you want to use.
So, the SUB cart cannot automatically choose the correct loader method, it uses what is configured in the setup (and if this is wrong, it does not work). That's why I have created a folder named "SIO" on my SUB cart and placed several programs into this folder, where I know for sure that they will not work with PBI. (Of course this SIO folder is still very small, since I have not tested all of the many thousand programs I have on the SD-card; most programs that load via DOS can be made to work with PBI/ECI if you simply use a normal/slow DOS version without any highspeed SIO drivers.)
Might be a good idea to provide some kind of metadata tag in the filename to allow automatic selection of the most optimal loading method, then, once it's known. Similar to the [BASIC] tag in the SIDE Loaders which allows an executable to specify that internal BASIC should be enabled prior to loading.
Jon, I think the newer Beta firmware for AVG and SUB does have that tagging feature, at least I remember tmp mentioning this in either of the threads on AA.