[Rescue on Fractalus with Intro VBXE patch]

This issue occurs on both of my VBXE 2.x equipped machines.

I've attached the original image if you want to give it a try.

Note that because of a custom SIO loader, the image won't load through a PBI device.

Rescue on Fractalus [Intro Ver.] .atr

[Rescue on Fractalus with Intro VBXE patch]

VBXE users might not get to see the cool spaceship intro, which is also used to check if the GTIA is faulty.

From what I've seen, this version can freeze the VBXE, so you'll have to power it off and on again.

When it boots up, it does this annoying memory cleaning thing that wipes out all the hardware settings, leaving the VBXE registers in a weird state (actually it turns off RGB output, Atari build-in video still works).

A patched image is attached, that skips the cleaning of the upper addresses.

Rescue on Fractalus [Intro Ver.] vbxe patch.atr

[AVGCART]

A bug has been identified in the SDX Supercart version that causes XVER to display it as SIDE2. We are addressing this issue for future versions.

[Online SDX Imager - Learning to Use]

 

19 hours ago, mytek said:

However when I try to add new files it brings up a file selector on my computer, then I select the .COM file I want to add, then click Open, and the file selector window closes but nothing appears to have been added (it doesn't show up in the list, nor consume any free memory).

The "ADD FILES" button should now work (I forgot to implement this feature 😀). Please clear the browser cache first (typically Ctrl+F5).

Note that the online imager (still in beta) is primarily designed for simple modifications of SDX images. Use the Windows tool for advanced scenarios.

[SpartaDOS X 4.49 (release version)]

1 hour ago, LessNick said:

For example, for a project on the photo: Is this has a PCB, schematic and firmware in the public domain (Open Source)?

Judging by the photo, it is a "Super SpartaDOS" PCB. You can search this forum for the authors and ask them directly. I think the referenced site (bitsofthepast) with build instructions and firmware is currently offline.

This is a pass-through (stackable) cartridge, as the original SDX cart from ICD. 

If the pass-through option is not necessary, you can build e.g. SIC! cartridge using schematics, gerber and jed files provided here.

 

[SpartaDOS X 4.49 (release version)]

I do not understand your question. SpartaDOS X 4.4x runs on a variety of hardware and cartridges. You can check this here.

[SpartaDOS X 4.49 (release version)]

IDEPTIME.SYS is available in CAR:, provided you are using an SDX 4.49g image for IDE Plus 2.0.

Make sure you are not using any other SDX hardware (e.g. U1MB) at the same time (you can use XVER to verify this).

[SpartaDOS X 4.49 (release version)]

20 hours ago, flashjazzcat said:

@trub I expect you have been very busy lately

I am afraid this is a permanent situation. ? I will send you PM.

[SpartaDOS X 4.49 (release version)]

@tmp

Thanks for the report. I have uploaded a new version of SDX Imager 3.1.2 which should not crash when there is a problem opening the last file.

 

@Ricky Spanish

Provide more information to let us know what is going on.

 

We will be working on the COPY /R bug with long device specification.

[SpartaDOS X 4.49 (release version)]

The SDX Upgrade Project page should now be operational.

Let me know when there are problems.

[SpartaDOS X 4.49 (release version)]

Sorry for not being able to access the site.

We have to upgrade the website scripts to the newer PHP version.  

I will let you know when it is done.

[SpartaDOS X 4.49 (release version)]

10 minutes ago, a8isa1 said:

I am getting a file corruption when editing CONFIG.SYS.  I'm using SDXImage.exe via wine/linux.

Please check if the problem occurs with the latest version 3.1.1 (I put it on the site a few hours ago).

[U1MB, Incognito, SIDE2, SIDE3, 1088XEL/XLD Firmware 4.0 Released]

On 7/16/2021 at 1:26 PM, flashjazzcat said:

I performed the test described above (booting straight into SDX after pulling the battery and putting it back, to completely clear the RTC), and the SIDE3CLK.SYS driver reports 'SIDE3 clock not present!'. This issue cannot be caused by the loader initialiasing the RTC, since the loader had at no point executed since the battery was reinserted.

 

I then went to the loader (which detected and reset the RTC without problems), set the date and time, and booted into SDX again. It still failed to detect the RTC. I will speak to Trub about this.

Currently, after replacing the battery, the driver should be forced to load with the /F option (SIDE3CLK.SYS /F). Then the time can be set with DATE and TIME commands.

This will be corrected in the next edition of SDX (along with other fixes).

 

[#FujiNet - a WIP SIO Network Adapter for the Atari 8-bit]

@tschak909I am aware of this SIO command and already tried it

However, for now I want to keep the TTR generic. Perhaps I will add a command line switch invoking CP/M for FujiNet/ATR8000.

 

@DrVenkman By holding the keys (e.g. Ctrl+Shift =, apparently on the real hw) you may cycle thorough different colors. For example, one may get an amber-like dumb terminal feeling 

I had some problems with configuring the WS 4.0 supplied in the Big RunCPM ZIP. So I downloaded another copy and then it was able to configure it for ADM-31. There were no problems with WS 3 tough.

 

[80-column Applications?]

On 1/23/2021 at 8:29 PM, DrVenkman said:

 

Well, I got TrubTerm 0.5 working and I can see text on my screen, but I can't figure out why FujiNet doesn't respond to the ATCPM command. That terminal appears to be hard-coded to emulate the ADM-3A terminal; all my attempts to enter CP/M via the "ATCPM" command just move the cursor around without actually sending the string to FujiNet. 

 

I wonder if @trub or @tschak909 might have any insight.

 

[#FujiNet - a WIP SIO Network Adapter for the Atari 8-bit]

I was asked for it, and here it is

 

TTR 0.1 for R1: (aka Trub Terminal R) is ready for testing at trub.atari8.info/cpm/TTR.ZIP

It is in fact a converted TT with the Indus CP/M routines removed and using CIO (via RS232 R1: driver) instead of the Indus-specific protocol.

 

Remarks:

- requires S_VBXE.SYS (or RC_GR8.SYS) for 80-column display

- Lear Sieger ADM-31 terminal emulation (as in Commodore 128, Kaypro and other CP/M systems)
- 9600bps communication speed (currently fixed)

- can also be used with Atari 850 (presumably PR: connection too) to communicate with other devices (apart from FujiNET)

 

Usage:
1. Connect the device (FujiNET, Atari 850) to the SIO port (preferably disconnect the others).
2. Install the R1: device driver (preferably RS232.COM for SpartaDOS X).
3. Launch TTR.
4. (FujiNET) Write ATCPM <Return> to run the built-in CP/M.
5. (FujiNET) Execute EXIT command to shut down CP/M before closing the terminal.
6. Full-screen software e.g. WordStart, Turbo Pascal, etc. should be configured
   for ADM-31 (or ADM-3A) terminal to get full benefit from the terminal.

7. Back to DOS: Ctrl + Shift Q
8. (VBXE) Adjust font colors (Ctrl + Shift -,=) and background (Ctrl + Shift 9,0), e.g. you may have pink fonts like in C128 CP/M
9. (VBXE) Save color settings in the configuration file with Ctrl + Shift S

 

Let me know in case of problems.

 

[Altirra 3.90 released]

18 hours ago, Faicuai said:

(UPDATE: even TrubTerminal for CP/M should do well re-implemented for XEP80 / Ultra drivers).

Once I prepared a terminal prototype for XEP. However, I had to abandon it, because the speed of displaying characters through the joystick port is 15.7 KBit, while communication with CP/M-enabled drive is 19.2 KBbit. This causes characters to be lost. So the Indus CP/M performance should be slowed down to work properly with XEP. I don't think it's worth the effort.

[SpartaDOS X 4.49 (release version)]

13 hours ago, Mark2008 said:

There is another disk called SDX449e_side2.atr, I try to open that, it says unsupported dos format, and shows nothing.

Just mount this as D1: and boot. SDX flasher starts automatically.

[SIDE 3 preorder]

23 hours ago, flashjazzcat said:

But while testing battery removal/insertion, I noticed that the SDX RTC driver cannot recognise the real time clock unless the loader has already set it up.

I'll let Trub know, anyway, and release the updated loader shortly.

Thanks for the info. I will update the clock driver accordingly.

However, it seems that the clock chip can also be initialized currently by forcing the driver to load (SIDE3CLK.SYS /F) and then setting TIME & DATE. 

 

@KPeterI am unable to reply to your email, because either mine or your email account is blocked by the server. However it seems that your problem with finding the link is solved by helpful @Frankie.

[SIDE 3 preorder]

For all interested, the updated alpha version of SDX 4.49e (dated December 2, 2020) is available at the link in the post above.

[SIDE 3 preorder]

9 hours ago, flashjazzcat said:

It appears that SDX is still using the 'old' scheme (which required explicit management of the windows). This is presumably the simple explanation for the whole screen garbage matter.

I can only confirm this ?

Currently both windows A and B are set regardless of the type of the cart.

[SIDE 3 preorder]

11 hours ago, KPeter said:

When I run BASIC XE 4.2 ROM from SIDE3 Loader and restart SDX 4.49e and activate TD, after CAR

command the Extension file is loading with short "colored junk" on the monitor and the BASIC starts up also, seemingly functional, but

the picture is blinking with 1 second period with colored fade mosaic, how the DATA/TIME bar on the top is updating.

First, I assume that you have read the "Using BASIC XE Extensions" section in the SpartaDOS X manual.
Second, we are investigating this problem, but it may be related to Basic XE's incorrect handling of NMI interrupts, which may result in the incorrect operation of VBLK and DLI interrupts when using extension routines.

[SIDE 3 preorder]

We do not normally do this, but here is a SDX 4.49e (alpha) development version for SIDE3 available for download.

 

We usually release versions after good testing, even beta versions.

So, you use this version at your own risk, and since it contains work-in-progress code, some things may not work. And it is not just about SIDE3 support.

Therefore, the official version 4.49e will not be available on our website until this work is completed.

 

Please also note that we develop SDX in our spare time as a non-profit hobby.

[Odd behaviour loading 180.xex via Side3]

TD is the same (from 2016). Please provide the image with the newer date for comparison.

 

However the problem is not with the TD, but with the SDX driver for the clock chip in SIDE3.

Unfortunately, I don't have a working SIDE3 at the moment to update it.

 

Also, the SDX version 4.49e placed by the manufacturer in SIDE3 should be considered an alpha version.

[Opening a dialogue for SpartaDOS Source Code]

Although not shown in the linked photos, mono is also very much involved in the project :)