SpartaDOS X 4.45

[+Stephen]

I run my setup with "SET PAGER=LESS;/C;%" Works a treat and doesn't matter if I am in 40 or 80 column mode.

[a8isa1]

I have some questions/issues. Hopefully, they aren't redundant.

 

- CONFIG.SYS or .CFGs (in SPARTA.DOS) don't seem to work if they are on an Atari DOS format disk or a MyDOS format disk/ATR

 

- Question: Regarding the configuration menu, If I do nothing then after a couple seconds "[A] default" is automatically selected. Is there there a way to make one of the other selections the automatic choice?

 

- Flashjazzcat was kind enough to patch MYIDE.SYS to access a slave drive. The intent is so that I can boot classic MyIDE OS (4.2i) and SDX+MyIDE at the same time. This works. I can access both classic MyIDE partitions (on the Master) and new SDX APT partitions (on the Slave).

 

I have no problems copying files from classic partions to the new partitons but if I copy from the new back to the classic the VTOC (MyDOS 4.53/4) gets messed up. I end up with wrong sizes and crosslinked files.

 

Now I don't expect old MyIDE and MyDOS to be supported by SDX but my issue might be something more general. I think I know what's happening. SDX seems to be assuming that those classic MyIDE partitions are 720 sectors in size. They are not. Could SDX be having problems because classic MyIDE does not support Percom blocks?

 

- Do there exist any programming notes for writing a driver for new RTCs?

 

Regards to the SDX team.

 

Thanks for everything you have done and will do!

 

-Steve Sheppard

[Roydea6]

This is my version of manpages.arc for SDX4xx. couldn't upload an arc file so I added manpages.arc.zip to file. Just rename to manpages.arc.

 

-->

 

compiled with The Last Word 3.21b using a word wrap macro with minimal reformating of text.

 

Thanks for sharing. Could you briefly describe, what did you change?

 

But is does seem to work well with the SET PAGER=TYPE ;%;/P

 

Why not SET PAGER=LESS ?

I just word wrapped all the text to 36 columns and tidied a few lines, added a few eols to space headings and one to the end of file.

Googling and reading the SDX445 manual set pager=type..... was the first example I came across.

[flashjazzcat]

- CONFIG.SYS or .CFGs (in SPARTA.DOS) don't seem to work if they are on an Atari DOS format disk or a MyDOS format disk/ATR

The volume containing CONFIG.SYS must be in SpartaDOS format, otherwise the file is ignored.

[drac030]

- CONFIG.SYS or .CFGs (in SPARTA.DOS) don't seem to work if they are on an Atari DOS format disk or a MyDOS format disk/ATR

 

Already answered.

 

- Question: Regarding the configuration menu, If I do nothing then after a couple seconds "[A] default" is automatically selected. Is there there a way to make one of the other selections the automatic choice?

 

On some hardware only. Certain builds are for devices which contain RTCs with oboard NV-RAM. Then the last selection is stored in the NV-RAM and read from there at next startup. It works so on IDE Plus 2.0 and Ultimate1MB. Basically any type of battery-backed RAM may be supported, provided that its presence is easily detectable and storing the selection does not conflict with anything.

 

I have no problems copying files from classic partions to the new partitons but if I copy from the new back to the classic the VTOC (MyDOS 4.53/4) gets messed up. I end up with wrong sizes and crosslinked files.

 

Now I don't expect old MyIDE and MyDOS to be supported by SDX but my issue might be something more general. I think I know what's happening. SDX seems to be assuming that those classic MyIDE partitions are 720 sectors in size. They are not. Could SDX be having problems because classic MyIDE does not support Percom blocks?

 

IIRC, the ATARIDOS.SYS driver does not rely on PERCOM blocks. It however relies on STATUS block (but so does MyDOS, so I guess the STATUS block is correct,if MyDOS works), and on the first byte of the VTOC. Last time I checked copying to MyDOS-formatted partition (8 MB in size) worked flawlessly, eventhough what I did was a massive copying of files with COPY /R.

 

- Do there exist any programming notes for writing a driver for new RTCs?

 

Not yet. I am now at pains of translating the general programming manual to English, when this is complete, I may proceed with writing sections of it on writing the drivers.

[drac030]

I just word wrapped all the text to 36 columns and tidied a few lines, added a few eols to space headings and one to the end of file. Googling and reading the SDX445 manual set pager=type..... was the first example I came across.

 

I see. But that's not necessary, just use LESS as the pager. It folds the lines automatically to fit on the screen.

[flashjazzcat]

I am now at pains of translating the general programming manual to English, when this is complete, I may proceed with writing sections of it on writing the drivers.

:thumbsup: :thumbsup: :thumbsup: :thumbsup:

[a8isa1]

I have no problems copying files from classic partions to the new partitons but if I copy from the new back to the classic the VTOC (MyDOS 4.53/4) gets messed up. I end up with wrong sizes and crosslinked files.

 

Now I don't expect old MyIDE and MyDOS to be supported by SDX but my issue might be something more general. I think I know what's happening. SDX seems to be assuming that those classic MyIDE partitions are 720 sectors in size. They are not. Could SDX be having problems because classic MyIDE does not support Percom blocks?

 

