drac030

I just checked it quickly, move works here. SCMAIN.OVL 15849 bytes, 15 Oct 2021 21:33. So more information is needed. BTW. 156 is Bad parameter, a weird error indeed. Could you try reflashing the ROM? Its intention is to provide information on how to write application programs rather than drivers. I hope that the next version will contain that section too. What you seem to need is a sector I/O driver, the chapter dealing with that is to be found in this thread, here: There are few minor inaccuracies, which I fixed already, but they should not impair anyone much. Yup, fixed, thanks. That is to be fixed too, thanks.

Excellent catch, thank you very much. It is a bug in the library (so replacing DOSKEY does not help). We will most probably upload a fixed revision today. As about the SDX Imager, it has been heavily rewritten, so if something does not work, please report - either here or to @trub.

IIRC, to access more drives in DOS 2, you first have to declare more buffers for disks. If you have 4 disk drives, you have to declare 4 buffers. If fewer buffers have been declared, expect problems. DISKFIX.COM is a tool to verify the continuity of the files and the integrity of the VTOC (aka disk bitmap).

Something neat that does not work It is cheating IMHO. A 256-byte intro, which uses illegal OS calls, is not really equally the same as another 256-byte intro which does not use that. They should not be in the same category.

I think it needs patching MyDOS. IIRC, it loads DUP.SYS from "D1:DUP.SYS". So the thing to try is to binary edit the drive number in that string on the booted MyDOS in the memory, then write DOS files to the required disk. It may work. Did not try

The low level formatting is being done by the disk drive's firmware. The floppy is divided into tracks and sectors. After that, the disk is empty (all sectors contain zeros). The directory structure is created and written to the disk by the DOS. It is its internal fuction. XIO 255 and friends usually do both things, i.e. send a command requesting physical formatting to the drive, then write out bootsectors, directory sectors, VTOC and other things if applicable. The logical disk structure (directory, VTOC etc.) is completely up to the DOS.

There is a new beta version of SpartaDOS X available on the relevant website: 4.49f, dated 31 December 2021. It can be downloaded from here: http://sdx.atari8.info/index.php?show=en_download_beta The list of changes relative to the previous beta, 4.49e, is available in the file whatsnew-4.49f.txt Perhaps the most important change in this release is that the CAR: device is no longer limited to 8176 bytes per file. The new limit is 7*8176=57232 bytes per file. To take advantage of that, you have to use the new SDXImager, which handles both formats (the new and the old one). The new imager program can be downloaded from here: http://sdx.atari8.info/index.php?show=en_addons Sorting the directories should now be much improved, as SORTDIR.COM now uses a new, much faster sorting routine. By "much" I mean 40-50 times faster than the old ICD code. The same sorting routine is used by Sparta Commander to sort directories in real-time for display. The ED text editor can now run on VBXE 80-column text console as well as on the software-driven 80-column text console (provided by RC_GR8.SYS). Besides, there were bugfixes and minor improvements all around. 65C816 support ========== Also, this version comes with improved 65C816 support, which is now centralized in a form of unified driver, 65816.SYS (this one is for Rapidus OS, and there is another instance for AltirraOS/816, named 65816A.SYS). Owners of Rapidus and Antonia machines may want to put that driver onto the CAR: device before flashing the SDX ROM, along with the SIO816.SYS - these are available on the Toolkit disk, among few others which can be loaded from the HDD. The immediate effect of configuring the system to use these is that much more conventional RAM would be free - as the new drivers load to the RAM past the first 64k. All this is also usable on Altirra. The 65816.SYS driver, among other things, contains the binary loader able to load relocatable binaries in SpartaDOS X format to the RAM past the first 64k. Such binaries can be built using the assembler ELSA http://drac030.krap.pl/pl-elsa-pliki.php Below I am attaching some small demo program which may help to test, if the 65816 support stuff is properly configured. It requires VBXE. The source code is included. Have fun. stars3dr.arc

The alternative names Atariki lists beside (not "instead of") those have been in circulation in Europe (or at least in Poland) for more than 30 years now. I think most/all of them come from the reverse-engineered XL OS listings which were published here in printed form around 1989. So you may say that they were made up by someone (as if Atari's official names were not), but still, GTIACTL actually makes much more sense than "PRIOR".

Actually, the poetry is difficult to understand only in two cases: 1) the poet was/is bad and it is bad poetry, 2) the poetry is good, but the reader does not understand the language. And I do not mean the language of the words, but the language of simple images being used to invoke other images in the reader's mind. Simple example: one could be confused when encountering a phrase like "the one who can see everything", unless we first learn the language of (this specific kind of) poetry and therefore know that this must be Helios, or the Sun. The same counts for sculpture or painting, a painted or carved figure will be completely anonymous, unless we know the language. E.g. if you find a sculpture of a woman in ancient dress and with an attic helmet, you would not need any caption to know that it is Athene. Similarly, if you see a religious picture of a man who defeated a dragon, it must be St. George, unless that man is winged, then it is Michael the Archangel. So, the principle here is as everywhere else: if something is difficult to understand, then it is either gibberish or you do not understand the symbols.

