Quote from: Kris on 19:39, 25 March 18At the moment i have no check against the real-media-size.
I just give it a trial but formatting a 128Mb DOM give wrong size results...If I choose FAT16 format then I own 400Mb ??
Quote from: Fessor on 22:23, 10 April 18http://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)
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?
Quote from: GUNHED on 17:13, 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?
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
Quote from: HAL 6128 on 16:25, 02 October 1832 Bit = 4294967295 Sectors can be assigned, size 2199023255040 Bytes = 2,19 TB
Max. 32Bit LBA addressing possibilities means 3 TB or 28Bit 128GB? (...not an important question for a CPC) :P
Quote from: netmercer on 02:07, 13 November 18
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.
Quote from: RockRiver on 10:29, 20 November 18Yes, should be run (i can't test it - i have no SF2).
Symbiface II (IDE) support???
Quote from: netmercer on 02:07, 13 November 18Bugfix sent to netmercer.
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 from: m_dr_m on 16:55, 20 February 19Strange, i will later test this, please inform me, when you can reproduce that
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.
Quote from: m_dr_m on 16:55, 20 February 19??
4/ Be able to use FAT with 128MB
For interoperability and since you say saving would be faster.
Quote from: m_dr_m on 16:55, 20 February 19It's a similar feature.
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.
Quote from: m_dr_m on 16:55, 20 February 197: Oh, should work :( (but doesnt)
7/ Globs doesn't work as in AMSDOS
E.g. |DIR,"*.BAK"
8/ |ERA doesn't work with globs.
E.g. |ERA,"*.BAK"
Quote from: m_dr_m on 16:55, 20 February 19No it's canceled, i'm thinking about this feature, but IMHO i Need a 40mhz instead of a 4mhz-CPU.
9/ Sort directory.
It should take less than 1 frame on a 4Mhz Z80 :)
Quote from: SOS on 18:03, 20 February 19I reproduce ~50% of the time.
> 2/ Inconsistent |A
Strange, i will later test this, please inform me, when you can reproduce that
Quote from: SOS on 18:03, 20 February 19> 4/ 128Mb FATHere is what I've understood. I might be wrong:
??What do you mean exactly?
I support the original 128MB formatted media's from ACMEDOS.
Quote from: SOS on 18:03, 20 February 19> 9/ Sorting directoryNot counting the 2ko for cat, cannot we reuse some AMSDOS buffer (like the one used to read sectors)?
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.
Quote from: m_dr_m on 20:52, 20 February 19ACMEDOS 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.
Quote from: m_dr_m on 20:52, 20 February 19Could you describe the steps a Little bit more?
I reproduce ~50% of the time.
* Booting on D.
* Working on D.
* Resetting to exist Orgams.
* |A
Quote from: m_dr_m on 20:52, 20 February 19
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.
Quote from: m_dr_m on 20:52, 20 February 19hmmm....
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)?
Quote from: m_dr_m on 20:52, 20 February 19(thanks)
I could do the sorting routine, if you wish!
|mkdir,"tmp":|cd,"tmp"
for i=1 to 99:print i:save str$(i):nextQuote from: Fessor on 00:08, 21 February 19That's an interesting approach, modulo some caveats:
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*"
Quote from: m_dr_m on 01:29, 21 February 19the "firmware zone" is zeroed could be a problem.
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.
Quote from: m_dr_m on 01:29, 21 February 19I can reproduce that now (thanks), crashes only on FAT16.
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.
Quote from: m_dr_m on 01:29, 21 February 19FAT32 is not restricted to 128MB, you can use large media's.
4/ FAT format
I'm not sure to see why FAT32 format couldn't be restricted to 128Mb, so that:
• |FREE is accurate
Quote from: m_dr_m on 01:29, 21 February 19I have checks against possible overwriting-issues, so this "should" be not occur.
• More importantly, disc full is properly detected and no overwriting occurs!
Quote from: m_dr_m on 01:29, 21 February 19Much too few.
And not that big in memory! Tell me how much space do you have (:
Quote from: m_dr_m on 01:29, 21 February 19I check this later
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?
Quote from: TotO on 20:31, 21 February 19It's not a strange limitation, it's a logical one.
The FAT32 strange limitation is to not be able to support partitions under 32MB. :-\
Quote from: gerald on 16:17, 23 February 19There 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).
Quote from: TotO on 16:28, 23 February 19That's laziness ;D . There is not much to do to support FAT12/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).
Quote from: TotO on 16:28, 23 February 19Next, 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.
Quote from: angelcaio on 14:07, 23 February 19Hi, strange things you reported :o
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.
...
Quote from: SOS on 10:00, 21 February 19Hum! I like my CPC self-contained (:
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, ....
Quote from: SOS on 10:00, 21 February 19The FREE-Display on FAT32 must be correct, else it's a strong indicator, that something is going very wrong!No problem so far, as I am only using ~10Mb for now! Simply the doc mentioned:
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?
QuoteThree presets of formats you can chooseBut as I understand now, this was a limitation of format.bas and not CUBEOS's.
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)
|cd,"/plad"
|o <- OK
|cd,"/plad/archive3" <- existing dir
|o <- unknown command
Quote from: m_dr_m on 01:29, 21 February 19I checked Starkos.
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?
Quote from: m_dr_m on 09:20, 03 March 19
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?
Quote from: 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.
Quote from: 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).
Quote from: SOS on 13:09, 03 March 19You are very welcome!
First thanks about your mails, to make CubeMDOS better :D
Quote from: SOS on 13:09, 03 March 19Yep, fair enough, that's what I've thought.
So the Starkos-Author must be change his program to get a functional Massstorage-Application.
Quote from: SOS on 13:09, 03 March 19Oh, why is that, since FAT32 is better (faster access, less space wasted, more common...)?
For the 128MB DOM i will Always recommend the 128MB ACMEDOS FAT16-Format (1st Preset).
Quote from: SOS on 13:09, 03 March 19Btw. 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. (:
Quote from: SOS on 13:09, 03 March 19Ok, 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.
Quote from: SOS on 13:09, 03 March 19Actually the scenario with /plad/archive3 also fails at RESET.
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
Quote from: SOS on 13:09, 03 March 19Orgams make a memory restore of the high-memory.Maybe related to this bug: mailto:http://orgams.wikidot.com/bugs#toc40
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.
Quote1: CubeIOS
I think the exact ROM-Configuration could be important
Quote from: m_dr_m on 16:55, 20 February 19Since YANCC doesn't allow A to A copy, this request would have a very good utility/work ratio!
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.
Quote from: m_dr_m on 17:53, 03 March 19The Projects CubeMDOS+YANCC are not started as an open-source project
Another option to make CubeMDOS better is to release the source (:Yep, fair enough, that's what I've thought.
Quote from: m_dr_m on 17:53, 03 March 19Backward-compatibillity to ACMEDOS+IMPDOS.
Oh, why is that, since FAT32 is better (faster access, less space wasted, more common...)?
Quote from: m_dr_m on 17:53, 03 March 19The ROM's 9+12 i haven't found.
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).
Quote from: m_dr_m on 14:48, 21 June 19Thanks, for you too ;-)
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? (:
Quote from: SOS on 15:15, 21 June 19
- Make-Directory: Convert Directory-Names to Uppercase (else Directory can't read by Windows)
QuoteWhy not? It works like a charm in Amsdos.
- Cannot save an ASCII file larger than 64k. The result is truncated. (thnx m_dr_m)
=> But i must check, if this is solveable....
Quote from: m_dr_m on 15:46, 22 June 19:D :D :D :D
I would be happy to beta-test!
Quote from: SOS on 21:53, 23 June 19IMHO 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
(Version runs without an Problem in Winape)
Quote from: TotO on 14:53, 25 November 19We will see, very soon ;)
Nice. No DSK file with the ROM inside like for YANCC? :-*
Quote from: zhulien on 08:18, 07 January 20hmmm, it's problematic:
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?
Quote from: SOS on 20:18, 07 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?
Quote from: 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). :)
Quote from: Fessor on 22:44, 13 February 20Use |V2 for your code
Is it possible thate CubeMDOS changes / reset the configuration of the memory banks?
Quote from: SOS on 07:27, 14 February 20Reverted the code for tests, its working now.
Use |V2 for your code
Quote from: Fessor on 22:44, 13 February 20No 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.
... and I wondered in the WinApe debugger why code was overwritten and memory banks remained empty.
Quote from: GUNHED on 21:04, 14 February 20What do you mean with "software for emulators"?
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.
Quote from: Fessor on 14:42, 15 February 20For 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.
What do you mean with "software for emulators"?
Quote from: 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" ?
Quote from: lordoftime on 23:21, 12 April 20Hmm, its a problem, i do not have an C4CPC.
Does anybody have a version of this that can be run on a C4CPC?
Quote from: SOS on 11:16, 13 April 20It's a normal romboad with a twist.
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)?
Quote from: gerald on 13:35, 13 April 20So you can set CubeMDOS in ROM 131 and AMSDOS in ROM15 (in an external ROM-Board), so
- rom 131 is a mirror of upper ROM 7
...
Or completely replace ROM7, but then you lose floppy access
Quote from: SOS on 15:14, 13 April 20Yes, this should work.
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 ?!
Quote from: lordoftime on 16:46, 13 April 20Please, could you describe more, what is your Goal and which Hardware do you have?
ok and how do i go about doing this?
Quote from: lordoftime on 02:53, 14 April 20The Problem is, that (when i understand Gerald correctly) you need an ROM-Board to install custom ROM's.
I want to use this on my c4cpc cart and use my hxc as a mass storage device.
Quote from: lordoftime on 02:53, 14 April 20The HxC is a floppy disc emulator, it's not intended to be used for mass storage, since it's too slow for that.
I want to use this on my c4cpc cart and use my hxc as a mass storage device.
Quote from: lordoftime on 14:28, 14 April 20Yes, 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).
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?
Quote from: GUNHED on 11:34, 14 April 20The 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.. :-\
Quote from: TotO on 15:12, 14 April 20One of them is doable, but the other one a killer.
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.. :-\
Quote from: lordoftime on 14:28, 14 April 20Welcome! :) It can be a lot at once of course. Therefore we help. I don't know if you're mistaken. :)
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!
Quote from: beb on 11:36, 22 April 20The Format.BAS are a "Little Example" to Format an Media.
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.
Quote from: m_dr_m on 00:30, 23 April 2032 MB ist the Minimum (my Windows10 Formats the 128MB media without Problems and
- 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.
Quote- Globs doesn't work as in AMSDOS (dir+era)
E.g. |DIR,"*.BAK"
E.g. |ERA,"*.BAK"
Quote from: m_dr_m on 08:32, 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]
Quote from: m_dr_m on 00:30, 23 April 20FAT32 require a less a 32MB partition. Not Mib (bit) but MiB (Byte) if you want to be a better geek! ;D
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.
Quote from: SOS on 09:33, 23 April 20Programming an Mass-OS-DOS is a heavy fight against Crackers ;-)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
=> 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)
Quote from: GUNHED on 12:44, 23 April 20FAT32 could make also sense on Medias < 512MB (it's faster)
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
Quote from: GUNHED on 12:44, 23 April 20It's an one example of one fight i have finished.
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
Quote from: GUNHED on 12:44, 23 April 20Microsoft Windows use by default FAT16 for mass-storages under 32MB and FAT32 over (16MB was possible before Windows 7)
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
Quote from: beb on 22:19, 23 April 20Nice to hear :)
Ok, FAT16 is working...
successful formatting. I don't touch anything anymore.
Quote from: beb on 22:19, 23 April 20See "CubeMDOS120120b.txt"
.. until I patch the rom with "config".
Maybe someone want to write a doc ??? :)
Quote from: m_dr_m on 12:55, 24 April 20Hmm, 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)
Helper ROM doing the proper thing for globs would actually increase compatibility.
Quote from: m_dr_m on 12:55, 24 April 20What 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
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.
Quote from: m_dr_m on 12:55, 24 April 20I do not use Orgams.
I'd like to know: which issues did you encounter with Orgams handling of headerless files? Or: what did I do wrong?
Quote from: SOS on 13:54, 24 April 20
Compatibillity is for me an very big goal (Games & Syntax)
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....)
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)
Quote
improved 1A-Handling (Orgams)
Quote
Only with HXC-Firmware (at the moment FlashFloppy is not supported!).
Quote from: m_dr_m on 23:45, 27 April 20Not 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. :)
Why not checking all the bytes are 00?
Your heuristic might be wrong 1 times every other 256!
Quote from: m_dr_m on 23:19, 27 April 20
- mdr073: First &80 bytes of a header-less file on |HA are consumed as a header. (*)
Quote from: 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.
- mdr073: First &80 bytes of a header-less file on |HA are consumed as a header. (*)
(*) 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!
Quote from: SOS on 10:44, 28 April 20That's true! Good thing the Z80 is pretty fast :)
- 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
QuoteI understand that. I was just taking about the display. Since it's case insensitive anyway, that would be nice.
- 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.
QuoteActually, that might give you some space (no check, no error message!).
- 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))
QuoteGreat 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!
- 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
Quote from: m_dr_m on 13:57, 28 April 20The 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.
- Having a fast format option for FAT32 128MiB. (Popular request by the way!)
QuoteIt might still be true:
- "at the moment FlashFloppy is not supported"
Bug in the documentation :D
(will be removed)
Quote from: m_dr_m on 12:55, 24 April 20I'm curious why SyX chose this callback approachIt was a fast hack made to allow SOS to do tests for his Norton Commander Clone project.
Quote from: m_dr_m on 12:55, 24 April 20The 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.
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.
;----------------------------------------------------------------------------------
; |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 Quote from: m_dr_m on 13:57, 28 April 20
I understand that. I was just taking about the display. Since it's case insensitive anyway, that would be nice.
Quote from: m_dr_m on 13:57, 28 April 20Hmmm.... I must think about that
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):
- |cd,"/toto"
- Error message. Damn!
- |d
- |cd,"/toto"
- |cd,"/toto"
Quote from: m_dr_m on 13:57, 28 April 20
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!
Quote from: m_dr_m on 13:57, 28 April 201)
- 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?
Quote from: SyX on 02:29, 29 April 20Yes, "Keep-it-short-and-simple" is a good strategy on 8Bit-Machines ;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.
Quote from: SyX on 02:29, 29 April 20:o
called SOS (SyX Operating System)
Quote from: SyX on 02:29, 29 April 20Great news! My congratulations and all the best for you (I hope you are all healthy).
being a father of a newborn during this pandemia, it doesn't let time for coding too much cpc things.
Quote from: SOS on 10:22, 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.
QuoteSounds great! Is it available for testing yet?
Yes, correct, i should upload an WIP.TXT.
At the Moment, which should work:
[...]
QuoteWell, i cannot plug the DOM on the PC I have access to!
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)
Quote from: SOS on 10:22, 29 April 20Thanks a lot for the great Vortex standard format. :) :) :)
- DSK: Support of "Parados80", "Vortex" (do you need more formats?)
Quote
- ASCII-Files >64KB are truncated
Quote from: SyX on 02:14, 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.
Quote from: GUNHED on 16:25, 30 April 20And I don't program on PC.You should Stefan, those days a pc is nothing else than other tool for CPC coding.
Quote from: SyX on 22:05, 30 April 20Sure, like steroids are just another tool to build muscle (:
Sorry by the off-topic...You should Stefan, those days a pc is nothing else than other tool for CPC coding.
Quote from: SyX on 22:05, 30 April 20What were are seen in your Screen?
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)
Quote from: SyX on 22:05, 30 April 20Well, 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
Sorry by the off-topic...You should Stefan, those days a pc is nothing else than other tool for CPC coding.
Quote from: SOS on 11:00, 01 May 20PM send! ;)
What were are seen in your Screen?
An NMI-ROM? Is the Source available?
Quote from: SOS on 10:44, 28 April 20
- mdr070: Handle paths: run"/tool/dirscan" (like in ImpDos!).
Hmm, i take a look later
Quote from: m_dr_m on 08:08, 15 May 20NB: the directory is correctly changed. 8224 is decimal for &2020, which is highly suspicious!
- mdr077: |cd,"orgrel/ee" displays "8224 ".
Quote from: zhulien on 16:31, 19 May 20
Is there any chance you can support m4 storage in cubedos?
Quote from: SOS on 16:48, 19 May 20It 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.
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
Quote from: m_dr_m on 19:02, 11 January 21Hi there, yes a new version will be come, but things goes slow this days... :(
SOS, I wonder if a new release is planned any time soon! Happy new week!
Quote from: m_dr_m on 09:03, 21 January 21Yes ;)
Can you tell us more about it?
Quote from: m_dr_m on 09:03, 21 January 21:o ??? :D
For some motivation, a new CubeMDOS bug:
Quote from: m_dr_m on 09:46, 21 January 21Nice does your "+" means "OR" or "AND"?And means "and" ;)
I.e., will it run on Native CPC with a SF III, with no apes involved?
Quote from: m_dr_m on 09:46, 21 January 21F11-Key in Winape ;-)
What do you use to generate the NMI?
Quote from: m_dr_m on 09:46, 21 January 21I hope, i will write enough in the documentation ;-)
Is it documented somewhere?
Quote from: SOS on 10:38, 21 January 21Thanks for telling that, this information is missing in the SF3 documentation.
Right Blue Button on the SF3, below the display
|cd,"/lib"
|dir,"b*"
-> OK, lists all my files starting with B
|dir,"/lib/b*"
-> No result.Quote from: m_dr_m on 12:53, 25 January 21I don't think I already have reported this bug (mdr079):At the moment i do not support a mix of path + filename.
Code: [Select]
|cd,"/lib"
|dir,"b*"
-> OK, lists all my files starting with B
|dir,"/lib/b*"
-> No result.
Quote from: m_dr_m on 12:53, 25 January 21No.
Also, do you plan an UniDOS version? (:
Quote from: m_dr_m on 17:23, 03 May 21Do you touch to bank connections?Yes, but it's nearly on top on my todo-list, to deactivate this on the SF3 (i hope in this year)
Quote from: zhulien on 03:58, 04 May 21
What advantages of CubeDOS are there over UniDOS and vice versa?
Quote from: m_dr_m on 01:11, 23 May 21Hmm, this is more complicated as expected.
Request #1c: |getpath rsx should return "A:" in |a mode, and HXC path in |Ha / |Hb mode.
Quote from: m_dr_m on 01:11, 23 May 21&a700? you must get the correct address from &be7d.
* More consistent with other DOS
* |A / |D doesn't set current drive (&a700 by default) -> It makes hard to know programmatically which drive is active!
Quote from: SOS on 09:33, 13 November 18Yes |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