Author Topic: SymbOS 3 released  (Read 4994 times)

0 Members and 1 Guest are viewing this topic.

Offline Prodatron

  • 6128 Plus
  • ******
  • Posts: 799
  • Country: de
  • Back on the Z80
    • index.php?action=treasury
    • SymbOS SYmbiosis Multitasking Based Operating System
  • Liked: 1003
Re: SymbOS 3 released
« Reply #20 on: 21:07, 31 August 17 »
I think I asked previously, but I'm not sure I got a definitive answer. Is it possible to keep the Boot disk in the internal drive and have SymbOS access its other applications from the external drive? I seem to remember the OS can read 720k MSDOS floppies, and that would be useful for people without mass storage (well, me).
Do you have a usual 3,5" disc drive as B or an HxC?
- if it's a disc drive, yes, you can copy all stuff onto a FAT12 720K disc and access all files there directly after booting SymbOS (Start -> Run -> Browse -> select Drive B etc.)
- if you use a HxC you can even access the FAT32 filesystem of the SD card directly. It's nearly as slow as a floppy drive (as it's still using the FDC), but you have space for 32GB or more. You can choose this option in the control panel -> mass storage -> floppy disc -> dropdown: HxC SD card at B.

GRAPHICAL Z80 MULTITASKING OPERATING SYSTEM

Offline remax

  • 6128 Plus
  • ******
  • Posts: 974
  • Country: fr
  • Liked: 310
Re: SymbOS 3 released
« Reply #21 on: 22:04, 31 August 17 »
I am so sorry for this!

At least i didn't panic. As it was only the header of the partition that was killed, any good recovery oftware allows to recover all the files in 5 minutes.


I think I fixed this problem in january. The M4Board SD card driver is now able to detect, if there is an MBR or not. But it will only do it, if you choosed "primary partition 1". Other settings won't take care.
But unfortunately I forgot to set this in the SYMBOS.INI in the release package for the M4Board, it was still set to "unpartitioned" (like my own SD card).

I uploaded the CPC package again with the correct SYMBOS.INI file for the M4Board.
It would be great of you could test it again!


Problem solved  ;D

Offline Prodatron

  • 6128 Plus
  • ******
  • Posts: 799
  • Country: de
  • Back on the Z80
    • index.php?action=treasury
    • SymbOS SYmbiosis Multitasking Based Operating System
  • Liked: 1003
Re: SymbOS 3 released
« Reply #22 on: 00:03, 01 September 17 »
Problem solved  ;D
Thanks, that's good to hear!!

GRAPHICAL Z80 MULTITASKING OPERATING SYSTEM

Offline khaz

  • 464 Plus
  • *****
  • Posts: 468
  • Country: fr
  • Liked: 229
Re: SymbOS 3 released
« Reply #23 on: 01:50, 01 September 17 »
Do you have a usual 3,5" disc drive as B or an HxC?
- if it's a disc drive, yes, you can copy all stuff onto a FAT12 720K disc and access all files there directly after booting SymbOS (Start -> Run -> Browse -> select Drive B etc.)
- if you use a HxC you can even access the FAT32 filesystem of the SD card directly. It's nearly as slow as a floppy drive (as it's still using the FDC), but you have space for 32GB or more. You can choose this option in the control panel -> mass storage -> floppy disc -> dropdown: HxC SD card at B.

Right, Of course I asked before even trying.

In 2.1, you had two dsk, main and apps, and you had to swap between the two in order to access different OS tools. That was super annoying. But it seems 3.0 works differently in that regard? You boot with load.dsk and swap for AppsStandard.dsk once loading is done, and there is no need to swap any more? If so, that's super cool.

[edit] ok, I believe I was referring to SYSTEM PATH. Have you considered allowing more than one entry? the internal drive can only contain the core OS tools, and being able to automatically load a default application on the other drive would be nice.
« Last Edit: 03:29, 01 September 17 by khaz »

Offline khaz

  • 464 Plus
  • *****
  • Posts: 468
  • Country: fr
  • Liked: 229
Re: SymbOS 3 released
« Reply #24 on: 15:52, 01 September 17 »
Do you have a usual 3,5" disc drive as B or an HxC?
- if it's a disc drive, yes, you can copy all stuff onto a FAT12 720K disc and access all files there directly after booting SymbOS (Start -> Run -> Browse -> select Drive B etc.)
- if you use a HxC you can even access the FAT32 filesystem of the SD card directly. It's nearly as slow as a floppy drive (as it's still using the FDC), but you have space for 32GB or more. You can choose this option in the control panel -> mass storage -> floppy disc -> dropdown: HxC SD card at B.

I'm trying with a real floppy drive and a 720K disk.

First thing, I have a problem accessing stuff on the internal drive, like SymCommander, with a floppy in drive B and if the motor isn't already spinning: it gives me an error code 26 (device is not ready). If I close the dialogue box and start again quickly enough so that the motors are still spinning, then the application loads. There is no error when trying to access stuff on drive B. Amsdos has no problem either way.

I've tried accessing a 720K, MSDOS-formatted floppy, but I couldn't. I get an error code 06 (error while sector read/write), and the size/file info in SymCommander isn't updated. This is not related to the motor error. nevermind that, the floppy was dead.