IIRC, the ATARIDOS.SYS driver does not rely on PERCOM blocks. It however relies on STATUS block (but so does MyDOS, so I guess the STATUS block is correct,if MyDOS works), and on the first byte of the VTOC. Last time I checked copying to MyDOS-formatted partition (8 MB in size) worked flawlessly, eventhough what I did was a massive copying of files with COPY /R.

 

This reminded me of another problem I had.

 

When I try to do a COPY /R back to a MyDOS formatted disk I get, "146 no function in device handler".

 

Same is true if I simply try to create a subdirectory on the MyDOS disk

 

-Steve Sheppard

[drac030]

Yes, to do recursive copying onto a MyDOS disk you first have to create the directory structure under MyDOS. ATARIDOS.SYS driver is not able to create directories (this is the source of the error, "no function" is MKDIR). This is probably solvable.

[a8isa1]

Yes, to do recursive copying onto a MyDOS disk you first have to create the directory structure under MyDOS. ATARIDOS.SYS driver is not able to create directories (this is the source of the error, "no function" is MKDIR). This is probably solvable.

 

That's what I did, for one test. Recreating an SDX tree on MyDOS is not something I would normally need to do though.

 

OK. I can't duplicate my problem using an ATR via an SIO2PC. It only happens with a partition on classic MyIDE but it happens every time.

 

I don't seem to have problems doing the same test writing to a SpartaDOS partition on classic MyIDE.

 

It's was frustrating but in the end it's not a big deal. There's nothing I would need to copy to classic MyIDE and the things I copy the other way I need only do once, or each time SDX+MyIDE partitiioning scheme gets changed (which hopefully won't happen again).

 

Thanks for all the explanations.

 

-Steve Sheppard

[flashjazzcat]

