CPCWiki forum

General Category => Applications => Topic started by: SOS on 01:18, 23 March 18

Title: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 01:18, 23 March 18
I'm finished, attached is my latest version.


Key Features:
- Detect (nearly) all Fat16+Fat32-Partitions on your CF-Card, DOM, etc. (1st Partition please). Prefered is Fat32 (should be faster with Save-Commands)
  You can format the media with e.g. Windows and fill it with data.
- Partial longnames.
- the usual RSX like |MD, |RD, |REN,....
- |DIR + |CD accepts Wildcards
- DSK-Support
- Compatibility should be high (i hope so  ;) ) - but i'm playing around with a lower-rom-patch to increase compatibility.
- Burn to ROM7 is allowed (max. compatibility), with (or without) AMSDOS as ROM15 (best compatibility) or below 15.
- ROM7 without Floppy-ROM is allowed too, compatible with Duke's lower-ROM-Patch

The ROM must be placed below (if used) AMSDOS, M4DOS, PARADOS
Not compatible with ACMEDOS at the same time.

YANCC-User should be update to the latest version.


History:
Added 23.03.18: CubeIOS180318b - first release - The ROM had fled  :-[ but i found it (please reload the file, sorry)
Added 15.04.18: CubeIOS140418b - Bugfixing + flexible ROM configuration allowed, changed handling of |A (see textfile)
Added 30.08.18: FormatBAS - the upcoming next release(s) will no longer include "Format.bas"
Added 01.10.18: CubeMDOS230918b - Renamed ROM, Support of Symbiface 3, HXC+Gotek (see Readme) + Small Bugfixes
Added 04.10.19: CubeMDOS290919b - A lot of Bugfixes
Added 20.01.20: CubeMDOS120120b - DSK-Support (read only) +  Bugfixes
Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: Ast on 14:20, 23 March 18

Well done SOS !
Happy to see other os will be ready for our beloved x-Mass !
Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: Kris on 19:39, 25 March 18
I just give it a trial but formatting a 128Mb DOM give wrong size results...If I choose FAT16 format then I own 400Mb ??
Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: SOS on 21:01, 25 March 18
I just give it a trial but formatting a 128Mb DOM give wrong size results...If I choose FAT16 format then I own 400Mb ??
At the moment i have no check against the real-media-size.

You can't choose a format with higher capacity as your media can fit!
So you must choose a correct format, eg.
128MB-DOM = 1st ACMEDOS-Format (128MB),
256MB-DOM = 1st ACMEDOS-Format (128MB),
512MB-DOM (or higher) = You can use all formats (128MB,400MB,450MB)

Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: Fessor on 22:23, 10 April 18
Cool. Works great for Winapes IDE-Device.

Created empty Image via
dd if=/dev/zero of=cpcide.img count=128 bs=1M, set to W95 FAT16 (LBA) with fdisk and initialised with mkfs.vfat cpcide.img

Mounted it in Winape and could Save Files to it.

Created Entry in /etc/fstab to mount it parallel in Linux. Copying Files from Disk-Images to the IDE-Image via ManageDSK works like a charm.

Must now look, how to get it transferred to the XMASS-DOM. Are there Adapters for USB available to Mount the DOM on a PC?



Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: SOS on 22:43, 10 April 18
Must now look, how to get it transferred to the XMASS-DOM. Are there Adapters for USB available to Mount the DOM on a PC?
http://www.cpcwiki.eu/forum/news-events/x-mass-a-mass-storage-expansion-for-all-cpc/msg140765/#msg140765 (http://www.cpcwiki.eu/forum/news-events/x-mass-a-mass-storage-expansion-for-all-cpc/msg140765/#msg140765)
but i will recommend:
http://www.cpcwiki.eu/forum/hardware-related/cf-card-adapter-for-x-mas/ (http://www.cpcwiki.eu/forum/hardware-related/cf-card-adapter-for-x-mas/)
buuuut, not all CF-Cards accepted from the XMASS...
Title: Re: CubeIOS / FAT16+FAT32-IDE-OS - ROM for the Amstrad CPC's with XMASS
Post by: SOS on 12:46, 15 April 18
New update, see 1st post.
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface3,HXC/Gotek
Post by: SOS on 07:40, 01 October 18
New Version released (Symbiface 3-Support, HXC/Gotek & Small Bugfix).
My big thanks (again) to Audronic & 00WReX for beta-testing  :D
(bohh, they have good,strong nerves  ;) )
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: GUNHED on 17:13, 01 October 18
Congrats to your update. Let me ask you few questions.

- Is your DOS compatible to X-DDOS and / or to R-DOS?

- What's the difference to support SF2 and SF3? There is no SF3 docs out there? Can you tell a bit?
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 17:47, 01 October 18
- Is your DOS compatible to X-DDOS and / or to R-DOS?
- What's the difference to support SF2 and SF3? There is no SF3 docs out there? Can you tell a bit?

X-DDOS / R-DOS: Never tested   (Edit: No, both did not run, i Need only 0-1 leading DOS-ROM, like e.g. AMSDOS on 7 or 8, Parados on 7, or no DOS-ROM)

SF3 has an USB-Interface.
I have an Prototyp-Card from TMTLOGIC.
He has documented the programming Interface.

The core functions which he provides are boring easy, so my actual ReadLBA-Sector looks:

Code: [Select]

        ld bc,#FD41
ld a,1
out (c),a ; reset pointers1
; -----------
ld bc,#fd43
out (c),h
out (c),l
out (c),d
out (c),e
;LBA number Sector write (max 32)
ld a,1
out (c),a
ld bc,#FD41
ld a,51 ; read sector from usb stick
out (c),a ; reset pointers1
SYMBIFACE3_ReadSector1
    ; wait processing 0 = oke 1 = busy 2 = error
in a,(c)
cp 0
jr z,SYMBIFACE3_ReadSector1_Exit
cp 1
jr z,SYMBIFACE3_ReadSector1
; error-state, so exit
jr SYM3_READ_ERROR
SYMBIFACE3_ReadSector1_Exit

call GetAMSDOSWorkingBufferInIX ; OUT: HL=Buffer, All Register preserved
ld bc,#fd43
ld de,512
SYMBIFACE3_ReadSector2
in a,(c)
ld (ix),a
inc ix
dec de
ld  a, d
or  e
jr nz,SYMBIFACE3_ReadSector2
in a,(c)
cp #1a
jr nz,SYM3_READ_ERROR

Because of the stable CubeROM for XMASS, I "only" added an autodetect & differs in the core-functions (like):
AutodetectSymbiface3
If Symbiface3Found then begin
  ReadLBASectorFromSymbiface
  exit
end
ReadLBASectorFromXMASS

Hmmm, maybe i will Play in the next days with the RTC.... (when it's functional in my prototyp-Card  ::) )
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: GUNHED on 13:26, 02 October 18
That's pretty neat actually. So adding USB seems more easy (and fun) than IDE.

About R-DOS... It should be at ROM position 1, because it "just" adds commands for RAM drive C and "should" be compatible with CubeDOS.
Well, I already downloaded the new update, but have some issues here with my hardware setup (only temporary I hope).

If you have any information about how to read / write the SF3 RTC it would be nice to post it here.  :)
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: HAL 6128 on 16:25, 02 October 18
Max. 32Bit LBA addressing possibilities means 3 TB or 28Bit 128GB? (...not an important question for a CPC) :P
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 17:07, 02 October 18
Max. 32Bit LBA addressing possibilities means 3 TB or 28Bit 128GB? (...not an important question for a CPC) :P
32 Bit = 4294967295 Sectors can be assigned, size 2199023255040 Bytes = 2,19 TB 
(never tested on my CPC, whether the whole range can be correctly assigned  ;) )
=> I'm using 32 Bit for Symbiface 3, HXC/Gotek and IDE 24 Bit :o (=16777215 Sec's = 8,5 GB  >:(  ).

I think, i must set this to my todo-List, should be 28 Bit (=137 GB) or more :-[

Edit: I'm blind (can't read my own source code), IDE are supported up to 28 Bit (=137 GB) (cross checked with WinApe) all ok  :) 
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: netmercer on 02:07, 13 November 18
Hi SOS,
I attempted to use CubeMDOS 23.09.18b in order to manage Toto's XMASS.

First: I can't enter ParaDOS menu any longer with RSX |DRIVE.
I know the RSX |DRIVE is taken by CubeMDOS, but perhaps there is another way to enter the menu of ParaDOS.

Second: Some subfolders shows as name "eEUERO~1" (with YANCC) in place of their real name.
(with pure CubeMDOS on the commandoline the first letter is instead of "e" a  (&HE5) Symbol)
This happens both on XMASS and on HXC Gotek with RSX |HB.

My configuration on CPC6128:
ROM8: LAUNCH 14.04.18b
ROM7: AMSDOS
ROM6: ParaDOS 1.1
ROM5: CubeMDOS 23.09.18b
ROM4: YANCC 14.04.18b

Perhaps I'm doing something wrong.

By the way, I'm using YANCC for more than an year and I really won't miss it. Thanks  :-*

Best regards
netmercer
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 09:33, 13 November 18
Moin netmercer   :)
First: I can't enter ParaDOS menu any longer with RSX |DRIVE.
I know the RSX |DRIVE is taken by CubeMDOS, but perhaps there is another way to enter the menu of ParaDOS.


Yes |DRIVE is caught by CubeMDOS, but when execute, i'm doing a decision "ParaDOS found?", so if yes, I execute the ParaDOS-RSX.
Works here   ???
Could you reproduce that in WinApe?
Same effect with Parados 1.2?
You can attach the big-floppy-drives? (so Parados is loaded correctly)
Please, could you send me the "?peek(&b0c7)"  and b0c8 & b0c9 values

[Strange Things happens with the Quote, so plain:]
Second: Some subfolders shows as name "eEUERO~1" (with YANCC) in place of their real name.
(with pure CubeMDOS on the commandoline the first letter is instead of "e" a  (&HE5) Symbol)
This happens both on XMASS and on HXC Gotek with RSX |HB.
[Quote-end]


Which media do you use (e.g. SD-Card 16GB FAT32 & DOM 512MB FAT16 both with partions at max size)?
You will see the strange names on both medias and the Gotek has HXC Firmware(!?)
In YANCC you dont see the longnames in the penultimate line? (I think YANCC is ok, and CubeMDOS reported strange Things)
With |DIR you will see "aUERO~1" (instead of the correct Name "EUERO~1")?
Do you deleted the subfolders before, when yes: How do you deleted them (Windows, CubeMDOS, …)?
The directory-content is correct, when displayed in MSDOS?
Do you have a chance to do a screenshot of the sector-content of the Directory on your WindowsPC or could you upload an Image of your media on an internet-hoster (prefered)? (i can assist you (PM))
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: netmercer on 02:05, 14 November 18
Servus SOS  ;D ,
thank you for your quick reply.

