Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


drac030 last won the day on July 26 2016

drac030 had the most liked content!

Community Reputation

1,559 Excellent


About drac030

  • Rank
    River Patroller
  • Birthday 07/28/1970

Contact / Social Media

Profile Information

  • Gender
  • Location
    Warszawa, Poland

Recent Profile Visitors

18,623 profile views
  1. I have uploaded version 0.94 to the same address as above. One major new thing is that ELSA is now able to generate SpartaDOS X relocatable binaries. I seem to have managed to make SpartaDOS X support more flexible than in MADS (let alone FA), for example, all 65C816 instructions and addressing modes will generate fixups, where applicable; also, labels declared as external symbols can be used in arithmetic expressions, the result of such an expression will then generate the external reference record when used, e.g. .xref COMTAB lbuf = COMTAB+$3f ... ... lda lbuf "lda lbuf" will cause the XREF record for the symbol "COMTAB" to be inserted into the object file. Also, fixups work between program blocks loaded to different 64k segments. To use this one will need to load an additional extension module, which will come with next beta release of SDX (on the Toolkit).
  2. It will not. Most SDX utilities and external commands (like all except one or two) are in the relocatable binary format which 3.2 does not understand, and require the SDX Library, which 3.2 does not contain.
  3. Yup, it has always been so in SDX: "path to root directory", when at the root, it is NUL.
  4. I know, I am just saying that it is no matter that the manual says "Dx:", because this does not forbid using "D:" anyways. Of course SD 3 (maybe except 3.2g) has no concept of current drive IIRC, so what is "current" must be established by other means.
  5. That is no matter: "Dx:" in SpartaDOS X also means "D:" (then x = current drive and is implied).
  6. It was said above that SpartaDOS should use the current drive. It might be worth then taking a look a the code which gets the information on the current drive from the system and how it is done.
  7. After the recent, much revealing discussion on the left margin issue in CC65 libs, I would not be much surprised if it was the latter. Yes, "\" and ">" are equivalent as path separators in SDX.
  8. To be honest, I do not know - my first SpartaDOS years back then was SpartaDOS X and so it remains until this day. The CIO is not often used in SDX utilities, so I just checked, if XIO 48 works as advertised in the SDX User's Manual, section 6.3.18. But it seems so: The program: test.zip
  9. It seems that the limit of TSR programs initialized at reset has been exceeded. It is pretty short I admit (5 or so), SDX drivers do not need it, but OS drivers (E: and such) do, you install four of them... Try installing TSR.SYS (it is to be found on the Toolkit disk) as one of the first programs after SPARTA.SYS/SIO.SYS/[clock].SYS, then see if it helps.
  10. I cannot see any problem with soft reset, everything seems to survive. Could you provide steps to reproduce? Your post #163 was excellent
  11. @drpeter about the TD bug, try this: tdfix.com and see if it is any better.
  12. Yup, User's Manual: But the second issue is real and I will have to take a look at it. There is definitely something depraved there (and it is related to TD _again_, I am seriously about to dislike this program).
  13. XEP80 fans would probably love the updated XEP80.SYS driver in current SDX, which is accompanied with a tool to tune the display parameters live. I am not sure, though, if the current beta is ready to be released. @phaeron could you add a separator after BRL?
  14. Unless there is more out in the wild than I have, the "original build tools" consist of these files: 1) XASM65.EXE, or "ICD Cross Assembler", serial number #0001 2) MAKECAR.EXE 3) MAKEBIN.COM The first two are MS-DOS 8086 executables and do not work on Windows. Both are written in Borland Turbo C. There is the source module for MAKECAR.EXE. Also there is a source module for XASM65.EXE, named XASM65.C, but, judging from the project file XASM65.PRJ, it is only one source file out of the total of about 20 other *.C and *.H files, and apart of that one all others are missing.
  • Create New...