Yet Another Norton-Commander Clone (YANCC) for ACMEDOS+M4DOS+CubeIOS

Started by SOS, 07:53, 08 September 16

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

SOS

Quote from: francouai on 10:16, 17 January 18
How can be loaded a .DSK file when I have to type ùCPM ?
perhaps to use a pre configured short cut key on your sw?
At the Moment i have no Access to the M4-Board.
Is it actual possible (without my software) that you |CD into the DSK and then |CPM starts the (CPM-)Program in the DSK-Image?!
If yes, i will set a shortcut-key to my todolist.

zhulien

hi, does anyone know where to download the ACMEDOS rom from?

SOS

Quote from: zhulien on 18:32, 08 February 18
hi, does anyone know where to download the ACMEDOS rom from?
Yes, see first post "xmass08P.zip".

zhulien


SOS

Quote from: merlinkv on 00:25, 02 October 17
With M4 Board:
- One FDD as drive A. I can read it, but the CPC reboot when I try to copy files from<=> to M4-FDD
- Two FDDs. I can readn only A, but copy from<=>to M4-FDD also don't work

Please test the new version.


Quote from: francouai on 10:16, 17 January 18
How can be loaded a .DSK file when I have to type ùCPM ?
perhaps to use a pre configured short cut key on your sw?

I check the M4, it doesn't Support |CPM from a DSK-File (it loads from the floppy).
When M4 Support |CPM from a DSK, i will add them.

merlinkv


SOS