...or each time SDX+MyIDE partitiioning scheme gets changed (which hopefully won't happen again).

Not by my hand it won't! APT is the standard (as it is written, so shall it be...) and I'm just waiting for other interfaces to follow suit.

[trub]

- Do there exist any programming notes for writing a driver for new RTCs?

Meanwhile you can look at "examples" in mads crossassembler package. It contains the source for ARC RTC driver. Although somewhat outdated, it can give you general idea how to write the drivers.

BTW. Which RTC are you considering ?

Edited November 21, 2011 by trub

[Roydea6]

I just word wrapped all the text to 36 columns and tidied a few lines, added a few eols to space headings and one to the end of file. Googling and reading the SDX445 manual set pager=type..... was the first example I came across.

 

I see. But that's not necessary, just use LESS as the pager. It folds the lines automatically to fit on the screen.

Ahhh.. the LESS I read the LESS I know.... Many new things to read and understand.

[flashjazzcat]

MADS examples are indeed WELL worth checking out.

[+bf2k+]

Just noticed the "Copy Progress" bar for larger files in the COPY command in 4.45...

 

======== 27%

 

Is this new or did I miss it in an earlier version?

[flashjazzcat]

AFAIK it's new to 4.45. I suggested it to KMK some months back because there was often no visual feedback when copying very large files (bigger than 64KB) on the now profuse range of HDD interfaces. He was kind enough to implement it.

Edited November 21, 2011 by flashjazzcat

[a8isa1]

- Do there exist any programming notes for writing a driver for new RTCs?

Meanwhile you can look at "examples" in mads crossassembler package. It contains the source for ARC RTC driver. Although somewhat outdated, it can give you general idea how to write the drivers.

BTW. Which RTC are you considering ?

Any one of the Dallas "Phantom Clock" chips (see notes for the DS1315), but specifically the DS1251 (DIP, i.e. no 'P' in the part number), since I have one waiting for me to build (or attempt to build) a home for it Edited November 21, 2011 by a8isa1

[trub]

If you have any problems or questions about writing SDX RTC drivers, feel free to ask.

[w1k]

the best OS

some screenshots can be uploaded on web page for illustration..

[w1k]

someone using sparta dos commander?

[+Stephen]

someone using sparta dos commander?

Yeah - I use it frequently with SDX 4.45.

[flashjazzcat]

Some features were incomplete last time I looked, but it's promising.

[flashjazzcat]

Don't know where KMK got to, but I've identified a problem with the SDX formatting menu when using VBXE. If the calling application has an XDL display set up - whether an overlay or with DMA turned off - the formatting menu doesn't show up (since it uses an Antic DL). I wonder if it might be a good idea for the formatting menu to forcibly (temporarily) re-enable DMA and turn off any active XDLs.

Edited January 13, 2012 by flashjazzcat

[Faicuai]

...Well, after some time awaiting TLC, I finally installed the Ultimate1MB expansion, on my 800XL.

 

Definitely one of those HW mods that falls in the category of "mods of mods", so you don't have to waste money on multiple (and potentially incoherent) modifications, thus eventually "ghettoing" the host machine, with a spaghetti of cables, and mumbo-jumbo soldering, all over. Nice-and-clean overall (even with resistors in-line, on the MMU ribbon).

 

All I can say: as SWEET as it can be within the constraints and potential of our little machines. KUDOS for all those folks that put such hard work in this wonderful O/S (and to Candle, for his Ultimate1MB).

 

Before this I had tried the SDX on a spare AtariMax 8Mbit cart, but that is like trying to fit a hord of Cheetas into a Fiat 500, so to speak. It is only when running on the Ultimate1MB combo, and after some basic configuration via config.sys and auto*.bat, when you eventually unleash its overall potential. I can only be impressed by how far this machine could go (and could have gone). Beautiful.

 

Now, I do have a few questions, based on my setup (800XL+Ultimate1MB, Nuxx SDrive as boot, and twin IndustGT+RamCharger as floppy):

 

1. So far, it seems that the only speed-factors I can set the SDrive to work with SDX is around $06 to $05. Anything higher, either the SDX and/or the Nuxx seem to lose track of what they are doing (e.g. multiple file copying within the Nuxx or between Floppies and Nuxx, for instance). Not sure if there is anything else I need to tune on SDX, in terms of buffers, etc.

 

2. When cold-booting (both 800XL from OFF-state, and Nuxx, witl all leds lit), and running a simple Autoexec.bat stored in SDRIVE.ATR boot image (with nothing other than screen-color changes, mem /x command, and a couple of SET definitions), the system does correctly detect the presence of the Indus, and makes it spin a bit, but it usually leaves the unit spinning at track 00 indefinitely (no disk read or transfer takes place, just spins). This goes away by issuing a "DIR" on the Indus, and it returns to track 39, and stops, as it should. No biggie, but it is there.

 

3. I wonder if it is possible to take advantage of the RamCharger installed on the Indus, in combination with SDX. Oddly enough, I was able to run Indus "GTSYNC ON" command (I copied the executable out of DOS XL into a working/boot SDX-formatted image). It DOES RUN, and activates track-buffering on the Indus, but both (SDX and INDUS) do not seem to exploit it.

 

4. How can I generate a 16MB or 32MB SDX-formatted image that I can use with my Nuxx SDrive, either as a boot image or as a working image? I tried as far as I could searching here, but could not find anything.

 

Many thanks, in advance, to those that take some time to read and answer some of this questions,

 

F.

[Frankie]

...Well, after some time awaiting TLC, I finally installed the Ultimate1MB expansion, on my 800XL.

 

Definitely one of those HW mods that falls in the category of "mods of mods", so you don't have to waste money on multiple (and potentially incoherent) modifications, thus eventually "ghettoing" the host machine, with a spaghetti of cables, and mumbo-jumbo soldering, all over. Nice-and-clean overall (even with resistors in-line, on the MMU ribbon).

 

All I can say: as SWEET as it can be within the constraints and potential of our little machines. KUDOS for all those folks that put such hard work in this wonderful O/S (and to Candle, for his Ultimate1MB).

 

Before this I had tried the SDX on a spare AtariMax 8Mbit cart, but that is like trying to fit a hord of Cheetas into a Fiat 500, so to speak. It is only when running on the Ultimate1MB combo, and after some basic configuration via config.sys and auto*.bat, when you eventually unleash its overall potential. I can only be impressed by how far this machine could go (and could have gone). Beautiful.

 

Now, I do have a few questions, based on my setup (800XL+Ultimate1MB, Nuxx SDrive as boot, and twin IndustGT+RamCharger as floppy):

 

1. So far, it seems that the only speed-factors I can set the SDrive to work with SDX is around $06 to $05. Anything higher, either the SDX and/or the Nuxx seem to lose track of what they are doing (e.g. multiple file copying within the Nuxx or between Floppies and Nuxx, for instance). Not sure if there is anything else I need to tune on SDX, in terms of buffers, etc.

 

2. When cold-booting (both 800XL from OFF-state, and Nuxx, witl all leds lit), and running a simple Autoexec.bat stored in SDRIVE.ATR boot image (with nothing other than screen-color changes, mem /x command, and a couple of SET definitions), the system does correctly detect the presence of the Indus, and makes it spin a bit, but it usually leaves the unit spinning at track 00 indefinitely (no disk read or transfer takes place, just spins). This goes away by issuing a "DIR" on the Indus, and it returns to track 39, and stops, as it should. No biggie, but it is there.

 

3. I wonder if it is possible to take advantage of the RamCharger installed on the Indus, in combination with SDX. Oddly enough, I was able to run Indus "GTSYNC ON" command (I copied the executable out of DOS XL into a working/boot SDX-formatted image). It DOES RUN, and activates track-buffering on the Indus, but both (SDX and INDUS) do not seem to exploit it.

 

4. How can I generate a 16MB or 32MB SDX-formatted image that I can use with my Nuxx SDrive, either as a boot image or as a working image? I tried as far as I could searching here, but could not find anything.

 

Many thanks, in advance, to those that take some time to read and answer some of this questions,

 

F.

 

I was going to try and explain how but I just found a blank one I had instead.

 

http://www.uspsa-clubs.com/misc/BLANKSDX.ATR