mirror of
https://github.com/wwarthen/RomWBW.git
synced 2026-02-07 06:53:13 -06:00
Compare commits
5 Commits
v3.4.0-dev
...
v3.4.0-dev
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
29f93fb153 | ||
|
|
b0975745df | ||
|
|
163460856a | ||
|
|
3ce9246904 | ||
|
|
1a021e02b9 |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -3,7 +3,7 @@
|
||||
**RomWBW ReadMe** \
|
||||
Version 3.4 \
|
||||
Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
|
||||
13 Oct 2023
|
||||
19 Oct 2023
|
||||
|
||||
# Overview
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
RomWBW ReadMe
|
||||
Wayne Warthen (wwarthen@gmail.com)
|
||||
13 Oct 2023
|
||||
19 Oct 2023
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -2660,6 +2660,166 @@ SAMPLE2.TXT ==> 4:/SAMPLE2.TXT ... [OK]
|
||||
2 File(s) Copied
|
||||
```
|
||||
|
||||
# Real Time Clock
|
||||
|
||||
RomWBW supports a variety of real time clock hardware. If your
|
||||
system has this hardware, then it will be able to maintain the
|
||||
current date and time even while your system is turned off.
|
||||
Additionally, depending on the operating system being used, you may be
|
||||
able to utilize date/time stamping of files.
|
||||
|
||||
You can determine if your system has a real time clock present (and
|
||||
functioning) by looking at the boot messages. Here is an example of
|
||||
a boot message reflecting the detection of a valid real time clock
|
||||
module:
|
||||
|
||||
`DSRTC: MODE=STD IO=0x8A Thu 2023-10-19 14:07:11 CHARGE=ON`
|
||||
|
||||
This example is from a DSRTC clock module. You may have a different
|
||||
one, but it will always display the current date/time.
|
||||
|
||||
In some cases, your real time clock will support charging of the
|
||||
battery or super-capacitor while the system has power. The status of
|
||||
this charging is displayed.
|
||||
|
||||
If the date/time of your RTC needs to be updated, you will need to do
|
||||
this with one of the utilities described below. There is no ability to
|
||||
update the date/time of the RTC in the RomWBW Boot Loader or Monitor.
|
||||
|
||||
## Date/Time Utilities
|
||||
|
||||
RomwWBW includes two utilities for displaying or setting the date/time
|
||||
stored by the RTC. They are both a bit different and are briefly
|
||||
described below.
|
||||
|
||||
### WDATE Utility
|
||||
|
||||
The `WDATE` utility (contributed by Kevin Boone) is an application
|
||||
that will display and/or update the current date/time. Its operation is
|
||||
described in $doc_apps$. This utility works with any of the supported
|
||||
RomWBW RTC hardware. Here is an example of displaying and updating the
|
||||
date/time with this utility:
|
||||
|
||||
```
|
||||
A>wdate
|
||||
Thursday 19 October 14:14:43 2023
|
||||
|
||||
A>wdate 23 10 19 14 24 30
|
||||
|
||||
A>wdate
|
||||
Thursday 19 October 14:24:34 2023
|
||||
|
||||
```
|
||||
|
||||
Note that `WDATE` does not have anything to do with date/time stamping
|
||||
of files. It merely displays and sets the real time clock value.
|
||||
|
||||
### RTC Utility
|
||||
|
||||
Like `WDATE`, the `RTC` utility (contributed by Andrew Lynch) will let
|
||||
you display and set the current date/time. However, this utility only
|
||||
works with the DSRTC hardware (DS1302 chip). It is a "direct to
|
||||
hardware application". Its operation is described in $doc_apps$. Here
|
||||
is an example of displaying and updatting the date/time with this
|
||||
utility:
|
||||
|
||||
```
|
||||
A>rtc
|
||||
Start RTC Program
|
||||
RomWBW HBIOS, Mark 4 RTC Latch Port 0x8A
|
||||
|
||||
RTC: Version 1.9
|
||||
Commands: E)xit T)ime st(A)rt S)et R)aw L)oop C)harge N)ocharge D)elay I)nit G)et P)ut B)oot W)arm-start H)elp
|
||||
|
||||
RTC>t
|
||||
Current time: 23-10-19 14:30:25-05
|
||||
|
||||
RTC>i
|
||||
Init date/time.
|
||||
|
||||
YEAR:23
|
||||
MONTH:10
|
||||
DATE:19
|
||||
HOURS:14
|
||||
MINUTES:31
|
||||
SECONDS:00
|
||||
DAY:05
|
||||
```
|
||||
|
||||
The `RTC` utility is also capable of turning the charging feature of
|
||||
the DS1320 chip on or off. Here is an example of turning if off and
|
||||
back on:
|
||||
|
||||
```
|
||||
|
||||
A>rtc
|
||||
Start RTC Program
|
||||
RomWBW HBIOS, Mark 4 RTC Latch Port 0x8A
|
||||
|
||||
|
||||
RTC: Version 1.9
|
||||
Commands: E)xit T)ime st(A)rt S)et R)aw L)oop C)harge N)ocharge D)elay I)nit G)et P)ut B)oot W)arm-start H)elp
|
||||
|
||||
RTC>n
|
||||
Trickle charger disabled.
|
||||
|
||||
RTC>c
|
||||
Trickle charger enabled.
|
||||
```
|
||||
|
||||
Do **not** enable charging unless you are sure that your system
|
||||
supports this. If your RTC is being powered by a normal battery, it
|
||||
would be dangerous to enable charging.
|
||||
|
||||
## Date/Time File Stamping
|
||||
|
||||
If an RTC is available in your system, then most operating systems
|
||||
can use it to date/time stamp files. This just means recording the
|
||||
date/time of file creation, update, and or access in the directory.
|
||||
This capability is available in all of the RomWBW operating system
|
||||
except the original DRI CP/M 2.2.
|
||||
|
||||
In some cases (such as ZSDOS), you must load an RSX (memory resident
|
||||
utility) to enable date/time stamping of files. Additionally, you
|
||||
will need to initialize the directory. The procedure varies in each
|
||||
operation system, so you must review the associated documentation.
|
||||
|
||||
The date/time stamping mechanisms for each operating system are
|
||||
generally not compatible. If you initialize a directory for a type
|
||||
of stamping, you should be careful not to manipulate that directory
|
||||
with a different operating system with a different date/time stamping
|
||||
mechanism. Doing so may corrupt the directory.
|
||||
|
||||
The RomWBW disk images do not have date/time stamping initialized. This
|
||||
is to avoid any chance of directory corruption.
|
||||
|
||||
## Timezone
|
||||
|
||||
None of the operating systems distributed with RomWBW have any concept
|
||||
of timezone. When files are date/time stamped, the date/time will
|
||||
simply be whatever date/time the RTC currently has.
|
||||
|
||||
The normal practice is to set the RTC to your local time. This implies
|
||||
that you would need to manually adjust the RTC for daylight savings time
|
||||
and/or when you travel to a different time zone.
|
||||
|
||||
The date/time stamps of files in directories will also be stored in
|
||||
local time. This includes files stored in a FAT filesystem. If you
|
||||
subsequently view the directory from modern machines (Windows, Linux,
|
||||
etc.), the date/time displayed will depend on the behavior of the
|
||||
modern system.
|
||||
|
||||
For example, Linux assumes that the date/time of files
|
||||
is UTC. So, if you create a file on a FAT filesystem with your RomWBW
|
||||
computer and then use Linux to view the directory, the date/time stamps
|
||||
will seem "off" by a few hours.
|
||||
|
||||
The only alternative you may consider is setting the date/time of your
|
||||
RTC to UTC. Since UTC is consistent across all timezones and daylight
|
||||
savings time, your file date/time stamps will also be consistent. Of
|
||||
course, this will mean that your RomWBW computer will display a
|
||||
date/time that seems wrong because it is not local time.
|
||||
|
||||
# CP/NET Networking
|
||||
|
||||
Digital Research created a simple network file sharing system called
|
||||
|
||||
@@ -229,12 +229,12 @@ SDCNT .EQU 1 ; SD: NUMBER OF SD CARD DEVICES (1-2), FOR DSD/SC/MT ONLY
|
||||
SDTRACE .EQU 1 ; SD: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
SDCSIOFAST .EQU FALSE ; SD: ENABLE TABLE-DRIVEN BIT INVERTER IN CSIO MODE
|
||||
;
|
||||
CHENABLE .EQU FALSE ; CH: ENABLE CH375/376 USB SUPPORT
|
||||
CHENABLE .EQU TRUE ; CH: ENABLE CH375/376 USB SUPPORT
|
||||
CHTRACE .EQU 1 ; CH: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
CHUSBTRACE .EQU 1 ; CHUSB: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
CHSDTRACE .EQU 1 ; CHSD: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
CHCNT .EQU 1 ; CH: NUMBER OF BOARDS TO DETECT (1-2)
|
||||
CH0BASE .EQU $BE ; CH 0: BASE I/O ADDRESS
|
||||
CH0BASE .EQU $4E ; CH 0: BASE I/O ADDRESS
|
||||
CH0USBENABLE .EQU TRUE ; CH 0: ENABLE USB DISK
|
||||
CH0SDENABLE .EQU FALSE ; CH 0: ENABLE SD DISK
|
||||
CH1BASE .EQU $FF ; CH 1: BASE I/O ADDRESS
|
||||
@@ -254,16 +254,16 @@ ESPCONENABLE .EQU TRUE ; ESP: ENABLE ESP32 CONSOLE IO DRIVER VIDEO/KBD SUPPORT
|
||||
HDSKENABLE .EQU FALSE ; HDSK: ENABLE SIMH HDSK DISK DRIVER (HDSK.ASM)
|
||||
HDSKTRACE .EQU 1 ; HDSK: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
;
|
||||
PIOENABLE .EQU FALSE ; PIO: ENABLE ZILOG PIO DRIVER (PIO.ASM)
|
||||
PIOENABLE .EQU TRUE ; PIO: ENABLE ZILOG PIO DRIVER (PIO.ASM)
|
||||
PIOCNT .EQU 2 ; PIO: NUMBER OF CHIPS TO DETECT (1-2), 2 CHANNELS PER CHIP
|
||||
PIO0BASE .EQU $B8 ; PIO 0: REGISTERS BASE ADR
|
||||
PIO1BASE .EQU $BC ; PIO 1: REGISTERS BASE ADR
|
||||
PIO0BASE .EQU $68 ; PIO 0: REGISTERS BASE ADR
|
||||
PIO1BASE .EQU $6C ; PIO 1: REGISTERS BASE ADR
|
||||
;
|
||||
LPTENABLE .EQU FALSE ; LPT: ENABLE CENTRONICS PRINTER DRIVER (LPT.ASM)
|
||||
LPTENABLE .EQU TRUE ; LPT: ENABLE CENTRONICS PRINTER DRIVER (LPT.ASM)
|
||||
LPTMODE .EQU LPTMODE_SPP ; LPT: DRIVER MODE: LPTMODE_[NONE|SPP|MG014]
|
||||
LPTCNT .EQU 1 ; LPT: NUMBER OF CHIPS TO DETECT (1-2)
|
||||
LPTTRACE .EQU 1 ; LPT: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
|
||||
LPT0BASE .EQU $E8 ; LPT 0: REGISTERS BASE ADR
|
||||
LPT0BASE .EQU $48 ; LPT 0: REGISTERS BASE ADR
|
||||
LPT1BASE .EQU $EC ; LPT 1: REGISTERS BASE ADR
|
||||
;
|
||||
PPAENABLE .EQU FALSE ; PPA: ENABLE PPA DISK DRIVER (PPA.ASM)
|
||||
|
||||
Binary file not shown.
@@ -17,6 +17,11 @@ FLASH4 has been tested and confirmed working on:
|
||||
It should work on many other machines that run RomWBW or UNA BIOS. If you test
|
||||
it on another machine please let me know the outcome.
|
||||
|
||||
FLASH030 (also included) is a Linux version of the same software. It is
|
||||
targetted at my 68030 machine but should be very easy to port to other
|
||||
machines. It expects a machine with a larger address space, and thus omits much
|
||||
of the bank switching and other tricks required on Z80 platforms.
|
||||
|
||||
|
||||
= Introduction =
|
||||
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -2,7 +2,7 @@
|
||||
#DEFINE RMN 4
|
||||
#DEFINE RUP 0
|
||||
#DEFINE RTP 0
|
||||
#DEFINE BIOSVER "3.4.0-dev.10"
|
||||
#DEFINE BIOSVER "3.4.0-dev.12"
|
||||
#define rmj RMJ
|
||||
#define rmn RMN
|
||||
#define rup RUP
|
||||
|
||||
@@ -3,5 +3,5 @@ rmn equ 4
|
||||
rup equ 0
|
||||
rtp equ 0
|
||||
biosver macro
|
||||
db "3.4.0-dev.10"
|
||||
db "3.4.0-dev.12"
|
||||
endm
|
||||
|
||||
Reference in New Issue
Block a user