SDrive XEX Loader from SD card ? How / What's required?

[jedimatt42]

I picked up an Atari 130XE yesterday, and a SDrive-MAX from The Brewing Company, and the manual states that XEX files can 'load them easily from a microSD card' 

 

From the best of my ability to read Atari lingo, I select a .xex file and assign to D1: and then power on the computer with the 'option' key down to disable basic.  I think I'm supposed to expect a virtual DOS disk to be simulated that auto-loads the chosen .xex file.  A green indicator flashes/blinks to the left of the SDrive screen title bar, with a momentary flash on the D1: row. The Atari appears to do nothing. 

 

I've only tried the .xex files that came on the included sd card...  I can't find any real description of how this works, only references to how 'easy' it is. I assume this is so trival no-one imagines it needs to be written down?

 

Assigning a .atr file works fine, things load... I can't figure out how .xex files are supposed to be 'easily' loaded.  ???

[jedimatt42]

The text here:

 

https://atari8bit.net/everything-sdrive-max/#using

 

says the xex file will be presented to the computer as though it is on a bootable disk.  But that doesn't seem to be true.

[+DrVenkman]

It might help if you described your setup just a bit more (computer model, whether any other devices are on the computer’s SIO chain, and the titles of a few of the XEX files you’re trying to load). You might also tag @MacRorie, who runs The Brewing Academy, or @Mr Robot, who has a website dedicated to all things SDrive-MAX (link is in his signature when he posts). I am away from my Ataris this morning but generally, the device *should* load almost everything you throw at it: ATR disk images, ATX copy-protected disk images, CAS tape files, and XEX executable files. 

 

[jedimatt42]

48 minutes ago, DrVenkman said:

It might help if you described your setup just a bit more (computer model, whether any other devices are on the computer’s SIO chain, and the titles of a few of the XEX files you’re trying to load). You might also tag @MacRorie, who runs The Brewing Academy, or @Mr Robot, who has a website dedicated to all things SDrive-MAX (link is in his signature when he posts). I am away from my Ataris this morning but generally, the device *should* load almost everything you throw at it: ATR disk images, ATX copy-protected disk images, CAS tape files, and XEX executable files. 

 

 

Thanks, Never used an Atari 8 bit before Thursday. 

 

I believe I've fully described my hardware. an Atari 130XE, and the SDrive-max.  That's it. Just that. only those things. nothing else. No mods... no roms. no cartridges. Not even a joystick. 

 

I can load a XEX, but I have to put a DOS .atr in D1: on the SDrive, then the .xex in D2: ( or other ) and then once in DOS, I can L<RETURN>  D2:ABC.XEX<RETURN>    <-- ABC.XEX is a real name of something... it shows a picture of the letters ABC.  

 

@Mr Robot's tutorial page doesn't describe using .xex files.   The link from there to do the docs I linked earlier, also doesn't really describe it... or it doesn't connect the dots... 

 

I don't think I'm supposed to put a DOS in D1, but rather use the SDrive.atr via D0, with the .xex selected in D1:  Then hold down some key combination <inverse>-shift-4 to get into DOS without the SDrive config menu.
I think... Let's go try...

 

[email protected]

[jedimatt42]

When I pick a XEX file, set D0: to boot, hold down <inverse>-shift and power on the Atari computer, I get a menu that I can't show you without 2 more hands... then menu goes away if I release <inverse>-shift.

but I think the options are:

