drac030

I see no objections, i.e. I think it should work without problems. Just get the current version, i.e. the one which can be found on the SpartaDOS X 4.41 cartridge, because any older one will most probably contain bugs that have been fixed before it got incorporated into new SDX.

That looks cool. does this have a driver or does it work with the ICD RT8 driver? SpartaDOS X 4.3x/4.4x supports this clock (the driver is called ARCCLOCK.SYS).

http://atariki.krap.pl/index.php/R-Time8

The page you need is translated there, in the first section named "I. Prerequisite: intSDX with the old SDX 4.22". It even says below that: "the following is just a short English summary of the information from the designer's (Pasiu) page" and the "designer's page" is this one: http://hardware.atari8.info/sdx.php The first section is the instruction how to build the 64k intSDX. Only the section two contains the instructions how to mod the 64k intSDX to make it a 128k intSDX.

SpartaDOS' MENU.COM is nothing like the DOS 2.5 menu, it is rather a copying tool. In X it allows to copy files over from one floppy to another using only one disk drive (the ordinary COPY command does not allow swapping floppies). ... yet

http://trub.atari8.info/index.php?strona=h...x_128kb_en.html

http://atariki.krap.pl/index.php/Lista_handler%C3%B3w_CIO

Currently it can not.

SpartaDOS X uses (or: can use, if the user wants so) the extra RAM to keep most of the kernel code, disk buffers and resident programs.

I don't know about 2.3, but the lowest possible MEMLO in X 4.41 is $0E40.

I currently have no idea. Must look up the sources. Certainly, SpartaDOS establishes the density now according to the PERCOM information returned. If none is returned, Atari 810 SD or Atari 1050 ED density is assumed. Is is so much trouble for MyIDE author to release an upgrade with READ PERCOM support? This command is de facto standard.

I am sure he would. Why not?

Provided that there are active SpartaDOS X developers who actually have the source code and can compile it directly into a ROM image, these "efforts" you mention to binary-patch a release version in a hope that it would somehow work, and the patcher did not omit any register reference or did not overwrite anything important, are rather funny form of aberration IMHO. The correct procedure to have a type of cartridge supported by SpartaDOS is actually to sponsor one device to the project maintainer. ABBUC did so with Turbo Freezer 2005, so their Turbo Freezer is supported.

The reason is that noone has MyIDE+flashcart, so there is no way to test the images. The same applies to the MyIDE driver someone wrote. It can't be included in the cart release, because there is no way to test, if it works correctly.

Ok, I understand now what are you referring to. Surely, it would speedup FP calculations and such, but in fact FP calculations are rarely used. I guess that all the gain would be wasted on communications with the cartridge and its coprocessor. You know, the calculations even the BASIC interpreter does are mostly ordinary integer stuff, most of the speed gain you can do with an accelerator comes from the fact that every CPU instruction is executed faster - not from the fact that just FP calculations are faster. I can't imagine how it could configure the system f.e. to use the native mode interrupts, in the other way than replacing the XL OS with something loaded into the RAM below the OS. This is "replacing the OS" I mentioned above and it is way better done by replacing the ROM. There are already some 32-in-one OS-es, so what is the problem with adding one more, this time really necessary? Yes. The high RAM (past the $FFFF) is clocked at 7 MHz currently, maybe 14 MHz in the near future.

SpartaDOS X 4.41 has officially been released: http://trub.atari8.info/index.php?ref=sdx_upgrade_en Problems - if any - with the software and documentation please report (preferably in Polish, but English is also accepted) here: http://atariarea.krap.pl/forum/viewtopic.p...id=77286#p77286

I don't understand what you are talking about. 65C816 by itself is not faster than 6502. It only can run at higher clock speed, and can do 16-bit calculations and moves with single instructions. To use the 16-bit instructions normally (with interrupts enabled) you have to replace the OS. It is an ordinary Atari with the CPU replaced and some (1 MB for example) of additional, directly addressable fast RAM located past the first 64k.

I am not speaking about accessing data. I am speaking of running code. The only speedup you gain in Warp 4 comes from running code in the high memory.

On cart it would not work, I guess. The entire goal is to have the new and the old memory directly adressable for programs, and this means that the CPU has to be replaced. The OS has to be replaced too, the old XL OS does not allow to switch the CPU to the mode in which it is able to run code in the extended memory (past the first 64k).

Right, it was called "Laser Demo", not "Lasermania Demo". I remembered that scroll, because, after I saw it, I was able to reproduce the effect using just the same method Rybaqs mentioned, i.e. with two fonts shifted one bit off one to another.

Lasermania Demo (year 1991 or something).

Or <commercial> this one http://drac030.krap.pl/eddy.arc </commercial>

You don't use D1 because it is not "free", it is reserved for PBI devices (like MIO, Blackbox, KMK/JŻ IDE, and so forth). The chip used in the VBXE is an FPGA.

But Micro SpartaDOS, despite the name, is not a DOS, AFAIK, it is just a binary loader + fileselector.

But on a 48k 800 it won't be low on MEMLO, rather contrary. With Axlon, though, it should be as low as on an expanded 130XE, yes. Other DOS-es load either to main memory or to the RAM under the OS, like DOS XE or SpartaDOS or whatever. The superiority of the SpartaDOS X is that it can occupy whatever memory you want: the main one, or the one under the OS, or the 130XE/Axlon banks.