trub

Please note that SDX 4.44 should be customized with the new SDX Imager version 2.0.5 published yesterday.

There seems to be some misunderstanding. Atrax is a name of a Polish manufacturer of different cartridges for Atari (and C64). SpartaDOS X was just one of them, so referencing a cartridge by the name "Atrax" may be ambiguous. SDX version by Atrax used the same banking scheme as the original ICD cart, but it was built using different electronics. The main problem is it is not flashable, because data and address lines were crossed to "encrypt" eprom contents. Nowadays, when new SpartaDOS X versions are released quite often, I would suggest building a flashable cartridge instead, like this one.

I don't understand what you are doing. The emulators do not support Atrax. Use SDX128 or Maxflash .ROM images (no need to convert).

To create Atrax image download the Atrax converter (available in Add-ons tab). Then use the following syntax: sdx2atrax c SDX444_sdx128.rom SDX444_atrax.rom

Have you read the instructions how to configure SDX with MUX ?: http://sdx.atari8.in...hp?show=en_docs

Why not using the current version from SDX Upgrade Project site.?

It does, however you have to create the customized CONFIG.SYS as a PC file and then use "Insert" function of the imager. It will then replace the original file with the new one.

You can also run MAE with SpartaDOS X and its XEP driver (XEP80.SYS). It seems to work fine.

PCLINK protocol is implemented in sio2bsd, the sources are available at Drac030's site: http://drac030.krap....-inne-pliki.php Official specification of the protocol is here: http://atariki.krap....dex.php/DOS2DOS (Polish-speakers only )

An updated revision of SDX 4.43 (version number kept, but dated 11.04.2011) is now available for download. Please update ! The changes cover SIO.SYS switches not working, new hardware platforms (SicCart! and IDEPlus 2.0) and drag-and-drop feature of the imager. absolutely !

Force loading the ARCCLOCK driver with /F switch.

SDX Imager (customizer) is now available for download. Be aware that it is designed for special/advanced purposes like adding extra files to the CAR: device. Users of flashjazzcat's myIDE driver can use it to replace the default CONFIG.SYS with a custom one.

Will be released in a couple of hours.

From my experiences I can say that Diamond GOS does not work very well with SDX. This has nothing to do with intSDX extended banks. Diamond expects different directory formatting than SDX presents. For example, SDX does not show file timestamps when they are not set. This fools the GOS and stops directory processing. The problem applies to both the old ICD versions (like 4.20) and the new DLT 4.4x. In addition, the directory format in SDX 4.4x is a little bit different than earlier due to enhanced filesystem. Diamond uses a trick to detect end of directory which no longer works in 4.4x and hangs up the system. Upon the release of SDX 4.43, I will also make available a patched version of Diamond ROM with the two issues resolved. It will be a modification of the original cartridge dump (not the Maxflash version), so usable as a replacement ROM. I am currently using it in Candle's SuperCart/Foocart which allows to mimic the Diamond banking scheme and it seems that SDX and the patched GOS now cooperate quite well. This is not true, SDX uses banks $D5E0 and above. The addresses you gave apply to Diamond only.

SDX has FIND utility which replaces the older WHEREIS.

New SDX beta (4.42g) is about to be send to testers. A ROM with MyIDE driver included may be based on that beta.

I've been playing a while with Candle's all-in-one cartridge, which was announced above. It's really great and very flexible ! I have enhanced the internal logic of CPLD and now it provides four cartridge "slots": SpartaDOS X 128kB (upgradable) 4xOSS cartridges (Action, Basic XL, Basic XE, Mac/65) Maxflash 1MB (flashable) Diamond GOS Note that each "slot" uses a different banking scheme. The cartidge roms don't need to be patched because the logic mimics the original banking. SDX controls all the stuff. To run one of the "virtual" cartridges, you just put its number to control register and then issue "CAR" from SDX command line. Under OSS cartidges you can return to SDX with "DOS" command. Maxflash slot can be programmed with .BIN files prepared for the regular MF1 cartidges. I had to prepare a customized version of DLT flasher for the purpose, because the flashing utility from Atarimax does not operate on the virtual cartidge (differences in hardware). Diamond GOS slot has been done just for testing. I'm considering replacing it with another Maxflash 1MB slot.

For more sophisticated setups you may also create a config file (text) and pass it to MAP as a parameter. More details in the manual.

You can turn OS SIO for individual drives with MAP command (like MAP 1 OS). Other drives will still use SDX SIO. intSDX 128 hardware (described here) uses the banking scheme similar to the older SDX carts (see here). An extra bit select lower or upper 64k. So $D5Ex selects banks from the first half (but located upper in the rom image), while $D5Fx is used to select banks from the other half. Anyway, I would rather recommend patching the existing intSDX image by modifying its CONFIG.SYS and putting the driver in. If you have problems with that, write me a PM.

The driver will allow for accessing MyIDE device from DOS routines only. Some programs will fail if they use stock OS SIO to access a disk. BTW. If you have a customized OS (MyIDE OS), put DEVICE SIO /A in CONFIG.SYS. The /A option will redirect SDX to use MyIDE-customized OS SIO. The same applies to The MUX OS which is required to run The Multiplexer hardware.

Instead of using a hacked (and outdated) image, I would suggest extracting the driver and use it with the current SDX version. Of course it should be then loaded from the command line or via a custom CONFIG.SYS. For testing & development having the standalone driver is the best solution anyway.

The difference is just the connector. Indus extension should have the connector facing down towards the male slot on the drive's PCB, while LDW/CA extension connects horizontally to the optional male slot on the side.

I can confirm that. The boards are great ! Excellent quality, compact and perfectly populated. Just "plug-and-play" it into your Indus GT and voila ! I will put the photos on my site soon

It is WD2797. The board is also designed to use 1770 instead, but apparently they never use the latter.

I would try replacing 74LS244 (U19) first. It often goes bad in Indus (as well as U23).