1SDrive(2???, 3Drive+Help),4DOS II+,5(some rom loader I can't recall that far in...) 

 

pressing 4 while the menu is on the screen (I'm still holding <inverse>-shift to keep it on the screen) does nothing. Ignores me...   Holding the 4 and then releasing the <inverse>-shift gets me into the SDrive config and assigns something to D4: cause I'm holding down the 4 key... So, the 4 key functions on this computer.

 

Anyway, I clearly don't understand some basic fundamentals of Atari DOS, and the .xex use case for SDrive. 

 

How do other SDrive users load their .xex files? 

 

[email protected]

[+DrVenkman]

Well here’s what I do (just tried it, to verify the steps). 
 

Load the file you want into the D1: slot. 
 

Verify on the CFG page that you have “Boot D1:” set. 
 

Boot the Atari with BASIC suppressed (holt OPTION at the the start of the boot - usually just a couple seconds is required) 

 

Profit! Er, enjoy your game! 
 

 

[jedimatt42]

2 hours ago, DrVenkman said:

Well here’s what I do (just tried it, to verify the steps). 
 

Load the file you want into the D1: slot. 
 

Verify on the CFG page that you have “Boot D1:” set. 
 

Boot the Atari with BASIC suppressed (holt OPTION at the the start of the boot - usually just a couple seconds is required) 

 

Profit! Er, enjoy your game! 
 

 

Thanks! That is the experience I would expect. But not the experience I get. 

 

For me it chirps a few times accessing the device, once again accessing the file, and then briefly back to the device (based on the visual activity indicator) and then the Atari stares vacantly into the distance.

 

I tried with a .xex file I know I can load from DOS... 

 

[email protected]

[+Mr Robot]

If you can load from DOS, that means BASIC is enabled. Try loading that xex like @DrVenkman showed, but don't hold down Option. 

Edited August 31, 2019 by Mr Robot
I no speaka da truth

[+DrVenkman]

17 minutes ago, Mr Robot said:

If you can load from DOS, that means BASIC is enabled.

I don’t think that follows. If you have a DOS ATR loaded without BASIC, there’s no reason you can’t use the DOS’s Binary Load feature; BASIC doesn’t have to be involved.

[+Mr Robot]

True... I got befuddled, juggling too many things today.

 

[jedimatt42]

I suspect the Arduino firmware is corrupt. 

 

It doesn't even reliably DIR sitting in DOS at a D1: prompt when I pick a .XEX file 

 

It does reliably work with disk image .ATR and tape emulation .CAS.

 

So maybe just the XEX bootloader is goofy.  Probably time to talk directly to @MacRorie

 

I believe this thread is the only explicit documented example of the .xex loader, thanks @DrVenkman !

 

[email protected]

 

 

[+DrVenkman]

I’m not sure a directory command (“A” from DOS 2.5 and DIR from SpartaDOS and similar command line DOSs) will work reliably with XEX files in the drive slot since there’s no actual directory data for the DOS to load. 

 

It might help if you post the XEX file(s) you’re trying to load here to see if their at issue. If you see an uncorrupted interface on the screen and if ATR and CAS files load, then it seems unlikely that *just* XEX file loading is broken. 

[_The Doctor__]

are we sure the D0: dirve is off?

please verify the xe's option key is solidly read in the keyboard self test of the Atari

last, what power supply and power method are you using?

not that it's the case, but have you clipped the two speed killing caps on read and send data sio lines of the XE?

Edited August 31, 2019 by _The Doctor__

[jedimatt42]

@_The Doctor__

Would the powersupply be a problem if ATR files work fine? But it is the USB source connected to a 2.5A outlet

When in the keyboard test, the option key was used to get there, and a nice constant tone is made when I hold it down.

I have not modified the XE in any way. This morning I opened it up to examine it. No modifications have been performed by previous owners.  -- what other symptoms would speed killing caps reveal themselves through?  1080 emulation? I've tried setting it to the 850... turbo tape? both turbo and not turbo work.

 

@DrVenkman

I am pretty sure any none-disk-image file assigned to a drive is supposed to show up as though it is the singular item on a disk. There is the feature that is intended to allow you to move individual files .xex or other data into real disks... 

 

I have tried many .xex files... even ones that load from DOS... but for the sake of testing let's restrict ourselves to these 2: 

Joust.xex

ABC.xex

 

I was able to load ABC from DOS once. Joust, never..   neither work with the xex bootloader that is psuedo composed into a disk image in memory by the Arduino to server up to the Atari.  So far nothing does.

 

[email protected]

 

 

[_The Doctor__]

was the usb power supply provided with the unit?

early experience suggested using the sio power or the actual power jack/battery jack was best... not the usb port for power although some have been known to put a switch inside and do a little surgery (that's a question for Mac though)...

 

ATR's are handled differently than XEX in terms of speed and timing.

 

Edited September 1, 2019 by _The Doctor__

[jedimatt42]

3 minutes ago, _The Doctor__ said:

was the usb power supply provided with the unit?

No, the unit does not come with one. 

 

[email protected]

[_The Doctor__]

don't use usb for power if possible, essentially this is for updating and programming when not connected to the Atari

make sure the caps are not on rd and td in the XE

double check once you have turned off D0: and then set D1: as boot, and then mounted the xex that you have saved the configuration

Edited September 1, 2019 by _The Doctor__

[jedimatt42]

12 minutes ago, _The Doctor__ said:

don't use usb for power if possible, essentially this is for updating and programming when not connected to the Atari

I believe I read this device needs something like 150ma , so I could see how USB would be bad if using a supply that restricts current to the standard 100ma for un-enumerated usb devices. But my supply is regulated and dumb to my benefit in this regard. 

 

12 minutes ago, _The Doctor__ said:

make sure the caps are not on rd and td in the XE

Are we saying that the xex bootloader drives the serial communication differently than the system ROM and may be incompatible with some stock 130XEs?  

 

12 minutes ago, _The Doctor__ said:

double check once you have turned off D0: and then set D1: as boot, and then mounted the xex that you have saved the configuration

I have tried this approach just now, but saving configuration does not save drive assignment information. It only saves information set in the cfg menu. So I didn't expect this to help at all. 

 

[email protected]

[jedimatt42]

So what speed is the xex bootloader using? 

 

[email protected]

[_The Doctor__]

the usb port power can interfere with the device, it has nothing to do with current

[Kyle22]

I power mine from SIO and it works great.

 

Edit: USB port is best reserved for programming the device only.

 

Edited September 1, 2019 by Kyle22
clarity

[+MacRorie]

22 minutes ago, _The Doctor__ said:

the usb port power can interfere with the device, it has nothing to do with current

 

15 minutes ago, Kyle22 said:

I power mine from SIO and it works great.

 

Edit: USB port is best reserved for programming the device only.

 

 

 I have been making and selling S-Drives for months now, all with USB cables to power them, and--if this is the cause of the problem with this one--this would be the first problem reported.

[jedimatt42]

So... :  https://www.technobyte.org/2016/07/power-up-the-arduino-uno/

 

But, I tried a 12v 60w powersupply that I use to power my pico-psu for my Amiga.. No change... not the problem.  

---

I've found the FastIO settings in the SDrive-ng program that run on the Atari ( from D0: ) lowered the speed as low as possible and off ( I presume ) both tests, no change... saved config each time ( or Control-W from the app )  It was defaulting to 69000.  What is that setting in scope for?  Does it impact all disk image emulation? Tape emulation? Does the xex bootloader even pay attention to it? 

 

seems like the xex bootloader on this device is mis-flashed. If I was building something like this, I'd have a binary Atari blob embedded in the Arduino firmware, that I compose with a data blob when the .xex file is selected. Then that is what the Atari would get when it loads the boot sector from D1:  -- another side detail is my upscaler can't handle the s-video output signal generated when this boot loader crashes. 

 

The built in screen says it is running version 1.1b.  Seems like I should re-flash the Arduino. 

 

[email protected]

[_The Doctor__]

If you do the switch mod it wouldn't be an issue... covered in the thread earlier on it wouldn't be and issue... but power through sio and power jack have never been and issue,

 

speed can be turned down to 19,200 to be sure it's not a cap issue

Edited September 1, 2019 by _The Doctor__

[+MacRorie]

37 minutes ago, jedimatt42 said:

I believe I read this device needs something like 150ma , so I could see how USB would be bad if using a supply that restricts current to the standard 100ma for un-enumerated usb devices. But my supply is regulated and dumb to my benefit in this regard. 

 

USB power should be fine.

37 minutes ago, jedimatt42 said:

Are we saying that the xex bootloader drives the serial communication differently than the system ROM and may be incompatible with some stock 130XEs?  

This would be news to me.  Not impossible, but it would be news to me.

37 minutes ago, jedimatt42 said:

I have tried this approach just now, but saving configuration does not save drive assignment information. It only saves information set in the cfg menu. So I didn't expect this to help at all. 

 

[email protected]

D0 is off by default in the firmware now, so this would not change anything.

 

As I said via eBay, I will need to build another one and see if the problem is isolated to yours or is generic to the units.  They get tested by loading the D0 program and then an ATR through that menu.  The second test is to load ATRs from D1.  I then load an XEX to verify subdirectory function, and then they go in the box, but odder things have happened.  Let me build one and will post results.