With Parados 1.2 the |DRIVE RSX works.  :doh:
I'm still using ParaDOS 1.1, because I patched it for my needs. I will see what to do...

Strange subfolder name:
In XMASS I'm using a 512MB CF card formated in FAT16 by ACMEDOS (no partition, 123 MB) and in Gotek there is a 8GB FAT32 USB stick.
Under Windows, Symbos or ACMEDOS the subfolder names are right and all works as expected. I think YANCC is ok, too.
In the past I deleted and created different files and subfolders on the CF card by ACMEDOS. For the USB stick I did this only with Windows.
The affected subfolder could be opened with its right name under CubeMDOS and the included files are usable.
Because of the beginning letter "&HE5" of the "wrong" name it might seem, that this folder was deleted, but it was not.
I will try to make a image of the directory sectors for you.

Best regards
netmercer
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: netmercer on 01:48, 20 November 18
Servus SOS,

in WinApe with CubeMDOS a image of my X-MASS drive shows the same behavior as a real CPC6128.
Enclosed you will find a screenshot of WinApe with strange subfolder name:  :o

Best regards
netmercer
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: RockRiver on 10:29, 20 November 18
Symbiface II (IDE) support???
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 14:00, 20 November 18
Symbiface II (IDE) support???

Yes, should be run (i can't test it - i have no SF2).
Please reported back.  (then i will Change the title of this thread)
Media max. 128GB FAT16 or FAT32.
CubeMDOS should be detect every 1st Partition.
Title: Re: CubeMDOS / FAT16+FAT32-IDE-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 23:24, 20 November 18
Second: Some subfolders shows as name "eEUERO~1" (with YANCC) in place of their real name.
(with pure CubeMDOS on the commandoline the first letter is instead of "e" a  (&HE5) Symbol)
This happens both on XMASS and on HXC Gotek with RSX |HB.
Bugfix sent to netmercer.
If he does not report any problems, the bugfix will be included in the next version.
The next version will take a while (I'm still struggling with the FlashFloppy-Firmware)


(Thanks to netmercer for cooperation)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: TotO on 15:07, 16 February 19
Hello SOS,

I have updated my X-MEM / X-MASS installer with:
- FW3.16 (UK,FR,ES) + EXP ROM
- BASIC 1.20
- CUBEMDOS 0.12
- SYMBOS 3.0 ABCD ROM (optional)

The disk content include FORMAT (use FAT32), INSTALL and the X-MEM FLASHER tool.
Here the link: xmem_xmass_install.zip (http://totoonthemoon.free.fr/temp/xmem_xmass_install.zip)

Cheers,

  TotO
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 16:55, 20 February 19
Thank you so much SOS for your work. You save our sources!
I've used the CubeIOS version for some months, and it really improves my life.

Some bug reports / feature requests (NB: I'm using 1st ACMEDOS format):

1/ Path handling
1a/ I regularly save backups on A from Orgams itself. It would be nice to just use "A:gap.o"
1b/ Even more important when includes are included: be able to write INCLUDE "/lib/arithm.o" (and relative paths as well)
Both Offset and Candy have a nice system working.

2/ |A inconsistent
Sometimes it works directly, other times I just log on A but subsequent CAT is on D: and I have to use |AOFF. I've tried both settings of the ROMs IIRC.

3/ Crashes when trying to save the 65th file.
"Directory full" message would be more gentle!

4/ Be able to use FAT with 128MB
For interoperability and since you say saving would be faster.

5/ YANCC should have a 'Move' command
At least YANCC should retain the selection (like PARADOS copier).

6/ There should be a |MV RSX as well!
Specially with 7/ fixed.

7/ Globs doesn't work as in AMSDOS
E.g. |DIR,"*.BAK"

8/ |ERA doesn't work with globs.
E.g. |ERA,"*.BAK"

9/ Sort directory.
It should take less than 1 frame on a 4Mhz Z80 :)

10/ Fix |DRIVE
When wrong number of arguments, you should lift the command to overridden DOS rom.
Right now we cannot invoke Parados copier anymore.

11/ Open source.

Ok, that's a lot demands! It just shows I've used it quite intensively (:)
As i said it's really useful. Thanks to TotO and yOu, disc access is now on par with general CPC reactivity (From switch on, 1 second to fire up Orgams, 2 seconds to load a source !).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 18:03, 20 February 19
Hi there!

nice to hear  :)

At the Moment I'm busy with Symbiface 3-Support, but i will continue the open points soon, i have some first Questions (i will check this message completely later):

2/ |A inconsistent
Sometimes it works directly, other times I just log on A but subsequent CAT is on D: and I have to use |AOFF. I've tried both settings of the ROMs IIRC.
Strange, i will later test this, please inform me, when you can reproduce that

4/ Be able to use FAT with 128MB
For interoperability and since you say saving would be faster.
??
What do you mean exactly?
I support the original 128MB formatted media's from ACMEDOS.



5/ YANCC should have a 'Move' command
At least YANCC should retain the selection (like PARADOS copier).

6/ There should be a |MV RSX as well!
Specially with 7/ fixed.
It's a similar feature.
I thinking about it, but when i will add this, i think not in this year.  (last Point on my todo-list)

7/ Globs doesn't work as in AMSDOS
E.g. |DIR,"*.BAK"

8/ |ERA doesn't work with globs.
E.g. |ERA,"*.BAK"
7: Oh, should work  :(   (but doesnt)
8: I will take a look…..

9/ Sort directory.
It should take less than 1 frame on a 4Mhz Z80 :)
No it's canceled, i'm thinking about this feature, but IMHO i Need a 40mhz instead of a 4mhz-CPU.
Next Problem: I Need RAM for sorting.


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 20:52, 20 February 19
> 2/ Inconsistent |A
Strange, i will later test this, please inform me, when you can reproduce that
I reproduce ~50% of the time.
* Booting on D.
* Working on D.
* Resetting to exist Orgams.
* |A

> 4/ 128Mb FAT
??What do you mean exactly?
I support the original 128MB formatted media's from ACMEDOS.
Here is what I've understood. I might be wrong:
- If I choose FAT format, it will try to use 400Mb. So, once the first 128Mb of the DOM is used, all hell breaks loose.
- ACMEDOS format is safe, but slower in regard to SAVE and not readable by SymbOS.
Hence, a FAT format not overflowing over 128Mb would be perfect.
> 9/ Sorting directory
No it's canceled, i'm thinking about this feature, but IMHO i Need a 40mhz instead of a 4mhz-CPU.Next Problem: I Need RAM for sorting.
Not counting the 2ko for cat, cannot we reuse some AMSDOS buffer (like the one used to read sectors)?
Do you plan to maintain the 64 files directory limit (I would be fine with that)?I could do the sorting routine, if you wish!


Thank you for your fast reply!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: TotO on 21:00, 20 February 19
ACMEDOS format is safe, but slower in regard to SAVE and not readable by SymbOS.
ACMEDOS handle an unparted FAT16 mass storage. You can read and write from SymbOS as well as from any compatible OS (windows, linux, ...) if connected.

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 22:52, 20 February 19
I reproduce ~50% of the time.
* Booting on D.
* Working on D.
* Resetting to exist Orgams.
* |A
Could you describe the steps a Little bit more?
"Resetting to exist Orgams." ?
CPC-Reset, starting Orgams from ROM, save & load something on A or ?

Here is what I've understood. I might be wrong:
- If I choose FAT format, it will try to use 400Mb. So, once the first 128Mb of the DOM is used, all hell breaks loose.

I want to quote Connor MacLeod here: There can only be one.
Yes, CubeMDOS supports only the 1st Partition of a media, so the Format kills every existing Partition. (i do not Change this)


Not counting the 2ko for cat, cannot we reuse some AMSDOS buffer (like the one used to read sectors)?
Do you plan to maintain the 64 files directory limit (I would be fine with that)?
hmmm....
my english is not very perfect :-[   (so i dont know exactly, if i understand you correctly)

For CAT i use the 2KB Buffer, when i detect buffer-overflow, i will print an information in the cat-buffer.
The ReadSector-Buffer in AMSDOS i use it intensively.
64-Files-Limit?
I copied with YANCC 68 files in one directory and do a save&load in BASIC , so 69 files are no problem.
=> i need a more reproduceable szenario


I could do the sorting routine, if you wish!
(thanks)
Hmmm, i dont know :-\
The problem is, that my ROM is nearly full and this may break the 16KB-Size.
I think, the sorting will be very problematic.
The whole Directory must be read by the CPC (e.g. 712 Files) and then sorted in the memory.
It could consume a lot of the 64KB Main-RAM....
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: Fessor on 00:08, 21 February 19
Sorting, kind of, could be done by |dir,"a*", |dir,"b*" etc..Maybe a command like |dira2z could be introduced, which intern runs through the alphabet and calls the dir-output with filemasks from "a*" to "z*"


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 01:29, 21 February 19
1/ |A
OK I can reproduce consistently: if firmware zone is zeroed, then I have to enter |AOFF to access A, despite my configuration (cf config.bas).
I like the fact that:
• X-MASS is the default on reset.
• The path is conserved across warm resets.
I'd like to have AOFF behavior forced all the time.

3/ 64 files per directory limit
I got a crash each time I reached 65 files.
Code: [Select]
|mkdir,"tmp":|cd,"tmp"
for i=1 to 99:print i:save str$(i):next
-> Boom after i=63.

4/ FAT format
I'm not sure to see why FAT32 format couldn't be restricted to 128Mb, so that:
• |FREE is accurate
• More importantly, disc full is properly detected and no overwriting occurs!

9/ Sort directory712 files !? I don't mind if the sorting is kind of disabled for such extreme cases.
It doesn't mean it should be thrown away for day to day usage !
We could come with a pretty fast solution for directories with <=128 files.
And not that big in memory! Tell me how much space do you have (:


13/ Starkos hangs with 'GetDir'
It could be a bug with Starkos, but if the ROM is fully AMSDOS compatible why wouldn't it work?

Thank you for your attention!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 01:40, 21 February 19
Sorting, kind of, could be done by |dir,"a*", |dir,"b*" etc..Maybe a command like |dira2z could be introduced, which intern runs through the alphabet and calls the dir-output with filemasks from "a*" to "z*"
That's an interesting approach, modulo some caveats:
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 10:00, 21 February 19
1/ |A
OK I can reproduce consistently: if firmware zone is zeroed, then I have to enter |AOFF to access A, despite my configuration (cf config.bas).
I like the fact that:
• X-MASS is the default on reset.
• The path is conserved across warm resets.
I'd like to have AOFF behavior forced all the time.
the "firmware zone" is zeroed could be a problem.
Please could you describe the completely point "1" with PM more clearly?

3/ 64 files per directory limit
I got a crash each time I reached 65 files.
Code: [Select]
|mkdir,"tmp":|cd,"tmp"
for i=1 to 99:print i:save str$(i):next
-> Boom after i=63.
I can reproduce that now (thanks), crashes only on FAT16.
Prio 1


4/ FAT format
I'm not sure to see why FAT32 format couldn't be restricted to 128Mb, so that:
• |FREE is accurate
FAT32 is not restricted to 128MB, you can use large media's.
I dont optimize the format.bas anymore, because you can format your media with Windows, Linux, ....
The FREE-Display on FAT32 must be correct, else it's a strong indicator, that something is going very wrong!
FREE on FAT16 is..... >:(  :'(  :'( :'(   So this should be nearly correct....

• More importantly, disc full is properly detected and no overwriting occurs!
I have checks against possible overwriting-issues, so this "should" be not occur.
Disc full detection: Should be work too
Do you have problems with this two points?


And not that big in memory! Tell me how much space do you have (:
Much too few.
Maybe (or not) i will later release an add-on-rom, where i have enough space.

13/ Starkos hangs with 'GetDir'
It could be a bug with Starkos, but if the ROM is fully AMSDOS compatible why wouldn't it work?
I check this later

I must now hurry-up to continue with Symbiface3-Programming, i think maybe april-mai i will correct the bugs.
(there are other open issues, which i want to fix, e.g. FlashFloppy-Support on a Plus-Machine)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: TotO on 20:31, 21 February 19
The FAT32 strange limitation is to not be able to support partitions under 32MB. :-\
Title: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: angelcaio on 14:07, 23 February 19
Hi. I have connected a DOM to the PC with an adapter and I have presented it to WinApe:
   (https://uploads.tapatalk-cdn.com/20190223/eadb6d3e154a086c4ea21552adb9e953.jpg)
(https://uploads.tapatalk-cdn.com/20190223/e875f38532d60f608daa1643e493fb40.png)

With the ROM’s configuration (with firmware 3.16 and extensions)
(https://uploads.tapatalk-cdn.com/20190223/d334c3ddcea994a0318256aa677d5a70.jpg)

The Format.bas utility does not do anything either. Leave it as it was
  (https://uploads.tapatalk-cdn.com/20190223/b7b9bf90597be4f80c7fb6e24e0aae00.png)

I have formatted it from Windows with Fat format and then, from Windows I can create subdirectories and files that are then visible from WinApe

In WinApe, can read from the DoM and browse the subdirectories, read and execute programs, but I can not create files or directories.
(https://uploads.tapatalk-cdn.com/20190223/b5e8f5dc699786abb4a7a3cb20239b98.png)
(https://uploads.tapatalk-cdn.com/20190223/8b3eb2c4833ba8a46b94441060215447.png)
   
 Again I  executed format.bas with the same result

What am I doing wrong?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: gerald on 16:17, 23 February 19
The FAT32 strange limitation is to not be able to support partitions under 32MB. :-\
It's not a strange limitation, it's a logical one.
There is no need to have 32bit fat entry when 16bit are enough. So you use FAT16.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: TotO on 16:28, 23 February 19
There is no need to have 32bit fat entry when 16bit are enough. So you use FAT16.
You have no need... This "fake" limitation avoid to use really common 32MB MMC/SD cards on devices not compatible with FAT16 (HxC in example).
Next, because FAT32 allows to support long filenames and a faster acces to the files.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: gerald on 17:56, 23 February 19
You have no need... This "fake" limitation avoid to use really common 32MB MMC/SD cards on devices not compatible with FAT16 (HxC in example).
That's laziness  ;D . There is not much to do to support FAT12/FAT16.
 It's just a matter of dealing with a fixed place root directory for FAT12/16 and cluster number to sector conversion.

Next, because FAT32 allows to support long filenames and a faster acces to the files.
Long filename is a extension of directory entry and has no implication on FAT itself.
You can use long filename on a floppy (FAT12) if you want.
 DOS 3.1 will only show you short names, but windows will show you the full name.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: TotO on 19:59, 23 February 19
Sure, I know that... But that not fix my HxC issue when I have offered a 32MB MMC bonus for R-TYPE 128K box versions, to use it like a floppy. ;D
I only got an answer to explain that is not possible to support the FAT32 for a next update of the HxCFloppyEmulator!  :-\



Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 22:53, 23 February 19
Hi. I have connected a DOM to the PC with an adapter and I have presented it to WinApe:

The Format.bas utility does not do anything either. Leave it as it was

I have formatted it from Windows with Fat format and then, from Windows I can create subdirectories and files that are then visible from WinApe

In WinApe, can read from the DoM and browse the subdirectories, read and execute programs, but I can not create files or directories.
...
Hi, strange things you reported  :o
It seems that the Partition is write-protected.

Ok, i do some Tests too:
- Plug in a 4GB Fat16 USB-Stick, it's writeprotected too (so i can reproduce your issue)
- Make an Image from the Stick and mount them in WinApe -> It's writeable!!!!!
- Format in Winape the 4GB-USB-Stick with ACMEDOS and Change the ROM to CubeMDOS.
  It's writeable from Winape.

I cant do in Z80 a difference: WinApe IDE-Image or Logical Drive-Letter -> It looks the same.
The only logical conclusion must be, that WinApe has a problem / bug and not CubeMDOS (?!)

I try to contact Executioner to talk with him, about this problem.
But "last active" was 07 June 18 .... maybe he will not answer....
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: GUNHED on 03:28, 24 February 19
Regarding the IDE part I'm not sure if the SF2 is emulated 100%. At the beginning my IDE code had problems, but I don't know it the missing status bits have been added. Therefore please do tests on real hardware.  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 09:20, 03 March 19
FAT32 is not restricted to 128MB, you can use large media's.
I dont optimize the format.bas anymore, because you can format your media with Windows, Linux, ....
Hum! I like my CPC self-contained (:

The FREE-Display on FAT32 must be correct, else it's a strong indicator, that something is going very wrong!
FREE on FAT16 is..... >:( :'( :'( :'(   So this should be nearly correct....
I have checks against possible overwriting-issues, so this "should" be not occur.
Disc full detection: Should be work too
Do you have problems with this two points?
No problem so far, as I am only using ~10Mb for now! Simply the doc mentioned:
Quote
Three presets of formats you can choose
Format 1: Original ACEMDOS, with the Identifier "X-MASS" at #2B of LBA 0, 128MB Volume
Format 2: First Primary Partition FAT16, 400MB partition Table (Type #06, 8192 Bytes/Cluster)
Format 3: First Primary Partition FAT32, 450MB partition Table (Type #0B, 4096 Bytes/Cluster)
But as I understand now, this was a limitation of format.bas and not CUBEOS's.
The recommended solution is to format the 128MB DOM with a 128MB FAT32 partition by another mean (e.g. via SymbOS).
Is that correct?

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 09:41, 03 March 19
I'm encountering an issue with YANCC.
All OrgamS sources larger than 32k copied to a sub-directory are corrupted at the end (but the file size seems correct).
I couldn't reproduce that with a binary file, so maybe it's because .O are ASCII.
That being said, thank you for your helpful answers and attentiveness.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 11:52, 03 March 19
Another one for your Sunday (:
Code: [Select]
|cd,"/plad"
|o     <- OK
|cd,"/plad/archive3"   <- existing dir
|o     <- unknown command

My Orgams ROMs are in &a,&15,&1a. Dedicated RAM memory starts at &ABF8.
Amsdos RAM memory start at &A6F0 (yes it is shifted).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 13:09, 03 March 19
Hi m_dr_m,

First thanks about your mails, to make CubeMDOS better  :D

13/ Starkos hangs with 'GetDir'
It could be a bug with Starkos, but if the ROM is fully AMSDOS compatible why wouldn't it work?
I checked Starkos.
The reason, why the access to the Massstorage is problematic, starkos re-init (why?) the ROM 07,
so the hook of CubeMDOS is re-init to Amdos-Default - no Massstorage-ROM anymore :-(
When i disable these init or mount CubeMDOS at ROM7: Starkos did not function correctly.
The CAT-Buffer from CAS_CATALOG is build correctly, but some routines in Starkos prevent
from function.
So the Starkos-Author must be change his program to get a functional Massstorage-Application.


Simply the doc mentioned:But as I understand now, this was a limitation of format.bas and not CUBEOS's.
The recommended solution is to format the 128MB DOM with a 128MB FAT32 partition by another mean (e.g. via SymbOS).
Is that correct?

The Format.bas should only have a small number of Presets for possible DOM's. So CubeMDOS is not restricted in detection of the Format. So the only rule is "first Partition", e.g. FAT16 with 1GB, FAT32 with 400MB or 40GB are possible.
For the 128MB DOM i will Always recommend the 128MB ACMEDOS FAT16-Format (1st Preset).
Btw. TotO almost convinced me to extend the format.bas with other/additional presets, but i must check, if i have the DOM's in my roof.


I'm encountering an issue with YANCC.
All OrgamS sources larger than 32k copied to a sub-directory are corrupted at the end (but the file size seems correct).
I couldn't reproduce that with a binary file, so maybe it's because .O are ASCII.
That being said, thank you for your helpful answers and attentiveness.
:(
Ok, i will check that later.


Another one for your Sunday (:
Code: [Select]
|cd,"/plad"
|o     <- OK
|cd,"/plad/archive3"   <- existing dir
|o     <- unknown command

My Orgams ROMs are in &a,&15,&1a. Dedicated RAM memory starts at &ABF8.
Amsdos RAM memory start at &A6F0 (yes it is shifted).

Hmmmm, in Winape this works
- I used your ROM-Numbers (Orgams in &a, orgext in &15 and monogams in &1a)
- CubeMDOS in ROM6
- I created the directories and make a cold-reset.
- I used your RSX-Codes, i leave Orgams with CTRL+B

Orgams make a memory restore of the high-memory.
In my test i noticed, that orgams does not restore the complete memory from himem up to the stack-end.
The first &81 bytes are missing, i not checked at the moment, if this is important.
I think the exact ROM-Configuration could be important

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 17:53, 03 March 19
First thanks about your mails, to make CubeMDOS better  :D
You are very welcome!
Another option to make CubeMDOS better is to release the source (:
So the Starkos-Author must be change his program to get a functional Massstorage-Application.
Yep, fair enough, that's what I've thought.
Thanks for looking at it.
Anyway soon no one won't need Starkos anymore as a native CPC tracker!

For the 128MB DOM i will Always recommend the 128MB ACMEDOS FAT16-Format (1st Preset).
Oh, why is that, since FAT32 is better (faster access, less space wasted, more common...)?
According to https://en.wikipedia.org/wiki/Design_of_the_FAT_file_system#Size_limits (https://en.wikipedia.org/wiki/Design_of_the_FAT_file_system#Size_limits), the min size is 32Mb.

Btw. TotO almost convinced me to extend the format.bas with other/additional presets, but i must check, if i have the DOM's in my roof.
Always listen to TotO, he is wise. (:

Ok, i will check that later.
Nice! I've done some more tests. It also fails when copying from D to A or from A to D.
BTW when trying to copy back a corrupted &8400 long ascii file (on D) to A, I got:
Error close Destination-File. Abort Operation
Hmmmm, in Winape this works
- I used your ROM-Numbers (Orgams in &a, orgext in &15 and monogams in &1a)
- CubeMDOS in ROM6
- I created the directories and make a cold-reset.
- I used your RSX-Codes, i leave Orgams with CTRL+B
Actually the scenario with /plad/archive3 also fails at RESET.

Orgams make a memory restore of the high-memory.
In my test i noticed, that orgams does not restore the complete memory from himem up to the stack-end.The first &81 bytes are missing, i not checked at the moment, if this is important.
Maybe related to this bug: mailto:http://orgams.wikidot.com/bugs#toc40
 (http://orgams.wikidot.com/bugs#toc40)Anyway, as said above, I get the issue from a cold start as well.

Quote
I think the exact ROM-Configuration could be important
1: CubeIOS
2: UTOPIA
3: YANCC
4: LAUNCH
5: HACKIT
6: PARADOS
7: AMSDOS
9: Flash burn
10: Orgams
12: TurboAss
15: OVL v2
The others ROMS are extensions (02) or data (03).

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 04:25, 04 March 19
10/ Fix |DRIVE
When wrong number of arguments, you should lift the command to overridden DOS rom.
Right now we cannot invoke Parados copier anymore.
Since YANCC doesn't allow A to A copy, this request would have a very good utility/work ratio!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 09:17, 04 March 19
Another option to make CubeMDOS better is to release the source (:Yep, fair enough, that's what I've thought.
The Projects CubeMDOS+YANCC are not started as an open-source project
=> Not planned at the moment, maybe (maybe not) later in this year.


Oh, why is that, since FAT32 is better (faster access, less space wasted, more common...)?
Backward-compatibillity to ACMEDOS+IMPDOS.


Actually the scenario with /plad/archive3 also fails at RESET.
Maybe related to this bug: mailto:http://orgams.wikidot.com/bugs#toc40
 (http://orgams.wikidot.com/bugs#toc40)Anyway, as said above, I get the issue from a cold start as well.
1: CubeIOS
2: UTOPIA
3: YANCC
4: LAUNCH
5: HACKIT
6: PARADOS
7: AMSDOS
9: Flash burn
10: Orgams
12: TurboAss
15: OVL v2
The others ROMS are extensions (02) or data (03).
The ROM's 9+12 i haven't found.
The other Orgams-ROMs i put it in 11+12.
But i can't reproduce your problem in WinApe  :(
Could you reproduce that in Winape?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 14:48, 21 June 19
Nice summer to you!


Another bug detected: cannot save an ASCII file larger than 64k. The result is truncated.
Is a new version planned anytime soon? (:
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 15:15, 21 June 19
Nice summer to you!
Another bug detected: cannot save an ASCII file larger than 64k. The result is truncated.
Is a new version planned anytime soon? (:
Thanks, for you too ;-)

"Soon" is very relative ;-)
My actual versions (CubeMDOS+YANCC) are stable in Winape, so i "only" Need to test it on real Hardware.
The changelog of the next Version is:
- Bugfix of FlashFloppy-Support (Amstrad+)
- CAT/DIR: Possible false display in the path name  (thnx netmercer)
- Display VolumeName during boot - Changed/Fixed - again :-(
- No MSD-Hardware found, correct exit
- Make-Directory: Convert Directory-Names to Uppercase (else Directory can't read by Windows)
- FAT16: Can't create more than 64 DirEntries  - checked 20000 save's   (thnx m_dr_m)
- FAT32: Saves to LBA 65535 crashes
- Internal Restructure->Some more games should be run.
- V1 (default) & V2 mode introduce ->Some more games should be run.
- |disc , then cat crashes
- CAS_IN_CHAR: Reads sometimes a little bit too much bytes & improved 1A-Handling (Orgams)
- Sometimes deleted directories will be displayed (thnx netmercer)

Open are you two issues:
- Globs doesn't work as in AMSDOS (dir+era)     (thnx m_dr_m)
  E.g. |DIR,"*.BAK"
  E.g. |ERA,"*.BAK"
- Cannot save an ASCII file larger than 64k. The result is truncated.        (thnx m_dr_m)
  => But i must check, if this is solveable....
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: m_dr_m on 15:46, 22 June 19
- Make-Directory: Convert Directory-Names to Uppercase (else Directory can't read by Windows)


Oh that's a pity! I enjoy the lowercase names (more legible).
[/size]
[/size]
Quote

- Cannot save an ASCII file larger than 64k. The result is truncated.        (thnx m_dr_m)
  => But i must check, if this is solveable....
Why not? It works like a charm in Amsdos.


I would be happy to beta-test!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: SOS on 21:53, 23 June 19
I would be happy to beta-test!
:D :D :D :D
https://sourceforge.net/projects/symbiface3/files/Alpha%20%28Next%20Version%29/ (https://sourceforge.net/projects/symbiface3/files/Alpha%20%28Next%20Version%29/)
(Version runs without an Problem in Winape)
You need an YANCC-Update and configure CubeMDOS with the Config.bas in the DSK-File

But Problems, Questions & …. please only per PM
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/Gotek
Post by: TotO on 12:05, 27 August 19

I would like to know if any updates was made for your tools to update the X-MASS installer? :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface 3,HXC/Gotek
Post by: GUNHED on 20:25, 27 August 19
(Version runs without an Problem in Winape)
IMHO then the emulator has to get improved. If software developers care too much about emulators, then one day stuff will not run an real CPCs.  :o
However, great work!!! I like to use it with SF3.  :) :) :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/Gotek
Post by: SOS on 19:30, 04 October 19
New Version 290919b - Changelog:
- Config.BAS, Extended - You should run Config.BAS before use
- Bugfix of FlashFloppy-Support (Amstrad+)
- CAT/DIR: Possible false display in the path name  (thnx netmercer)
- Display VolumeName during boot - Changed/Fixed - again :-(
- No MSD-Hardware found, correct exit
- Make-Directory: Convert Directory-Names to Uppercase (else Directory can't read by Windows)
- FAT16: Can't create more than 64 DirEntries  - checked 20000 save's   (thnx m_dr_m)
- FAT32: Saves to LBA 65535 crashes
- Internal Restructure/OS-Integration changed->Some more games should be run.
- V1 (default) & V2 mode introduce ->Some more games should be run.
- |disc , then cat crashes
- CAS_IN_CHAR: Reads sometimes a little bit too much bytes & improved 1A-Handling (Orgams)
- Sometimes deleted directories will be displayed (thnx netmercer)
- CD in MD-Created Dir's with length < 8 chars problems  (thnx netmercer)
  e.g.  |MKDIR,"TEST.TST"
  |CD,"TEST.TST" results 'no directory'
  |CD,"TEST    .TST" opens the directory
- Directory ".." in Root-Directory confuses CubeMDOS

Remarkable parts are the 2nd ROM, which allow to install CubeMDOS at ROM14 and AMSDOS at ROM15.
V1+V2: My main focus are game-compatibillity. Only a few games (+ORGAMS + Symbos) can not be started with the default configuration (V1).
 So you can switch with |V2 to an alternative configuration (or use config.bas to switch V2 permanently "on").

YANCC-Users must be Update YANCC when using this new Version.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 14:53, 25 November 19
Nice. No DSK file with the ROM inside like for YANCC?  :-*
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 15:33, 25 November 19
Nice. No DSK file with the ROM inside like for YANCC?  :-*
We will see, very soon  ;)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 22:50, 23 December 19
Hi Folks,
I'm looking for a beta-tester for my new DSK-Plugin (incl. new YANCC-Version).
You need an XMASS or SF2.
I think the compatibillity is good, the performance is medium, but useable (tested with 2GB F32-DOM).
SF3-Version with Hardware-Acceleration is coming very soon (fucking fast  :o ;D).
Please PM, when you have fun and time to test.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: zhulien on 08:18, 07 January 20
Any chance for the next version of CubeMDOS to work at the same time as M4 so we can have Hx Floppy Support, Compact Flash Support and SD Card Support all at the same time with internet?

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 20:18, 07 January 20
Any chance for the next version of CubeMDOS to work at the same time as M4 so we can have Hx Floppy Support, Compact Flash Support and SD Card Support all at the same time with internet?
hmmm, it's problematic:
you can only have one primary mass-storage-rom.
when you (a game) init AMSDOS, then you have only chance to init one mass-storage-rom.
also the RSX's are problematic too.

i removed for testing the M4-ROM-Check, and test
 CubeMDOS at ROM > 6
=> i cant switch to CubeMDOS.
 CubeMDOS at ROM < 6
=> i can switch to CubeMDOS with |DISC and back with |SD.
 |TAPE resets at the moment the Amstrad
 (it's problematic, because you have only one place in the RAM for the pointers)
 When M4-ROM-is active:
 |CD goes to the CubeMDOS-MassStorage and not to the M4

And what's you goal to have both MassStorage's active?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: zhulien on 02:20, 13 January 20
hmmm, it's problematic:
you can only have one primary mass-storage-rom.
when you (a game) init AMSDOS, then you have only chance to init one mass-storage-rom.
also the RSX's are problematic too.

And what's you goal to have both MassStorage's active?


I understand.  Let's see if my drivers ROMS get traction - if they do then maybe we can revisit.  If I have the hardware why not make use of it?  It is good hardware.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 16:40, 20 January 20
New Version 120120b - Changelog:
- DSK-Support (read only - "Write" is on my todo-checklist, but has no high priority)
- HXC/FlashFloppy: Save-Bug
- |A & |B -Bug (Thanks Ast)
- |DIR sometimes brings an AUTO-Line after display
- Compatibility fix, when starting Games from Floppy + CubeMDOS in ROM7   
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 18:50, 20 January 20
Cool! Can you please summarize up which expansions it does support now? (Guess that's interesting for people getting a mass storage device now).  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 19:02, 20 January 20
Cool! Can you please summarize up which expansions it does support now? (Guess that's interesting for people getting a mass storage device now).  :)

Please see the Title "CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy"  ;)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: Fessor on 22:44, 13 February 20
Is it possible thate CubeMDOS changes / reset the configuration of the memory banks?

I have code where I select a memory bank and then use cas_in_open, cas_in_direct and cas_in_close to read a file directly into the selected memory bank.
This works without any problems under AMSDOS.
Not with CubeMDOS, however, and I wondered in the WinApe debugger why code was overwritten and memory banks remained empty.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 07:27, 14 February 20
Is it possible thate CubeMDOS changes / reset the configuration of the memory banks?
Use |V2 for your code
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: Fessor on 10:45, 14 February 20
Use |V2 for your code
Reverted the code for tests, its working now.


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 21:04, 14 February 20
... and I wondered in the WinApe debugger why code was overwritten and memory banks remained empty.
No emulator is perfect. However IMHO we really shouldn't start to write software for emulators instead of the CPC. Else we just can use the PC instead of the CPC. No offense, just my POV.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: Fessor on 14:42, 15 February 20
No emulator is perfect. However IMHO we really shouldn't start to write software for emulators instead of the CPC. Else we just can use the PC instead of the CPC. No offense, just my POV.
What do you mean with "software for emulators"?
Im using the Emulator as Tool to Develop for the CPC. And using PCs/Workstations as IDE for the 8bits began back in the 80s. Emulators are just an logical Evolution of what started back then.


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 15:13, 15 February 20
What do you mean with "software for emulators"?
For example: The code of the CPC-Telegramm was (back the day) changed to run on emulators too.  First it looked super great and did run on the CPC. Later it just looked great and did run on everything.

But back to topic! I'm just encouraging the inventor of the great CubeMDOS to focus an CPC and not on emulators. If something doesn't run on an emulator the emulator need to be changed and not something actually working on the CPC itself.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GFXOR on 16:42, 09 April 20
I don't read anything about it but I had an issue with CubeMDOS, I don't knowif it is on a todolist somewhere, maybe I did wrong...

LOAD"ANYTHING.BIN",&XXXX
Returns Syntax Error

Is it "normal" ?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 17:05, 09 April 20
I don't read anything about it but I had an issue with CubeMDOS, I don't knowif it is on a todolist somewhere, maybe I did wrong...

LOAD"ANYTHING.BIN",&XXXX
Returns Syntax Error

Is it "normal" ?

No, not normal.
Works here.
Ok, lets reproduce:
Please your Rom-Config & Which hardware do you use?
Could you check it with a short example:
> save"scr",b,&c000,&3fff
> cls
> load"scr",&c000
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GFXOR on 18:18, 09 April 20
Thank you for your quick answer.
I simply didn't make your test before, sorry. And it works.
I made other tests, and it seems that the problem is from my side (maybe my file has a problem). Maybe a pb of file copy (2 files had the same pb), maybe a connector problem...

I will just come back here if I identify something new and concrrete and reproductible.
Just in case, my rom config (CPC6128) :
2-CubeMDOS
3-YANCC
14-LAUNCH
15-ROMAN
Nothing else except in ROM0 and 7 (alternadtive 464 boot with XMem).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 23:21, 12 April 20
Does anybody have a version of this that can be run on a C4CPC?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 11:16, 13 April 20
Does anybody have a version of this that can be run on a C4CPC?
Hmm, its a problem, i do not have an C4CPC.
I think it's a "normal" ROM-Board for the Plus-Slot?!
How do you configure the ROM-Numbers and what's the problem (e.g. the CPC reset)?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 13:19, 13 April 20
It loads them from a menu - i am new to all this but think it might need to be in a special format or something? has nobody here done this?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: gerald on 13:35, 13 April 20
Hmm, its a problem, i do not have an C4CPC.
I think it's a "normal" ROM-Board for the Plus-Slot?!
How do you configure the ROM-Numbers and what's the problem (e.g. the CPC reset)?
It's a normal romboad with a twist.
ROMs are mapped from 128 to 160, so none of them are initialised by the FW.Also
- rom 128 is a mirror of the lower ROM,
- rom 129 is a mirror of upper ROM 0- rom 131 is a mirror of upper ROM 7
So either you modify the FW to initialise ROM in the cartridge range (something @dragon (https://www.cpcwiki.eu/forum/index.php?action=profile;u=251) did)
Or completely replace ROM7, but then you lose floppy access



Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 14:48, 13 April 20
i wanted to use this with my hxc as a mass storage rather than the sperate dsk images so I am assuming i still need floppy access as thats how it connects? can anybody supply a version of this i can just put on c4cpc sdcard and run?

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 15:14, 13 April 20
- rom 131 is a mirror of upper ROM 7

Or completely replace ROM7, but then you lose floppy access
So you can set CubeMDOS in ROM 131 and AMSDOS in ROM15 (in an external ROM-Board), so
AMSDOS will be first init as ROM15 and after that CubeMDOS as ROM7 ?!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: gerald on 15:33, 13 April 20
So you can set CubeMDOS in ROM 131 and AMSDOS in ROM15 (in an external ROM-Board), so
AMSDOS will be first init as ROM15 and after that CubeMDOS as ROM7 ?!
Yes, this should work.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 16:46, 13 April 20
ok and how do i go about doing this?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 21:09, 13 April 20
ok and how do i go about doing this?
Please, could you describe more, what is your Goal and which Hardware do you have?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 02:53, 14 April 20
I want to use this on my c4cpc cart and use my hxc as a mass storage device.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 07:40, 14 April 20
I want to use this on my c4cpc cart and use my hxc as a mass storage device.
The Problem is, that (when i understand Gerald correctly) you need an ROM-Board to install custom ROM's.
=>
You can e.g. CubeMDOS install at ROM6 - but not with c4cpc, you can only choose ROM7 (=131).
But if you do that, you must(!) install AMSDOS in a Slot 8 up to 15 (15 is the best choice) - but  not with c4cpc.
The next CubeMDOS-Version Needs for HXC-Access to install both Cube-ROM's (e.g. the DSK-ROM at Slot8).
You need an extra ROM-Board to install ROM's with this numbers
   (in my example Cube on ROM6, DSK on ROM8   OR   Cube on ROM7(=131), DSK on ROM8, AMSDOS on ROM15)

But i dont know, what @dragon (https://www.cpcwiki.eu/forum/index.php?action=profile;u=251) done with his c4cpc-card, Maybe you can ask in the c4cpc-thread, how to fit the needed ROM-Config (6+8 or 7+8+15).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 11:34, 14 April 20
I want to use this on my c4cpc cart and use my hxc as a mass storage device.
The HxC is a floppy disc emulator, it's not intended to be used for mass storage, since it's too slow for that.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: lordoftime on 14:28, 14 April 20
i know this but the title of this post says HXC and i know the HXC has a direct access mode i thaught this is what this did? am I mistaken? I am new to the world of expanded amstrads!

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 14:40, 14 April 20
i know this but the title of this post says HXC and i know the HXC has a direct access mode i thaught this is what this did?
Yes, i am using the direct access mode of the HXC, so you can use them as a normal mass-storage (e.g. with an FAT32-16GB SD-Card), with Slot-Handling and "Changedir-into-HFE"-Feature (automount).
But yes again, it's sloooooowwww (but IMHO usable).
Your "only" problem is, that you do not have a hardware to burn ROM's/ROM-Board (but dont forget, i dont know anything about the C4CPC - sorry). Normally it doesnt matter which "normal"(!) ROM-Board you have, you must "only" burn the ROM-Numbers:
   (in my example Cube on ROM6, DSK on ROM8   OR   Cube on ROM7(=131), DSK on ROM8, AMSDOS on ROM15)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 15:12, 14 April 20
The HxC is a floppy disc emulator, it's not intended to be used for mass storage, since it's too slow for that.
Using floppy emulator as mass storage, using mass storage to open DSK... Peoples like to make coffee with a tea-pot and tea with a coffee maker..  :-\
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 16:47, 14 April 20
Using floppy emulator as mass storage, using mass storage to open DSK... Peoples like to make coffee with a tea-pot and tea with a coffee maker..  :-\
One of them is doable, but the other one a killer.
Well, all that comes from PC world where Nero Burning ROM XX now can read the newspaper for you.


Back to topic, the newest CubeMDOS is from January 12, 2020, right? The SF3 got a new update, will check this out soon. How it all works.  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 16:50, 14 April 20
i know this but the title of this post says HXC and i know the HXC has a direct access mode i thaught this is what this did? am I mistaken? I am new to the world of expanded amstrads!
Welcome!  :)  It can be a lot at once of course. Therefore we help. I don't know if you're mistaken.  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: beb on 11:36, 22 April 20
Hi.


I'm using Xmass with a 128mb DOM. The format tool can't handle 128mb FAT32 (only 450mb with fat16 or fat32 and ACME special format)

Also I'm trying to format the 128mb DOM on my laptop (with windows10 and he didn't recognize FAT16) but everything seem to work
and I got a fresh 120mb fat32. I put file on it. And when I try to read something onto my CPC, their is nothing or corrupted files.

Questions are following:
Maybe a format.bas tool with partition size choice ?
What kind of tool are you using onto win10 for a lowlevel format ? (the MSpartitiontool dont work well)

Thanks for CubeMDos.
Maybe it could be nice to release sources today ? (No one is immortal. Who know :) )
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 12:18, 22 April 20
The format tool can't handle 128mb FAT32 (only 450mb with fat16 or fat32 and ACME special format)

Also I'm trying to format the 128mb DOM on my laptop (with windows10 and he didn't recognize FAT16) but everything seem to work
and I got a fresh 120mb fat32. I put file on it. And when I try to read something onto my CPC, their is nothing or corrupted files.
The Format.BAS are a "Little Example" to Format an Media.
CubeMDOS is concepted to detect all(?  ;) ) FAT16/FAT32-Partions on an Media (first partion please).
So the reconmend way to Format an Media is to get your Windows, Linux, MAC-Computer and Format them, without using an special tool.
I make an quick check:
Mount an ACME-DOS-Image with my W10-PC, Format them with FAT32, copied some files on it and check it with WinApe (all is working, save is working too).
So, please could you make an Image from you complete(!) DOM, ZIP it and load it somewhere up in the Internet (WeTransfer, GoogleDrive, Filehoster,.-..)?
(+ some words, e.g. Game XY doesnt load or save to root doesnt work,...)
I will check this Image.
(for Image-Creation i use "Raolkil-DiskImage", but there are more working Tools in the WWW  ;) )
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: beb on 23:01, 22 April 20
ok.


I follow your advice and it doesn't work.
I ll try to make a image of my DOM
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 00:30, 23 April 20
I was also confused by the formats choice. I still am.


Ultimately, I switched to a 512 Mib CF, incidentally formatted with sudo mkfs.vfat -F 32 /dev/sdmadram1


(http://orgams.wikidot.com/local--files/pictures/xmass-cf.jpg)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 07:43, 23 April 20
  • Is FAT32 ok on a 128 Mib partition? Some sources says the minimum is 260Mib.
  • If it is, why deal with FAT16 at all, which leads to slower and slower writes.
32 MB ist the Minimum (my Windows10 Formats the 128MB media without Problems and
CubeMDOS detected them without a Problem, so I'm very intersting in the Image from @beb (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1105) )

https://en.wikipedia.org/wiki/File_Allocation_Table#FAT32
https://superuser.com/questions/1310927/what-is-the-absolute-minimum-size-a-uefi-partition-can-be

Yes correct, the FAT16 writes goes slower and slower and slower and.....
Additional you have a problem to show the free-memory (it's IMHO too slow)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 08:32, 23 April 20
Thanks for the confirmation. I might ask again in one year!


Regarding:
Quote
- Globs doesn't work as in AMSDOS (dir+era)
  E.g. |DIR,"*.BAK"
  E.g. |ERA,"*.BAK"


This could be solved by delegating the glob mechanism, as suggested here: [size=78%]https://www.cpcwiki.eu/forum/applications/i-wanna-be-your-dos/ (https://www.cpcwiki.eu/forum/applications/i-wanna-be-your-dos/)[/size]
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 09:33, 23 April 20
Regarding:

This could be solved by delegating the glob mechanism, as suggested here: [size=78%]https://www.cpcwiki.eu/forum/applications/i-wanna-be-your-dos/ (https://www.cpcwiki.eu/forum/applications/i-wanna-be-your-dos/)[/size]

DIR,*.BAK already works,
ERA,*.BAK is on the todo-list, but with a very-very-very-low-priority (not in 2020, Maybe 2021)

Yes, i saw you prev. post, yes it's interesting BUUUTTTT you will get a lot of Problems, when you check game-compatibillty (is the most important thing for me).
Programming an Mass-OS-DOS is a heavy fight against Crackers ;-)
=> You must accept a lot of compromise (e.g. the next Version will be come without a line in the Amstrad-Booting screen -> increase the game-compatibillty)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 10:18, 23 April 20
I was also confused by the formats choice. I still am.
  • Is FAT32 ok on a 128 Mib partition? Some sources says the minimum is 260Mib.
  • If it is, why deal with FAT16 at all, which leads to slower and slower writes.
FAT32 require a less a 32MB partition. Not Mib (bit) but MiB (Byte) if you want to be a better geek!  ;D
And true, the FAT16 if slower. I will provide a 512MB DOM to Beb ASAP (waiting the ITX-CPC).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 12:44, 23 April 20
Hi!
Oh a typo. FAT32 is fine up to 32 GB (or as you mean less than 32 GB).  :) Ok, this is only true for MS Windows 2000, in theory FAT32 can do up to 2 TB (for later OS).  ;) ;)
Therefore all storage media I buy for my CPC are 32 GB, and they're cheaper now.  ;D
 
EDIT: Oh, I see, the minimum requirement for FAT32...

- Smaller than 512 MB: FAT16
- Between 512 MB and 2 GB: FAT16 or FAT32
- Bigger than 2 GB: FAT32

Programming an Mass-OS-DOS is a heavy fight against Crackers ;-)
=> You must accept a lot of compromise (e.g. the next Version will be come without a line in the Amstrad-Booting screen -> increase the game-compatibillty)
A line in the boot screen is fighting crackers? Oh crap, FutureOS got four lines in the boot screen! They'll hate it!  :o :o :o
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 13:05, 23 April 20
in theory FAT32 can do up to 2 TB (for later OS).  ;) ;)


 
EDIT: Oh, I see, the minimum requirement for FAT32...

- Smaller than 512 MB: FAT16
- Between 512 MB and 2 GB: FAT16 or FAT32
- Bigger than 2 GB: FAT32
FAT32 could make also sense on Medias < 512MB (it's faster)
I personally only use FAT32 on my CPC.

Btw. for the SF3 you can use 2TB Media's for your CPC with CubeMDOS (ok, not tested).
XMASS is limited to 127GB


A line in the boot screen is fighting crackers? Oh crap, FutureOS got four lines in the boot screen! They'll hate it!  :o :o :o
It's an one example of one fight i have finished.
For FutureOS it's only important, when you want to install them at ROM7  ;D
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 13:12, 23 April 20
Holy crap! That's the problem to be compatible to the native OS. There's just way too much one needs to take in accound. But you're getting forward in big steps. Yesterday by chance I worked with CubeMDOS and it could even delete an 153 MB big file from the SF3 USB stick. Great!  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 21:26, 23 April 20
EDIT: Oh, I see, the minimum requirement for FAT32...
- Smaller than 512 MB: FAT16
- Between 512 MB and 2 GB: FAT16 or FAT32
- Bigger than 2 GB: FAT32
Microsoft Windows use by default FAT16 for mass-storages under 32MB and FAT32 over (16MB was possible before Windows 7)
All those limitations are arbitrary... FAT16 is not recommended over 64/128MB, because the minimum cluster sizes for little files (<1K)
https://support.microsoft.com/en-us/help/140365/default-cluster-size-for-ntfs-fat-and-exfat (https://support.microsoft.com/en-us/help/140365/default-cluster-size-for-ntfs-fat-and-exfat)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 21:49, 23 April 20
There seem to quite different docs out there.
Anyway. What's the reason for FAT32 being faster than FAT16?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: beb on 22:19, 23 April 20
Ok, FAT16 is working... successful formatting. I don't touch anything anymore.

Trouble with Orgams, until I patch the rom with "config".
Maybe someone want to write a doc ??? :)

thanks
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 23:09, 23 April 20
Ok, FAT16 is working...

successful formatting. I don't touch anything anymore.
Nice to hear   :)

.. until I patch the rom with "config".
Maybe someone want to write a doc ??? :)
See "CubeMDOS120120b.txt"

(ok, i move the CONFIG.BAS-Information in the TXT also to the beginning of the TXT-Doc)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 12:55, 24 April 20
Compatibility: Fear enough! I use my CPC octo-daily to code, so I'm biased towards fast and convenient facilities, not game launching :)
I appreciate the fact you offer the choice (v1 vs v2). Nit: the config message isn't very clear. Suggestion:
"Default to v1? It improves game launching compatibility, but requires to type |v2 to use Orgams and Symbos (Y/N)".



Crackers don't have much thing to crack anymore. They could use their retirement time and insane amount of money to patch their sloppy floppy loaders. Some of them don't even work on B: drive!


Glob: having an helper ROM doing the proper thing for globs would actually increase compatibility!
By the way, it would be great to follow unix behavior ("*" means everything regardless of extension) rather that the crappy msdos one.
Never in my life I have used "*" to match "*.   ".




United we stand: This is nice that both CubeMDos and M4 provides the same UDIR RSX than AcmeDos. I'm curious why Syx chose this callback approach rather than providing DIR_OPEN + DIR_GET_NEXT which doesn't require to poke in memory and deal with ROM re-connection.


I'd like to know: which issues did you encounter with Orgams handling of headerless files? Or: what did I do wrong?


Meta: What's with this spurious [size] markup everywhere?[/size]
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 13:54, 24 April 20

Compatibillity is for me an very big goal (Games & Syntax)
It doesnt matter, if i like the actual AMSDOS-Handling-Syntax or not.
(e.g. you will see a little side-project of me "Duke's Telnet-Client" working on both WIFI-Cards with an
driver-like structure ("RSX"  :D ) - compatibillity, compatibillity, compatibillity....)
(maybe later i will start a second side project like that)

Helper ROM doing the proper thing for globs would actually increase compatibility.
Hmm, IMHO no, because Games will init ROM7, which is the main Mass-Storage OS - and then? The Helper-ROM must handle this and init the correct MassOS, with the correct parameters. (a lot todo)
The memory-handling inside a Game-Program is terrible enough, you can't imagine how difficult it could be, to find free RAM, which you can use and what to do, when a game thinks the same  :o ???


United we stand: This is nice that both CubeMDos and M4 provides the same UDIR RSX than AcmeDos. I'm curious why Syx chose this callback approach rather than providing DIR_OPEN + DIR_GET_NEXT which doesn't require to poke in memory and deal with ROM re-connection.
What do you think, long long time ago, in a long forgotten century who has working together with Syx for this part and why this RSX was programmed?  ;D
And with Duke for the same RSX  ;D
And with SOS for the same RSX  ;D
(you can get an tip inside http://www.spinpoint.org/cpc/m4info.txt)

(This callback approach was at that time the best idea and for compatibillity reasons the best choice for M4DOS+CubeMDOS)


I'd like to know: which issues did you encounter with Orgams handling of headerless files? Or: what did I do wrong?
I do not use Orgams.
When there is an error, please report it here in an separate post. I will take sometimes a closer look (actual i work on the next release and can't include more things , else i will never be finished)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 14:16, 25 April 20
Compatibillity is for me an very big goal (Games & Syntax)


I am also all for compatibility and uniformisation, when it empowers interoperability.
Compatibility with legacy crap, I'm less enthusiast :)


Quote
(e.g. you will see a little side-project of me "Duke's Telnet-Client" working on both WIFI-Cards with an
driver-like structure ("RSX"  :D ) - compatibillity, compatibillity, compatibillity....)


Sweet! Tell us more!


Quote
Hmm, IMHO no, because Games will init ROM7, which is the main Mass-Storage OS - and then? The Helper-ROM must handle this and init the correct MassOS, with the correct parameters. (a lot todo)


Well, I'm not sure to understand the issue.
Orgams & 1A: I was referring to your doc:


Quote
improved 1A-Handling (Orgams)


What was wrong?



Also in the doc:


Quote
Only with HXC-Firmware (at the moment FlashFloppy is not supported!).


Why is that? What is missing with FF?


BTW, when I load something in |HA mode, the device displays 'W' as if it were writing. Troubling!
(Gotek + Firmware FF v0.9.19a).


Thanks again for the great work,
Take care!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 21:05, 27 April 20
Today's requests:
Thanks & Cheers!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 23:19, 27 April 20
Today's bug report:
To reproduce: DISC_IN_OPEN, then DISC_IN_CHAR: 129th byte is read instead of first one.


(*) It can happen by coïncidence that the &80 first bytes looks like a valid header (witch correct checksum etc), but it's extremely rare and wouldn't occur on 4 files  in a row (Symbos ROMs for that matter) I guess.


Don't forget to drink!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 23:34, 27 April 20
Files starting with more than &43 Bytes of &00 provide a "wrong-valid" header, because the checksum it 0. Under FutureOS I catch that problem by checking if the checksum (of bytes 0 to &42) equals 0. If yes, it's not a header, rather a picture.  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 23:45, 27 April 20
Why not checking all the bytes are 00?
Your heuristic might be wrong 1 times every other 256!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 23:47, 27 April 20
Why not checking all the bytes are 00?
Your heuristic might be wrong 1 times every other 256!
Not needed, a header contains file name, file length. Both are non-zero. So the checksum can't be 0. I guess I tested thousands of files (during decades), never had a problem.  :)


EDIT: Even if not, headers always contain some bytes being greater than zero, so the checksum is too. Thrust me.


EDIT2: I offer eight bits (Bitburger pils beer) to eveybody being able to send me a file with a zero-header - but please not something being purely constructed for the purpose.  :) :) :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 00:13, 28 April 20
Oh you're right, that's a 16-bit checksum which is just a sum.
I agree that if it's 0 it implies previous bytes are 0!


I encountered once an headerless file with "wrong-valid header", it took me some times to figure it out.

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 00:15, 28 April 20
  • mdr073: First &80 bytes of a header-less file on |HA are consumed as a header. (*)


I don't know if it"s related, but I get some "Drive Missing" and i must (R)etry.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 10:44, 28 April 20
Today's bug report:
  • mdr073: First &80 bytes of a header-less file on |HA are consumed as a header. (*)
To reproduce: DISC_IN_OPEN, then DISC_IN_CHAR: 129th byte is read instead of first one.


(*) It can happen by coïncidence that the &80 first bytes looks like a valid header (witch correct checksum etc), but it's extremely rare and wouldn't occur on 4 files  in a row (Symbos ROMs for that matter) I guess.


Don't forget to drink!

Okay, a lot  :o to read & check from you - but big thanks!!!  :D


First answers (yes, some are open):

- "Duke's Telnet-Client" working on both WIFI-Cards
  https://www.cpcwiki.eu/forum/programming/wifi-compatibility-between-the-m4-symbiface-3-using-telnet-as-an-example/
  My vision of compatibillity.
  Maybe, depends on the Progress of the SF3-Firmware and my joy/fun (what to do next), Maybe i will make an second project like that.

- Helper ROM:
  Yes, normally (nearly) everything is solveable (but with amount efforts which could be uninteresting).
  In your Example you must cascade up to three ROM's: Helper, Cube, AMSDOS (dont forget to start games from floppies)
  And this during an ROM-Init7

- improved 1A-Handling (Orgams)  "What was wrong?"
  Sorry, cant remember  :-[

- "at the moment FlashFloppy is not supported"
  Bug in the documentation   :D
  (will be removed)

- "BTW, when I load something in |HA mode, the device displays 'W' as if it were writing. Troubling!"
  Yes, Correct, that's the way of communicate with the HXC/FF  ;)

- mdr067: Display directories in lowercase. Or Titlecase, like in SymbOS!
  I Change this, to get Windows compatibillity.
  You can use |DIR to get the longnames of the Dir's.

- mdr069: Display free MiB along with "Drive D:"  to save one display line. And/or only when < 1 MiB.
  Hmm, i take a look later

- mdr070: Handle paths: run"/tool/dirscan" (like in ImpDos!).
  Hmm, i take a look later

- mdr071: Switch to D when using |CD (I have one strong case why one should do that).
  Why?  (because my ROM is full and with this function i have Control both mode (normal Storage & HXC))

- mdr073: First &80 bytes of a header-less file on |HA are consumed as a header. (*)
  That's new  :( , yes Maybe a bug - i will compare this to AMSDOS

- I don't know if it"s related, but I get some "Drive Missing" and i must (R)etry.
  Yes, i know this. I hope the next Version will be solve that.
  I found an bug & fixed (why HA had ever even worked before??)
  => should be more stable
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 13:57, 28 April 20

Thank you for addressing each point!

- Helper ROM:
  Yes, normally (nearly) everything is solveable (but with amount efforts which could be uninteresting).
  In your Example you must cascade up to three ROM's: Helper, Cube, AMSDOS (dont forget to start games from floppies)
  And this during an ROM-Init7
That's true! Good thing the Z80 is pretty fast :)

Quote
- mdr067: Display directories in lowercase. Or Titlecase, like in SymbOS!
  I Change this, to get Windows compatibillity.
  You can use |DIR to get the longnames of the Dir's.
I understand that. I was just taking about the display. Since it's case insensitive anyway, that would be nice.


Quote
- mdr071: Switch to D when using |CD (I have one strong case why one should do that).
  Why?  (because my ROM is full and with this function i have Control both mode (normal Storage & HXC))
Actually, that might give you some space (no check, no error message!).
That's basic UX! When you want to get into a directory, obviously you want to go the device that supports directories.
Before (3 steps):
After (1 step):


Quote
- I don't know if it"s related, but I get some "Drive Missing" and i must (R)etry.
  Yes, i know this. I hope the next Version will be solve that.
  I found an bug & fixed (why HA had ever even worked before??)
  => should be more stable
Great to hear that. Since your doc (.txt) is the reference point, it would be sweet to be up-to-date with the latest known issues!


New requests :)


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 14:13, 28 April 20
  • Having a fast format option for FAT32 128MiB. (Popular request by the way!)
The main problem of any programs called "DOS or OS" on CPC ... Not able to do the first required task: detect the capacity and format a drive.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 15:21, 28 April 20
I agree heartfully, especially when you don't do use your mass storage to do any transfert!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 16:25, 28 April 20
Quote
- "at the moment FlashFloppy is not supported"
  Bug in the documentation   :D
  (will be removed)
It might still be true:


Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: TotO on 01:30, 29 April 20
I'm curious why SyX chose this callback approach
It was a fast hack made to allow SOS to do tests for his Norton Commander Clone project.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SyX on 02:29, 29 April 20
I'm curious why Syx chose this callback approach rather than providing DIR_OPEN + DIR_GET_NEXT which doesn't require to poke in memory and deal with ROM re-connection.
The reason was because one of the main testers in the real machine, SOS,  was working in a "norton commander clone" and he needed that functionality.

SOS helped me a lot with his tests, without his help and the other test guys, it would have been impossible to release AcmeDOS at all. Mainly, because in those days my X-Mass prototype was lost in the brazillian postal service... I only received it 6 months after AcmeDOS was published. And WinApe hard disk support it didn't work at all, Richard only fixed it after my reports of a few bugs that I found in the emulation. Then AcmeDOS was coded without being able to make any tests at all, I was not totally blind because I built a tool for building memory snapshots where I inserted in the RAM the disk sectors that I needed in that moment... yes, I always have been that crazy :P

Maybe |UDIR was not the most sensible thing to do, but this 5 minutes hack for getting file/dir entries was enough for SOS and gave enough flexibility for with a 3 bytes patch anybody could process the information that this function produce for adjusting at their necessities. Even if the patch is ugly, it is using an RSX for adding extra functionality; this is the Amsdos way of adding extra functionality. And that always was important for me, AcmeDOS main goal was/is/will to be Amsdos and firmware compatible and because that try to use the small amount of RAM possible for its internal variables (there is not an ARM microcontroller rocket launcher where I can put those variables in the X-Mass board :P); and those variables live in the only place that you can steal from the OS without producing compatibility problems (well, every old bad crack crunched with cheesecruncher is going to fuck that, but it is always possible to get a better file version of the software that you want to install).
Internally my api has the usual functions:
1.- Goto to the first file/dir entry in the folder that is not . or ..
2.- Get the actual file/dir entry.
3.- Get the next file/dir entry.
Infact the main code for this RSX is:
Code: [Select]
;----------------------------------------------------------------------------------
; |udir (DEPRECIATED); This temporary hack it will disappear with the publication of
; the Posix interface in the 1.0 release.
;----------------------------------------------------------------------------------
xmass_cmd_udir
    ; Initialise the buffer used for formatting a catalog entry
    LD   DE,AMSDOS_RECORD_NAME_BUFFER + 2
    CALL add_de_iy
    LD   A,' '
    LD   (DE),A                             ; Mark as not valid name

.dir_no_args
    CALL fs_goto_first_dir_entry
    RET  NC                                 ; Hardware Error
    OR   A
    JR   NZ,.exit_udir
   
.loop_get_dir_entry
    CALL fs_get_dir_entry                   ; line list loop starts here
    RET  NC                                 ; Hardware Error
    OR   A
    JR   NZ,.exit_udir                      ; end of dir?

    ; Process catalog entry
    ; HL = Location of null terminated filename string
    ;  B = File flag (1 = directory, 0 = file)
    CALL CAT_HANDLER
   
.continue
    CALL fs_goto_next_dir_entry
    RET  NC
    OR   A
    JR   Z,.loop_get_dir_entry
.exit_udir   
    SCF
    RET
And as you can see in the code, this function was going to be depreciated with the release of the version 1.0. And I am practically sure that
I told that to SOS in the email where I explained how to use UDIR.

This unpublished version 1.0, called SOS (SyX Operating System) those days includes a LOT of extra things (you will even need to flash the basic rom for my patched one), but I am not going to fill this post with vaporware... specially because there is not publishing date at all. My priority those days should be to finish our racing game and being a father of a newborn during this pandemia, it doesn't let time for coding too much cpc things.
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 10:22, 29 April 20
I understand that. I was just taking about the display. Since it's case insensitive anyway, that would be nice.

Handling of Longnames on an 64KB (only a few Bytes avail for Cube)-4MHZ-8Bit-CPU-16KB ROM-Computer is a torture.
Yes, this Point will be nice (Display on CAT + CD into), but sorry, no  :(

That's basic UX! When you want to get into a directory, obviously you want to go the device that supports directories.
Before (3 steps):
  • |cd,"/toto"
  • Error message. Damn!
  • |d
  • |cd,"/toto"
After (1 step):
  • |cd,"/toto"
Hmmm…. I must think about that

Great to hear that. Since your doc (.txt) is the reference point, it would be sweet to be up-to-date with the latest known issues!

Yes, correct, i should upload an WIP.TXT.
At the Moment, which should work:
- DSK: 464 without Floppy
- DSK: Support of "Parados80", "Vortex" (do you need more formats?)
- DSK: |DIR displays the DSK-Content
- Remove the Booting-Message, to increase the Game-Compatibillity (Super Skweek)
- HXC detection bugfix (should be more reliable), Slot-Handling (|HSL, …) now works
- Code-Restructure of HXC-Interface (now needed the 2nd DSK-ROM for operate)
todo:
- Added SF3-Features for higher Game-Compatibillty



  • Having a fast format option for FAT32 128MiB. (Popular request by the way!)
  • Having some diagnostic tool, when an externally formatted/populated device isn't recognized. What was expected and not found?
1)
I know, that this was often requested. My general concept is, that you have great format-Tools in Windows, Linux, MacOS, ….
(much more better then i can program)
The only Point which i think to change, is to implement more presets of formats.
But i need an image of an previously formatted DOM to do that.
(someone can send me an Image)
2)
No, too much complicated. CubeMDOS should detect all(!) first partitions (if not i like to check it). When it's not detected, then you have an bigger Problem, which will not easy to fix. It doesnt have an Benefit, when the user know's what's going wrong - and the but: all 1st partitions will be detected, so there is no case in "not recognizing"  ;D
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 10:29, 29 April 20
Hey SyX!!!!!!!!

nice to see you  :D

Maybe |UDIR was not the most sensible thing to do, but this 5 minutes hack for getting file/dir entries was enough for SOS and gave enough flexibility for with a 3 bytes patch anybody could process the information that this function produce for adjusting at their necessities.
Yes, "Keep-it-short-and-simple" is a good strategy on 8Bit-Machines  ;D

called SOS (SyX Operating System)
:o 
hahahahahha  ;D ;D ;D ;D ;D

being a father of a newborn during this pandemia, it doesn't let time for coding too much cpc things.
Great news! My congratulations and all the best for you (I hope you are all healthy).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 12:20, 29 April 20
Handling of Longnames on an 64KB (only a few Bytes avail for Cube)-4MHZ-8Bit-CPU-16KB ROM-Computer is a torture.


I'm just talking about lowering the shortnames. And / or:
Also, size-coding tip: for routines called from a lot places, use RST mechanism. E.g. call toto:word tata  ; Pass tata as parameter.

Quote
Yes, correct, i should upload an WIP.TXT.
At the Moment, which should work:
[...]
Sounds great! Is it available for testing yet?
BTW, when a bug is discovered and confirmed, the main doc.txt should be updated too!


Quote
I know, that this was often requested. My general concept is, that you have great format-Tools in Windows, Linux, MacOS, ….
(much more better then i can program)
Well, i cannot plug the DOM on the PC I have access to!
Also, it's very convenient to be able to do that from the CPC. A (d)os should operate (disks)!




Hey SyX, good to see you here!
Thank you very much for the explanation. It's good to know the legacy. I agree that pragmatism is useful.
Congrats for the kido, have fun!


Looking forward to SOS. And SOS!


Maybe we should name a project "Super Yummy Xplorer".
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 20:12, 29 April 20
- DSK: Support of "Parados80", "Vortex" (do you need more formats?)
Thanks a lot for the great Vortex standard format. :) :) :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: beb on 22:19, 29 April 20
Ok, You have to format your device FAT32 with 1kb cluster... And it work well...


Until I tried to copy a 110kb Ascii file.. and it doesn't load... :(
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 23:48, 29 April 20
Thanks Bob for the update.


There is an open issue (see "Known issues" in the doc):
Quote
- ASCII-Files >64KB are truncated   


Also, the YANCC copier used to truncate files > 32KiB
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SyX on 02:14, 30 April 20
Thanks guys! This real life project is really hard and consume all my energy, but I have not enough words to describe the happiness that brings me, hehehe.

Ok, I have stolen a few minutes more to read this thread; last night I only answered because Richard sent me here, hahaha.

First: Congratulations SOS! Great Work! :) Your ROM supports FAT16 and 32 and a lot of devices, I will test CubeMDOS when I get some time.

For me, it has been a nice surprise (mind note: review all those nice projects in the international CPC community from the last 5 years ;) ). And the good thing of your amazing work is that I don't need to hurry up with mine, I even think that the CPC community doesn't need another FAT rom. That means that now I feel free for experimenting a few funny things that I have in mind.

For example, I replaced FAT16 by exFAT after Microsoft made the specifications free, FAT32 didn't make too much sense for the original DOM size... and of course, there is a few nice features that exFAT brings to the FAT world. But I never have been too happy about using FAT in a Z80 machine; I would like to support other filesystems that can be mounted easily under Linux, Mac and Windows. Now, I have that chance and I can refactor the code for extracting the filesystem handler, hehehe.

A lot of silly ideas for when I get some time.

Thanks for your work :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 16:25, 30 April 20
...
 But I never have been too happy about using FAT in a Z80 machine; I would like to support other filesystems that can be mounted easily under Linux, Mac and Windows. Now, I have that chance and I can refactor the code for extracting the filesystem handler, hehehe.


Well, I had the same idea for FutureOS. A filesystem which fits the needs of the CPC. What kept me doing something like that was the question how to fill the media up with data. It would need a PC program for it. And I don't program on PC.
However if there would be a possibility to fill up a device with data from the PC side then that old idea would make new sense.  :)


FAT is not so great anyway, just think about how it stores long filenames. A nightmare. It's main advantage is that it can be used be most machines/computers. But that doesn't make it a great fs. per se.

Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SyX on 22:05, 30 April 20
Sorry by the off-topic...
And I don't program on PC.
You should Stefan, those days a pc is nothing else than other tool for CPC coding.

Take a look to the kind of things that you can do using a serial port interface and an NMI generator device in the CPC ;)
(https://syx.neocities.org/images/debugger_session.png)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 00:52, 01 May 20
Sorry by the off-topic...You should Stefan, those days a pc is nothing else than other tool for CPC coding.
Sure, like steroids are just another tool to build muscle (:
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 11:00, 01 May 20
Sorry by the off-topic...You should Stefan, those days a pc is nothing else than other tool for CPC coding.

Take a look to the kind of things that you can do using a serial port interface and an NMI generator device in the CPC ;)
(https://syx.neocities.org/images/debugger_session.png)
What were are seen in your Screen?
An NMI-ROM? Is the Source available?
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 16:18, 01 May 20
Sorry by the off-topic...You should Stefan, those days a pc is nothing else than other tool for CPC coding.
Well, to be honest... The limiting factor is always time. So I decided to spend my "computing" time to actually do something on the CPC. If I would start to learn how to write a tool to put files on a proprietary file system using the PC then this would take me a loooooong time. Well, it's me, others may be way quicker.  ;D

Of course you're right, today the PC could work wonders.

However, my philosophy was always to be able to do everything on CPC. One main reason to develop FutureOS actually.

In reality until now I couldn't finish this goal due to a bunch of reasons I don't want to discuss in public.

But in principle it's doable, Prodatron showed it with SymbOS. The CPC can do everything. I really do adore his efficiency in coding. Mine was the same 25 years ago, but then real life happened.  :laugh:

EDIT: Sorry, I guess I completely derailed this thread now.  :-X
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SyX on 17:39, 03 May 20
What were are seen in your Screen?
An NMI-ROM? Is the Source available?
PM send! ;)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 09:43, 11 May 20
- mdr070: Handle paths: run"/tool/dirscan" (like in ImpDos!).
  Hmm, i take a look later


It would also enable to move files. E.g. |ren,"/newdir/","/olddir/toto.bas"
That's what I need most of the time (it's a pity to have to resort to a slow copy).
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: m_dr_m on 08:08, 15 May 20
NB: the directory is correctly changed. 8224 is decimal for &2020, which is highly suspicious!
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 09:10, 15 May 20
  • mdr077: |cd,"orgrel/ee"  displays "8224 ".
NB: the directory is correctly changed. 8224 is decimal for &2020, which is highly suspicious!

Thanks, i saw this only one time before, but i missed to freeze my actual image to have an reproduceable envoirement  :(
(you can't make an image of your DOM?)

Btw. MoveDir, yes it's on my todo-list, but priority extremly-low (this year "no" - maybe 2021/2022/2023)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: GUNHED on 17:04, 15 May 20
Renaming DIRs is IMHO a great feature.  :)  But there are always different ways to reach a goal.  :)
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: zhulien on 16:31, 19 May 20
Is there any chance you can support m4 storage in cubedos? Would you and Duke perhaps work together to allow that?  Maybe all fs code of m4 could move to cubedos and the m4 rom be split into 2 versions? Standalone with fs support and cubedos version?  It would be way cool to be able to use all my storage devices together...
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: SOS on 16:48, 19 May 20
Is there any chance you can support m4 storage in cubedos?

I'dont think so + see my Reply
https://www.cpcwiki.eu/forum/applications/cubeios-fat16fat32-rom-for-the-cpc's-with-xmass/msg182179/#msg182179
Additional: It's problematic, that you only can have one ROM7-ROM, so you get more freebie Troubles....
So you must check for both ROMs to init and think about, which is the leading one after an ROM7-Reinit .. :(
For directly Integration of M4-Card, Maybe could be possible (C_SDREAD exist), but i dont know, if this can cause Troubles on M4-Side
Title: Re: CubeMDOS / FAT16+FAT32-OS - for XMASS, Symbiface_2+3,HXC/FlashFloppy
Post by: Duke on 20:35, 19 May 20
For directly Integration of M4-Card, Maybe could be possible (C_SDREAD exist), but i dont know, if this can cause Troubles on M4-Side
It should not  be a problem, just wrap the C_SDREAD and C_SDWRITE to your FAT I/O and you could set M4 rom to a higher slot than CubeMDOS.