I have no problem using my HxC, both in floppy emulation mode and direct access mode.
« Last Edit: 16:38, 01 September 17 by khaz »

Offline Gryzor

  • Administrator
  • 6128 Plus
  • *****
  • Posts: 14.174
  • Country: gr
  • CPC-Wiki maintainer
    • CPCWiki
  • Liked: 2511
Re: SymbOS 3 released
« Reply #25 on: 16:16, 01 September 17 »
Damn.... I mean, where to even start??!


Now, when's the c64 version coming? :D


(anyone worked with GeOS?)

Offline ComSoft6128

  • ..................................
  • Supporter
  • CPC6128
  • *
  • Posts: 187
  • Country: scotland
  • CPC THEN CPC NOW
  • Liked: 98
Re: SymbOS 3 released
« Reply #26 on: 13:58, 03 September 17 »
Hi Prodatron,


I have a 6128 Plus with a 3.5 B drive and Parados on cartridge, the format used for the 3.5 discs is Romdos D20 - can Symbos read and write to this disc format?


I have more than 200 of these discs dating from 20 years ago and plan on using the M4 board and Symbos to retrieve most of the files that are still viable and then transfer them to a PC for permanent storage.


As this is not a hypothetical problem for me I am more than interested in any info you could offer.


Many Thanks,


Peter


Offline Ygdrazil

  • Global Moderator
  • 464 Plus
  • *****
  • Posts: 472
  • Country: dk
  • Liked: 37
Re: SymbOS 3 released
« Reply #27 on: 14:04, 04 September 17 »
Having played around with the SymbOS 3.0 I am absolutely  impressed!!!!  :P The level of detail and effort in doing version 3.0 is awesome! Must have a M4 soon....

A C64 version! I doubt that will ever happen, but I am still hoping to see a version for the Amstrad NC!

Regards,
/Ygdrazil


Damn.... I mean, where to even start??!


Now, when's the c64 version coming? :D


(anyone worked with GeOS?)

Offline Prodatron

  • 6128 Plus
  • ******
  • Posts: 799
  • Country: de
  • Back on the Z80
    • index.php?action=treasury
    • SymbOS SYmbiosis Multitasking Based Operating System
  • Liked: 1003
Re: SymbOS 3 released
« Reply #28 on: 23:41, 04 September 17 »
In 2.1, you had two dsk, main and apps, and you had to swap between the two in order to access different OS tools. That was super annoying. But it seems 3.0 works differently in that regard? You boot with load.dsk and swap for AppsStandard.dsk once loading is done, and there is no need to swap any more? If so, that's super cool.
Regarding this there is no difference between 2.1 and 3.0.
- The boot disc contains everything you need to load during booting (well, that's obvious :) ). This includes the SymbOS core files (SYM., SYMBOS.BIN), the INI file, the SymbOS extension + ini, the screen saver, the background picture and the widgets (everything is optional of couse).
- after booting, you don't need the boot disc anymore and can replace it with any app disc or whatever. As long as you don't change the SymbOS configuration.
- in the past the control panel was located on the boot disc as well. So you could do some changes directly after booting and saved it without the need to swap discs.
- since SymbOS 3 there isn't enough space on a 178K amsdos data disc anymore for storing all compontens needed for booting on expanded systems PLUS the control panel. So I decided to put the Control Panel application files on the "standard application disc" as well. That's the only difference between 2.1 and 3.0.

But there is no need for disc swapping anyway as soon as you don't need to change the SymbOS config anymore. You can store all stuff you need after booting on another disc (and drive) and access it directly. It is not required, that the "system path" is the same like the boot drive. You can set it to drive B as well, if you boot SymbOS from drive A. And anyway the system path is just a shortcut (to keep links smaller). You can set the icon links freely to any location. When using the new Extended Desktop there are no limitations for links anymore.

In your case, I would keep the boot disc in drive A and put everything else on a FAT12 720K disc in drive B and modify the links of the desktop icons and startmenu entries. No need for disc swapping at all. Or even better, use the FAT32 SD card of your HxC as another drive directly and have unlimited space and the possibility to exchange files with a PC very easy! :)

GRAPHICAL Z80 MULTITASKING OPERATING SYSTEM

Offline Prodatron

  • 6128 Plus
  • ******
  • Posts: 799
  • Country: de
  • Back on the Z80
    • index.php?action=treasury
    • SymbOS SYmbiosis Multitasking Based Operating System
  • Liked: 1003
Re: SymbOS 3 released
« Reply #29 on: 23:49, 04 September 17 »
First thing, I have a problem accessing stuff on the internal drive, like SymCommander, with a floppy in drive B and if the motor isn't already spinning: it gives me an error code 26 (device is not ready). If I close the dialogue box and start again quickly enough so that the motors are still spinning, then the application loads. There is no error when trying to access stuff on drive B. Amsdos has no problem either way.
Does this only happen, if you have a floppy in drive B and try to access the internal drive A? Never heard about this... If there is no floppy in drive B it doesn't happen?

GRAPHICAL Z80 MULTITASKING OPERATING SYSTEM