You are right pointing out that "e" in "per" is short, whereas in "se" it is long. But still it does not really need emphasizing in script. PS. I now feel guilty for derailing the topic. And yet I cannot blame anyone else, than myself, for that. I probably should report myself to the administration and get banned

Ah so, I see. I just was wondering why to make the effort to decorate the letter when no decoration is nęęded

Apologies for off-topic, but why "se" is accented?

That is perfectly understandable. However, the website's title says: And so, whereas "new", or "programming language" are not obviously striving for strict definition, "human-friendly", for the reasons specified above, may need some explanation on the top of the website, at least as long as the rest of it suggests in a veiled way that "human-friendly" = REBOL-like.

Maybe some of these qualifications could be moved to the beginning of the explanations in the website, such as: and because these two are greatly clarifying your definition of "human-friendly"

That declared "human-friendliness" seems to cause much confusion here, perhaps it would help if you defined it more precisely. Because, as stated several times already, pretty much everything in this world is human-friendly, even king cobra, once you have already learned how to deal with one. From the mere declaration one expects the language to be intuitive, but it apparently is not your intention, for nobody needs to learn things which are intuitive (that is the definition of intuitiveness). So what does this mean really?

$A000-$BFFF is normally occupied by the SDX cartridge. If you want RAM there, use X command (as you did). Yes, "USE BANKED" configuration, as you said, uses the Ext RAM, doing the memory banking at $4000-$7FFF. Any I/O call will result in the memory being banked, so if you put your interrupt routine there, expect a crash.

MD5.COM to be found on SDX Toolkit collection hashes 25040 bytes (the first file I grabbed as an example) in 6.94 sec (8.38 including loading from HDD), which gives about 3600 bytes/s. Sure, Atari is faster, but not twice as fast

Rosetta stone is not very relevant here, because now we are living in the times after the Rosetta stone (so one can learn hieroglyphs from a textbook), and also there were times when the knowledge of the hieroglyphs had not been lost, and you were able to learn them from a teacher. So for the sake of a better analogy, we can say that it is Greek instead of hieroglyphs (because the knowledge of Greek has never been lost). The point, at least as I understand it, may be somewhere else. You are claiming that Meta has "Human-friendly syntax" and is "Closer to human language than most computer languages". Perhaps it is so. But for the untrained eye, the examples available in this thread contain much too many usual code symbols (=, [], ~ etc.) to be recognized as a human language: perhaps it is "closer", but still not does not look like close enough. For example: unsafe!!! constant reference volatile byte! [ RTCLOK= ~14 ] In human language it would be rather something along the lines of label volatile byte number 20 as "RTCLOK".

By this definition ("learn it") pretty much everything is "human-readable", even Egyptian hieroglyphs.

So far he has not even been able to explain this: Basically, "nothing works, see, how bad it is", but when asked about details, then "oh, I do not know exactly". Gosh.

Yup, might have been. Like 10+ years ago. So how long ago you tried and which version of SpartaDOS we are talking about?

What FDISK? FJCs FDISK works on VBXE in 80-column mode. True, it is about just the only program which does not display itself in VBXE 80-column mode. What is "the menu system"? SpartaDOS X MENU _does_ work in 80 column VBXE mode. Program names of that other stuff, please? Even approximately.

Not sure. As said above, VBXE outputs the same kind of signal as Amiga or Atari ST. Monitors like Commodore 1084S, 1085S, Atari 1224 or 1435, European TVs with SCART connector should be okay. Any converter from that format to VGA/HDMI should also be okay.

Yes. Nowadays everyone has the luxury of being able to contact active developers directly, either via e-mail or through the fora. It is not 1990, when, to get some support, I had to send a letter written on paper (and in a truly alien language!) to the other half of the globe, only to receive no reply just after six months. And now, as to the point being raised, we all are here on AAge. Maybe not every day, but still. So, what, specifically, are the things that do not work, when they should?

VBXE does not produce own sync signals, these still come from the standard Atari hardware. So if the monitor got the signal from the outside of its normal range, it definitely was not the fault of VBXE, but rather the fault of your scaler. NATURALLY. It is not NTSC, nor PAL. It is RGB. No artifacting or any other color distortions in RGB. "Utils" need to use system calls to produce display on 80 columns (e.g. TBXL is able to draw a circle on VBXE display - a miracle problably). Otherwise, when the ANTIC screen memory is written to directly, it obviously will produce no display on VBXE (nor XEP80 nor on anything else).