Author
| SymbOS MSX multitasking operating system - help needed!
|
Sonic_aka_T
msx guru
Posts: 2268 |  Posted: July 03 2006, 02:09 |
Quote:
| Quote:
| does it also include saving the configuration?
|
ah, yes, that was what I forgot to ask. it works now, but I need to know one thing: how do I find out the drive letter, where a program was started from in Msx-Dos?
|
Uhm, while SD-Snatcher's function is very cool, uhm, well, I prefer LD C,$19 | CALL $0005 which would return the drive letter in A (and L). The advantage of that method is that it also works on DOS1, which some people might still be using. |
|
arnold_m
msx lover
Posts: 81 | Posted: July 03 2006, 19:00 |
Quote:
| Quote:
|
ah, yes, that was what I forgot to ask. it works now, but I need to know one thing: how do I find out the drive letter, where a program was started from in Msx-Dos?
|
Uhm, while SD-Snatcher's function is very cool, uhm, well, I prefer LD C,$19 | CALL $0005 which would return the drive letter in A (and L). The advantage of that method is that it also works on DOS1, which some people might still be using.
|
Uhm, well, this bdos call only gives you the defaullt drive, but the program may be on another drive as in
A>b:loadit
Under DOS2 the loader may also be found in the search path.
The $19 bdos call is probably the best you can do under DOS1, but under DOS2 reading the PROGRAM environment variable has some real advantages.
If the loader is to work under both DOS1 and DOS2 the best would be to use the PROGRAM environment variable if the program is run under DOS2 and the $19 bdos call otherwise.
Come to think of it, the $19 bdos is not even needed to open a file on the default drive. |
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 20:04 |
Well, I am using the DOS1 $19 call for the moment now.
Can't I find the start string somewhere in the memory in DOS1? I think I saw it somewhere in a memory dump. Then I could check for ":" as second char. I will upload a new version in about 30 minutes.
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 20:35 |
Here is the new version:
http://www.symbos.de/files/symbosmsx.zip
What's new:
- there is about 16K more memory (makes more fun now on my unexpanded 128K Philips NMS8250, but unfortunately still not enough to start two bigger applications like SymCommander at the same time - I am waiting for my TurboR  ).
- saving the config works now. Please note: SymbOS will load/save the config always from the drive you started it. That means the drive letters should be the same in MSX-DOS and SymbOS. If you have a Sunrise IDE it will first search for the config on drive C (sunrise IDE partition 4 or see below). You may first create a config (symbos.ini) on your disc drive and then copy it to IDE.
- new command line paramater "f" for specifying the FDC.
Syntax: f[FDC type (FDC slot (FDC subslot))]
type can be:
0=no FDC present (use this if you have an unsupported FDC to avoid crashes!),
1=WD2793/Philips,Sony (the only one tested on a real machine),
2=MB8877A/National,
3=WD1793/SVI,
4=Microsol (not working yet),
5=TC8566AF/Panasonic (not implemented yet)
If you don't specify a slot/subslot it will take the first slot/subslot, where a disc rom is present, which is not the sunrise IDE.
If you don't specify a FDC at all, type 1 will be assumed.
Example:
A:>SYMBOS f1 -> WD2793
A:>SYMBOS f31 -> WD1793 in Slot1
A:>SYMBOS f232 -> National in Slot3, Subslot2
- new command line paramater "p" for specifying the IDE partition.
Syntax: p[partition number]
Number can be 0 (drive is not partitioned) or 1-4.
If you don't specify a partiton at all, partition 4 will be assumed.
- the LED of the second disc drive won't burn all the time. I hope this also works on other machines and not only on my NMS8250.
Please replace the old control panel versions (escpecially APPCP.EXE and APPCPDSP.EXE), as they will not run with the new version.
Hope it will work on your machines. Please report all problems...
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 22:04 |
Every MSX has a very useful reset key, but I would like to know, what is the best way to reset a MSX, when the internal OS is complete destroyed (like in SymbOS). And is there a way to skip the logo at the beginning, so that the machine tries to boot MSX-DOS at once or starts basic? Or can I start basic directly and skip the MSX-DOS boot try?
Currently I am on the edge with the FDC shit, and I want to do some other things like replacing some Amstrad specific parts.
|
|
PingPong
msx professional
Posts: 978 | Posted: July 03 2006, 22:23 |
Quote:
| Every MSX has a very useful reset key, but I would like to know, what is the best way to reset a MSX, when the internal OS is complete destroyed (like in SymbOS). And is there a way to skip the logo at the beginning, so that the machine tries to boot MSX-DOS at once or starts basic? Or can I start basic directly and skip the MSX-DOS boot try?
Currently I am on the edge with the FDC shit, and I want to do some other things like replacing some Amstrad specific parts.
|
In basic we msx users do:
Def Usr = 0: a=usr(0)
This causes a reboot.
Loading all z80 registers with default power on values, resetting slot memory regs and issuing a ld hl,0 jp (HL), does not work?
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 23:03 |
Ok, I just would like to know which slot I have to make visible for page 0.
And I wonder if it's also possible...
- to boot MSX-DOS directly without having the MSX logo at the beginning
- to start basic directly without the other stuff in front
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 23:05 |
Quote:
| Ok, I just would like to know which slot I have to make visible for page 0.
|
Erm, sorry, of course it should be slot 0/subslot 0. Now only the two other questions are left... |
|
spl
msx professional
Posts: 738 | Posted: July 03 2006, 23:14 |
DELETED
|
|
spl
msx professional
Posts: 738 | Posted: July 03 2006, 23:16 |
DELETED
|
|
spl
msx professional
Posts: 738 | Posted: July 03 2006, 23:19 |
Well... sorry, I didn't updated well Symbos. Now yes, it works great  Now with "save settings" working it's usable for everyday use. |
|
spl
msx professional
Posts: 738 | Posted: July 03 2006, 23:37 |
Well, I've found a real bug: if you open a sgx or a st2, symbos opens SymSee or SymAmp, but image or music are not opened.
Also, if you open Control Panel, its icon is always on the task bar and then if you open another app, you only see Control Panel icon.
Yours,
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 23:52 |
|
|
Prodatron
msx master
Posts: 1109 | Posted: July 03 2006, 23:57 |
Quote:
| Well, I've found a real bug: if you open a sgx or a st2, symbos opens SymSee or SymAmp, but image or music are not opened.
|
You are right!... It could be because of the memory rearragement (16K more memory free). I will try to fix it today.
Quote:
| Also, if you open Control Panel, its icon is always on the task bar and then if you open another app, you only see Control Panel icon.
|
This I can't reproduce. What are you exaclty doing? I started the control panel, then the task manager and see both in the task bar. Then I can close both and everything is fine. |
|
Prodatron
msx master
Posts: 1109 | Posted: July 04 2006, 00:11 |
Quote:
| Well, I've found a real bug: if you open a sgx or a st2, symbos opens SymSee or SymAmp, but image or music are not opened.
|
Thanx for the hint, I fixed it. You can download the working update at the same location. Hope this was the last bug caused by the new memory structure, if not, please report. |
|
|
|
|
