TR-DOS with ramdisc for all 1MB ZX clones

Вид для печати

Показывать 40 сообщений этой темы на одной странице

19.01.2013, 19:42
VELESOFT

Цитата:

Сообщение от solegstar

VELESOFT , is possible to integrate a token/command which changes the letter RAM-DISK instead of "D" for "A" into TR-DOS6.11Q? there are programs with "drive A only" problem.

---------- Post added at 17:23 ---------- Previous post was at 17:19 ----------

and back on "D". value of a variable can be stored in GLUK CMOS.

CMOS is usable only on some clones. I use this trdos without real FDD and ramdrive is "A". And work more programs with access only to "A" drive :-)
I can add CMOS support from orig. version 6.11E...
Make new command for change RAMDRIVE number is possible, but I don't know this routines in tr-dos. If anyone can help with this feature.... This command must write one byte with ramdisc drive number to system variables in zx ram(we must find one free/unused byte), but if any software rewrite this byte, trdos can see incorrect ramdisc drive number... :-(

One idea: we can save tr-dos setup also to 1MB ram. For example at begin of 16th ram page = first 256kB ram(ram pages 0-15) is full usable for ZX software with 256kB support. Next page(page 16) at begin contain setup = word "cfg:"+bytes with ramdrive and similar setup. If this "cfg:" text are not detected then tr-dos can use default tr-dos setup (ramdisc on drive "D")
19.01.2013, 20:00
solegstar

Цитата:

Сообщение от VELESOFT

I use this trdos without real FDD and ramdrive is "A". And work more programs with access only to "A" drive :-)

how it is possible if the letter RAM-DISK is set as "D"?
19.01.2013, 21:04
VELESOFT

Цитата:

Сообщение от solegstar

how it is possible if the letter RAM-DISK is set as "D"?

Source code of this tr-dos version contain at begin small config:

Код:

;========== SETUP ========== ;------- select only one memory model ------ DEFINE RAM_ZX_PROFI_1024 ; DEFINE RAM_PENTAGON_1024 ; DEFINE RAM_SCORPION_1024 ; DEFINE RAM_ZXM_PHOENIX ;------- select for autoboot tr-dos ------ ; DEFINE RUN_BOOT_B_ON_DOS_START ; BOOT_ON_CMD_8 ;------- select for enable testing drives ------- ; DEFINE TEST_DRIVES ;------- select for madrom support ------- ; DEFINE COMPILE_FOR_MADROM ;------- select for active patch for fix HL' register ------- DEFINE FIX_HL ;------- select for enable NMI code ------- ; DEFINE NMI_ENABLE ;------- number of ramdisc drive ------- RMD_DRIVE EQU #03 ;ramdisc on drive A(#00),B(#01),C(#02),D(#03) ;------- ramdisc size (free space) -------- RMD_SIZE EQU #09F0 ;ramdisc size(only free sectors = full capacity - 16 sectors) ;( #0DF0=896kB / #0BF0=768kB / #09F0=640kB / #07F0=512kB / #05F0=384kB / #03F0=256kB / #01F0=128kB )

You can change ramdisc drive on this lines to value #00:
;------- number of ramdisc drive -------
RMD_DRIVE EQU #03 ;ramdisc on drive A(#00),B(#01),C(#02),D(#03)

I can send you trdos compiled with ramdisc drive on "A" :-)
I use WDC in service rom(start after reset/power on ZX) and this tr-dos with ramdisc on "A". WDC after start show FAT32 + drive "A". Problems is with some booters (ofter use custom loaders and work only with real FDD).

---------- Post added at 15:04 ---------- Previous post was at 14:17 ----------

Here is screenshot of same trdos 6.11q compiled with ramdisc on drive "A":
http://velesoft.speccy.cz/other/TR-D...1024_RMD_A.png

And here you can download all 4 ROM images with trdos 6.11q with ramdisc on drive A:
http://velesoft.speccy.cz/other/TRDO...ETAVERSION.zip
19.01.2013, 21:44
VELESOFT

Цитата:

Сообщение от Keeper

VELESOFT, you can use command "4" or "8" for changing ram-disk drive letter, in addition to CMOS support.

Yes, but I need know way :-(
20.01.2013, 00:36
VELESOFT

Цитата:

Сообщение от Keeper

Feel free to use "*" command as working example ;) Also you should notice that NVRAM implementation on ZXM-Phoenix is soooo sloooow:

Take a look into FORMAT command for example how to notify user about performed actions, e.g. "Saving to GLUK CMOS". For example, we are choosing "4" command for setting ram-disk drive letter, something like: 4"B:"<enter>
What we need to do when enter key pressed:
1. PRINT "Saving to GLUK CMOS"
2. Disable interrupts
3. Save to GLUK CMOS
4. Enable interrupts
5. Return with OK.

I can use this syntax:
*"rmd a" - *"rmd d" for change ramdisc drive. OK ?
Save to CMOS is good feature, but must exist autodetection ? This device is unknown for me.

If I will save info about ramdics drive to extra ram page then will usable on all computers with 1MB memory and without cmos chip. After poweron will set default ramdisc drive "D" and in any time can user mount ramdisc to any other drive. After reset are 1MB memory not erased, yes ? Then trdos after restart/reset can detect if exist ramdisc setup in higher memory and change always ramdisc drive from "D" to custom value from setup. Problem can be on computers where reset button disable refresh for dram chips and can destroy ram data.
21.01.2013, 03:18
VELESOFT

Цитата:

Сообщение от VELESOFT

I can use this syntax:
*"rmd a" - *"rmd d" for change ramdisc drive. OK ?
Save to CMOS is good feature, but must exist autodetection ? This device is unknown for me.

If I will save info about ramdics drive to extra ram page then will usable on all computers with 1MB memory and without cmos chip. After poweron will set default ramdisc drive "D" and in any time can user mount ramdisc to any other drive. After reset are 1MB memory not erased, yes ? Then trdos after restart/reset can detect if exist ramdisc setup in higher memory and change always ramdisc drive from "D" to custom value from setup. Problem can be on computers where reset button disable refresh for dram chips and can destroy ram data.

Ramdisc drive switching work perfect, but I support this feature only on my PROFI interface ( *"RMD A" - *"RMD D" ). Save setup in extra memory is hard because this code need often test 128kB ram pages. Save to CMOS can be implement only if anyone send me code for it (write one byte to CMOS memory and read this byte from CMOS memory). I will also add possibility disable ramdisc via *"RMD OFF"...
21.01.2013, 03:43
alvis

Цитата:

Сообщение от VELESOFT

I can use this syntax:
*"rmd a" - *"rmd d" for change ramdisc drive. OK ?
Save to CMOS is good feature, but must exist autodetection ? This device is unknown for me.

Может глупость скажу, но почему бы не использовать стандартный синтаксис комманды Subst ?
21.01.2013, 04:20
VELESOFT

Цитата:

Сообщение от alvis

Может глупость скажу, но почему бы не использовать стандартный синтаксис комманды Subst ?

*"A" - *"D" = select drive

Ramdisc emulate one of four drives and you can set number of drive which is emulated with ramdisc.

For example:

*"RMD A" = ramdisc(fdd emulation in 1MB ram) are instead drive A and drives B,C,D are used as FDD.

*"RMD D" = ramdisc(fdd emulation in 1MB ram) are instead drive D and drives A,B,C are used as FDD.

*"RMD OFF" = disable ramdisc, all 4 drives are used as FDD
21.01.2013, 14:46
solegstar

Цитата:

Сообщение от Keeper

It is possible to store ram-disk drive letter and/or other configuration params in RAM if you will prohibit writes to sectors 9-F of the track 0.

да, но ведь при сохранении рамдиска в образ TRD, этот параметр таки запишется... есть еще, кстати, командеры, которые вписывают себя в это место...
21.01.2013, 19:30
VELESOFT

Цитата:

Сообщение от Keeper

я думаю что там компромисс можно найти...

I need know one unused byte in zx ram (system variables/tr-dos variables) for save info about current ram page = during testing drive number tr-dos rewrite this byte. If you know this adress, then setup in extra ram is no problem.
In TR-DOS source configuration I can add three ways for save setup:
- save to CMOS
- save to 1MB memory (zx ram)
- save to PROFI INTERFACE port
- autodetection....
Setup in 1MB ram can be at end of ram page 16. First 256kB(ram pages 0-15) can be used for software/games, next ram page 16 used for save setup, pages 63-17 reserved for ramdisc.

---------- Post added at 13:30 ---------- Previous post was at 13:27 ----------

What CMOS memory adress are free and what space is used/reserved on ZX clones ? Exist any info ?

Показывать 40 сообщений этой темы на одной странице