trub

Indus GT with firmware version 1.20 is required. According to the service manual, earlier ROM releases have serious bugs and should be replaced anyway ROM version is displayed while Synchromesh is being loaded and can also be checked with CPMTool. In LDW Super 2000 drives (Indus clones) the connector J3 is not soldered in. In such case an easy fix should be done prior installing the board (see info on my page).

Thanks for the info. Good job !

Error 1 means that there is no extended RAM at $8000. Check if A15 enables it. You probably saw a file "indus14.bin" which in fact is the older 1.10 ROM. The 1.20 file is "indus12.bin".

Not possible with regular SIO commands. Just run CPMTool to fix the CP/M disks (it uses drive downloadable code to write full 256-byte boot sectors).

1.20 ROM is fine, there is no 1.4 ! To run CP/M you need 1.20 (some drives have eariler versions 1.00, 1.10) Run CPMTool and see what it shows.

Looks fine! The tight connection will make the whole thing more reliable. What about the case ? Does it fit ?

No, /ROMDIS is an _output_ signal which is used to disable the drive's firmware ROM when the external RAM is accessed. So it derives its state from the /BANK input line. As a result, /BANK is used as an input to multiple TTLs. You may consider some kind of signal duplication to avoid potential problems (although it wasn't needed in my INDUS and LDW).

The idea of having the header on the other side is great ! Keep two PCBs for me, one for Indus, the other for LDW. The original INDUS.SYS driver is a cut down version of Super Synchromesh, without track buffering. Besides, reports exist that a drive programmed with buffering does not work well with SDX. This subject is under an investigation. A new driver is under development with help from sup8pdct and kyle22.

SRAMCharger is a functional replacement of the original RAMCharger board. CP/M operating system and software can be run on the drive using Atari as a terminal. See my page for more info and utilities: http://trub.atari8.info/index.php?ref=cpm_en Track buffering is possible only with Super Synchromesh software. tregare: Indus and LDW Super 2000 have different boards. In LDW, connector J3 is positioned horizontally (see pictures on my page). If you want to make the PCB universal, you can provide mounting holes for LDW-type connector.

Boot the disk with OPTION, Microsoft Basic should load. Then type RUN "D:DIAGS". The utility is a little bit different than described in the manual but performs the similar functions.

Have you tried bypassing the 320ohm resistors ?

Yes, see my post #567 above.

I successfully connected VBXE to a composite input via Amiga modulator (a Polish A520 clone) The clue is MC1377 encoder which converts RGB into composite or s-video. The chip can also be found on some ST boards. The VBXE RGB signals should be connected to appropriate inputs of the chip (via capacitors). Their levels must be adapted to the required level as Candle wrote above. I have done this by grounding all three RGB signals with 75R resistors. The other problem is to provide 12V to the encoder chip (Amiga video output has this). I used an external power supply but I think a DC-DC step-up converter would also do. A520 does not have S-Video output by default, but it can be added as described here.

DLT introduced the 816 block moves in 4.39, have you forgotten?? FTe's 4.22 just tries to detect 816 CPU (or Sweet16 board) and do nothing with it later.

An enhanced Indus CP/M terminal is available, which utilizes the VBXE 80 column text mode. I attach two screenshots of Turbo Pascal and Wordstar. The green font simulates the oldstyle hardware terminal , but it can be changed if required.

See the chapter "SpartaDOS User Accessible Data Table" in the SpartaDOS X manual. There is a pointer to the hi-speed SIO routine under COMTAB-10. The pointer is preceded with a jump command (at COMTAB-11).

Thanks for the report, it's true - we have been hacked It should be fixed by know. I have also added some security enhancements. Anyway, we are considering to move to a more secure server.

If you have the flashable version of intSDX, disable flashing (there should be a switch/jumper somewhere). It should be enabled only during the process. Leaving it enabled afterwards causes such problems.

Done, see sdx.atari8.info.

Dwhyte, please understand that no one blames you for extracting the ROM file from the ATR. It would be polite however to contact anyone invoved before releasing it to the public... That's not true. Read above, I have just explained this. Note that Real.DOS version 1.0a has already several builds. Will you also complain to the author that the version number persists while releasing bugfixed revisions ?

This has been discussed and we decided to change just the revision date and leave the version number intact. Changing the version would be more confusing, because the problem applies to Maxflash 1Mb image only and systems with a double cartridge slot. The people who had this problem were announced that the update was available.In fact, the modification is minor (an additional line in CAR:CONFIG.SYS) and one can achieve the same by a custom CONFIG.SYS.

Unfortunately this is not a "potential", but real inconvenience. SDX Maxflash 1Mb image has been updated two weeks ago (with RTime-8 issue fixed), while the .car file posted by dwhyte still contains the previous version. We would like to avoid such situations in the future.Dwhyte's idea of making ready-to-use cartridge image for the popular emulator is very good (we have never thought about it, because most of us use real machines ). You must understand however, that it should be hosted at one place with other stuff for easy update. We don't want to discourage anyone to submit new solutions or ideas. There is a bug tracker system which can be used for that. We very much appreciate any feedback.

You should use INIDOS.SYS if you want to boot SDX from QMEG. See SDX manual for details how to setup INIDOS.SYS.

Please, download the Maxflash1 image once again and reflash. RTIME8.SYS has been missed from the default CONFIG.SYS.

Note that Maxflash 8Mb and R-Time8 are hardware incompatible, so use Maxflash 1Mb for hosting SDX 4.42.