New Version, changelog:
130318b
- Fixed Unwanted starts of YANCC during Warm-Reset (e. g. ,,Monty on the Run")
- In rare circumstances, some files are copied empty.
- In rare circumstances, the ROM-Init of YANCC makes nonsense...  (e.g. in "12 Lost Souls")
- CubeIOS bugfix

MissionComplete

Great work, SOS!!

Especially the launcher works fine for me and is VERY comfortable. Congratulations.

My problem is with Yancc (last version 130318b).

I use M4 Board in a 6128, with the lower rom modified by Duke for more compatibility with games, in slot 31. Yancc rom is in slot 1 and launcher in slot 15 (Amdos in slot 8 and Parados in 7, M4 in 6).

When I type 3 or 4 (C or D, I have 2 FDD), I can't see the inside of the disks, but a folder called M4. To see the software in the disks, I have to delete the lower rom and let empty the slot 31. Then your software works fine and I can copy files between drives. But a lot of games are not compatible with this configuration of roms, sadly.

Is there any configuration to work with disks in Yancc and having the modified rom of Duke as lower rom?

Thank you!!

SOS

Quote from: MissionComplete on 19:33, 27 March 18
Is there any configuration to work with disks in Yancc and having the modified rom of Duke as lower rom?
I will test this (will take a few days).
When i can reproduce that, i bet i can patch this.
(if i have problems with replication, i will send you a PM for assistance)

MissionComplete

Quote from: SOS on 21:21, 27 March 18
I will test this (will take a few days).

@SOS

I think the problem is that the lower rom modified by Duke disables all drives except the sd, precisely in order to improve compatibility for games whome call the floppy. So, this is the unfortunated dilemma: more compatibility for games or visibility to manage files.

SOS

Quote from: MissionComplete on 22:32, 31 March 18
I think the problem is that the lower rom modified by Duke disables all drives except the sd, precisely in order to improve compatibility for games whome call the floppy. So, this is the unfortunated dilemma: more compatibility for games or visibility to manage files.
You can install AMSDOS e.g. in ROM 8, so you have still Floppy-Access.

It was a medium-good idea to hardcode AMSDOS to ROM 7 in YANCC   :picard: -> in the RC of the next version i've changed that (works in your configuration), but i will test a similar configuration with CubeIOS, if the floppies are still accessable.
(i think approx 2-3 Week?!)

MissionComplete

Quote from: SOS on 18:52, 01 April 18
You can install AMSDOS e.g. in ROM 8, so you have still Floppy-Access.


I have indeed AMSDOS in slot 8, but it looks like YANCC doesn't know it.

Thanks for the support and, again, congratulations for the wonderful software.

SOS

Quote from: MissionComplete on 13:47, 02 April 18
I have indeed AMSDOS in slot 8, but it looks like YANCC doesn't know it.

Please check the new version, problem should be solved.

MissionComplete

Quote from: SOS on 13:15, 15 April 18
Please check the new version, problem should be solved.
It works perfectly!!! Thanks. Now I can use the drives to copy files between them.
Sorry for the delay, but I was the las two months only with 464 an now I have my 6128 again.
Just a detail. In the changelog txt you say "Floppies not detected, when AMSDOS <> ROM 7". In muy case, it works with AMSDOS in ROM 8, not 7.
Thanks again!!!  ;D

SOS

Quote from: MissionComplete on 16:10, 02 June 18
In the changelog txt you say "Floppies not detected, when AMSDOS <> ROM 7". In muy case, it works with AMSDOS in ROM 8, not 7.
This is what i changed: "Floppies not detected, when AMSDOS <> ROM 7"

AMSDOS in ROM 8 is a very good choice...

m_dr_m

YARFYANCC (Yet Another Request For Yet Another Norton-Commander Clone)
Not to have to burn LAUNCH.ROM when you don't use the functionality.Anyway it's always nice to check the presence of additional ROM you rely on, so it's wouldn't add much work.BTW, why does the ROM have to be in a higher slot?

I'm also copying here the requests from CubeMDOS thread, for clarity.

5/ YANCC should have a 'Move' command
5a/ At least YANCC should retain the selection (like PARADOS copier).
42/ Fix copy of 32k+ Ascii files (Orgams sources!)
43/ Release the source code (:

Thank you for your great work.

SOS

Quote from: m_dr_m on 03:57, 04 March 19
YARFYANCC (Yet Another Request For Yet Another Norton-Commander Clone)
;D ;D ;D ;D

Quote from: m_dr_m on 03:57, 04 March 19
Not to have to burn LAUNCH.ROM when you don't use the functionality.
...
BTW, why does the ROM have to be in a higher slot?
The YANCC-ROM is full, so i Need an second ROM. In the second ROM are enough free Bytes, so the combination "Needed-YANCC-Functions-to-run" & "Launcher" (which Needs functions from YANCC) makes sense...

YANCC Need to have an lower ROM, because of detection the Floppy-&Massstorage-Device-ROM's.


Quote from: m_dr_m on 03:57, 04 March 19
I'm also copying here the requests from CubeMDOS thread, for clarity.

5/ YANCC should have a 'Move' command
5a/ At least YANCC should retain the selection (like PARADOS copier).
42/ Fix copy of 32k+ Ascii files (Orgams sources!)
43/ Release the source code (:

Move: I'm thinking about it, but it's OS-dependant. (so then only for CubeMDOS)
It could be problematic, due to the full Cube-ROM. => Maybe (or not) later in this year (Summer? Winter?)

YANCC was not started as an open-source project
=> Not planned at the moment, maybe (maybe not) later in this year.


=> Other Points: I will check YANCC later in this year (no time).

SOS

New Version, changelog:
020919b
- CubeMDOS:  Compatibility-changes for the new version
- Message, when File can't be delete from Floppy (write-Protect) (thnx Audronic)
- ASCII-Files > 32 KB will be corrupt (e.g. OrgamS-Sources)  (thnx m_dr_m)
- Display of Directory-Entry reworked ("." was missing)         (thnx netmercer)
- Input of Filenames (MKDIR&REN) will not result the expected filename, when usig DEL  (thnx netmercer)
- Sometimes corrupt files, when copy from MassStorage to floppy (thnx SOS)
- Start of Protected Binary-Files are not possible
- Launcher: 0KB Files not displayed correctly, '<DIR>'-Info is missing on longnames
- Launcher: Speedup of Display-Output

CubeMDOS-Users must update to the new CubeMDOS-Version (coming very soon)

SOS

Quote from: SOS on 22:22, 13 September 19
CubeMDOS-Users must update to the new CubeMDOS-Version (coming very soon)

Out now  :)

TotO

"You make one mistake in your life and the internet will never let you live it down" (Keith Goodyer)

SOS

New Version ("141119"), for the upcoming CubeMDOS (DSK support)

darkhalf


I cannot get the ROMs functioning on the M4 board. Problem is that after running CONFIG.BAS it will not save the updated YANCC-CC.ROM file to the SD card, so I copied the DSK image to my floppy drive and ran from there


However on M4 you cannot ROM update from the disc (only SD card)



Does anyone know if you can make M4 mounted DSK files writeable?



When I did manage to get the ROM files into the M4 (YANCC 140418B in Slot 9, Launch in Slot 10) both programs will just reset the CPC6128 when try try and run it


Similar to:

QuoteYancc rom in slot 1Launcher rom in slot 9when i typed : |YANCC or |LAUNCH , CPC always reset ...




Not sure how XeNoMoRPH got it working in the end?


So I run on the emulator and that run fine if there is a disk image in A.
There is a bug where it will crash if no disk image is inserted (WinApe 2.0B /140418B [size=78%]  ) [/size]
CPC6128, 2xCPC464, C64, A500

Duke

Quote from: darkhalf on 12:10, 08 March 21
I cannot get the ROMs functioning on the M4 board. Problem is that after running CONFIG.BAS it will not save the updated YANCC-CC.ROM file to the SD card, so I copied the DSK image to my floppy drive and ran from there
Just run the files from the native FAT32 filesystem?
Use |DSKX to extract all the files from the .DSK image

SOS

Quote from: darkhalf on 12:10, 08 March 21When I did manage to get the ROM files into the M4 (YANCC 140418B in Slot 9, Launch in Slot 10) both programs will just reset the CPC6128 when try try and run it
Same effect, when the Main YANCC-ROM is below the M4-ROM? (e.g. place YANCC on Slot 4)
You use an old version of YANCC, when you use the latest one, also reset?

darkhalf


Quote
Just run the files from the native FAT32 filesystem?
Use |DSKX to extract all the files from the .DSK image
Excellent, that got |YANCC working properly on the CPC6128, plus I put in YANCC slot 3, Launch slot 10.


QuoteYou use an old version of YANCC, when you use the latest one, also reset?
I had started with 14119b.ROM on the M4 board on my CPC6128 but tried some older versions


On WinAPE |LAUNCH will crash (reset) with no drive A disk inserted, but works fine in emulation only with a disk inserted. Attached is my WinAPE setup



On CPC6128 with M4 |LAUNCHER (141119) will still crash with disk inserted (or not)


Tested with |CD,"TEST.DSK" to open an M4 disc image and
|DISC to an actual floppy on my gotek drive


CPC6128, 2xCPC464, C64, A500

Powered by SMFPacks Menu Editor Mod