SDX447 - What's up with the Ramdisk?

[Dragon375]

I updated all my A8's with SDX 4.47 a while ago. I noticed then that I would get an error during boot that Ramdisk.sys was improperly configured, so I removed it from my Config.sys. Stopped the error message. Yesterday, I was moving some stuff around trying to organize my CF card and could really use a ramdisk as a temp landing spot for some of the files. Well, I wasnt able to get it going. I have a U1MB installed, but D0: doesnt get setup during startup. I tried re-adding Ramdisk.sys, but just get that stupid config error and it doesnt work. What do I have to do to get this working again? Is there updated files that I need to get? Are there new settings I need to apply? I'm at a loss.

[Marius]

Any chance you have something in your autoexec.bat?

 

You did not type in any parameters after ramdisk did you?

 

By default it is DO: (not D0:)

[Dragon375]

Some more info (just to make sure I'm not making a stupid mistake):

 

Exact error message (during bootup):

Config error (152) DEVICE RAMDISK.SYS

 

My Config.sys file:

USE BANKED

DEVICE SPARTA

DEVICE SIO /A

DEVICE ATARIDOS

DEVICE ULTIME

DEVICE JIFFY

DEVICE FATFS.SYS

DEVICE RAMDISK.SYS

 

My AUTOEXEC.BAT:

PATH CAR:,D1:>DOS,D1:>TOOLS

PROMPT $L$P>

 

My RAMDISK.SYS is running off the file in CAR: it is 1405 bytes and dated 10-02-15.

If I rename CONFIG.SYS and AUTOEXEC.BAT to *.BAK, I still get the config error during bootup.

 

So, what am I screwing up?

Edited September 4, 2015 by Dragon375

[fujidude]

I see you're using SDX 4.47. The user guide that is distributed with 4.47 has a section on error codes and causes for them. I went ahead and looked it up and found this:


152 $98 'Not binary file'

1. Attempt to LOAD or run a file that is not a binary load file. There are several scenarios in which this error can occur.
2. The file does not start with a valid binary file header of $FFFA or $FFFF. (The file is a BASIC program, text file, database, etc.)
3. You attempted to run a relocatable SDX command file with the X command. The X command only loads standard Atari binary load files.
4. The end of the file you attempted to load has been corrupted. This is generally caused by incompatible communications software when the file was either uploaded or downloaded from a bulletin board.

Reasons 1, 2, and 3 should be ruled out, although #4 could cause the condition mentioned in #2 as well. So, perhaps it is a corrupted file. In theory, it could also be corrupting memory, since that's where a file is brought into. I am attaching an ARC file (made on the Atari, should be unARCed on the Atari) with the RAMDISK.SYS and RAMDISK.MAN file from my 4.47 settup which is known to work. Failing that, I would get Phaeron's test software and see if you have any memory issues etc.

RAMD447.ARC

[drac030]

Yes, as fujidude wrote, error 152 is "not binary file". This means that your CAR:RAMDISK.SYS file is corrupt. Which in turn means that the SDX in your U1MB is not completely correct. Please refetch the appropriate copy of the SDX from the website http://spartados.com and reflash the SDX ROM.

Edited September 4, 2015 by drac030

[Dragon375]

OK, I gotta say it.. you guys are AWESOME! It was a corrupted SDX. How that happened, I have no idea, but there it is. I reflashed with a known good copy, and suddenly everything works. I would never have guessed that solution. That is the value of this forum Thanks ppl !!!

[fujidude]

Good to hear it's all good now.