-
Notifications
You must be signed in to change notification settings - Fork 101
/
ReadMe.txt
3838 lines (3135 loc) · 138 KB
/
ReadMe.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
***********************************************************************
*** ***
*** R o m W B W ***
*** ***
*** Z80/Z180 System Software ***
*** ***
***********************************************************************
This directory is the root directory of the source tree for RomWBW.
This document describes the process to build a customized version
of the RomWBW firmware. RomWBW was explicitly organized in a way
that makes it very easy to rebuild the firmware.
Significant customization can be achieved with a custom built
firmware using simple option configuration files. You can
customize your firmware to:
- Include support for add-on support boards such as
the DiskIO, Dual-IDE, etc.
- Modify operational parameters such as serial port
speed or wait state insertion.
- Add or remove programs or files contained on the disk images.
Virtually all source code is provided including the operating
systems themselves, so advanced users can easily modify any of
the software.
A cross-platform approach is used to build the RomWBW firmware.
The software is built using a modern Windows, Linux, or Mac
computer, then the resulting firmware image is programmed into
the ROM of your RetroBrew Computer CPU board.
Windows Build System Requirements
---------------------------------
For Microsoft Windows computers, all that is required to build the
firmware is the RomWBW distribution zip archive file. The zip
archive package includes all of the required source code
(including the operating systems) and the programs required to run
the build.
The build process is run via some simple scripts that automate the
process. These scripts utilize both batch command files as well as
Windows PowerShell. Windows 7 or greater is recommended. If you want
to use Windows Vista or XP, you will need to first install PowerShell
which available for free from Microsoft. Either 32 or 64 bit versions
of Microsoft Windows are fine. No additional programs need to be
installed to run the build.
You may find that you get messages such as this during the Windows
build process:
Security warning
Run only scripts that you trust. While scripts from the internet can be
useful, this script can potentially harm your computer. If you trust
this script, use the Unblock-File cmdlet to allow the script to run
without this warning message. Do you want to run
C:\Temp\RomWBW-v3.5.0-dev.67-Package\Source\Images\BuildDisk.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"):
These prompts occur if Windows has marked the files as "blocked"
because they were downloaded from the Internet. To unblock all of
the files in the entire RomWBW distribution tree, start PowerShell
and navigate to the root of the distribution. Enter the following
command:
dir -recurse | unblock-file
This will unblock all files within the distribution and preclude the
security warning messages. Obviously, you should make sure you have
downloaded the RomWBW distribution from a valid/trustworthy source
before removing the file block protection.
Linux Build System Requirements
-------------------------------
You must have some standard system tools and libraries
installed, specifically: gcc, gnu make, libncurses, and srecord.
Typically, something like this will take care of adding all
required packages in Linux:
sudo apt install build-essential libncurses-dev srecord
Since there are many variants and releases of Linux, it is difficult
to ensure the build will work in all cases. The current stable
release of Ubuntu is used to verify the build runs.
MacOS Build System Requirements
-------------------------------
You will need to install the srecord package to complete the
build process:
brew install srecord
You may encounter a failure reading or writing files. This is caused by
protection features in MacOS (at least, in Catalina) that prevent
programs built on your local system (unsigned) from running. To
disable this feature:
1) Make sure you exit System Preferences.
2) Open a terminal session and type the following. You will need to
authenticate with an admin account: sudo spctl --master-disable
3) Exit terminal
4) Go into System Preferences and choose Security and Privacy
5) Select the General tab if it isn't already selected
6) You should now see a third selection under
"Allow apps downloaded from:" of Anywhere - select this.
7) Now you can run the build successfully.
DISCLAIMER: You do this at your own risk. I highly recommend that you
return the settings back to normal immediately after doing a build.
Process Overview
----------------
The basic steps to create a custom ROM are:
1) Create/update configuration file (optional).
2) Update/Add/Delete any files as desired to customize the disk
images (optional).
3) Run the build scripts and confirm there are no errors.
4) Program the resultant ROM image and/or write thedisk images.
Note that steps 1 and 2 are performed to customize your ROM as
desired. If you want to simply build a standard configuration, it is
*not* necessary to perform steps 1 or 2 before running a build. In
fact, I strongly recommend that you skip steps 1 and 2 initially and
just perform perform steps 3 and 4 using the standard configuration to
make sure that you have no issues building and programming a ROM that
works the same as a pre-built ROM.
Each of the 4 steps above is described in more detail below.
1. Create/Update Configuration File
-----------------------------------
The options for a build are primarily controlled by a configuration
file that is included in the build process.
RomWBW uses cascading configuration files as indicated below:
cfg_MASTER.asm - MASTER: CONFIGURATION FILE DEFINES ALL POSSIBLE ROMWBW SETTINGS
|
+-> cfg_<platform>.asm - PLATFORM: DEFAULT SETTINGS FOR SPECIFIC PLATFORM
|
+-> Config/<plt>_std.asm - BUILD: SETTINGS FOR EACH OFFICIAL DIST BUILD
|
+-> Config/<plt>_<cust>.asm - USER: CUSTOM USER BUILD SETTINGS
The top (master configuration) file defines all possible RomWBW
configuration settings. Each file below the master configuration file
inherits the cumulative settings of the files above it and may
override these settings as desired.
Other than the top master file, each file must "#INCLUDE" its parent
file. The top two files should not be modified. To customize your
build settings you should modify the default build settings
(config/<platform>_std.asm) or preferably create an optional custom
user settings file that includes the default build settings file (see
example Config/SBC_user.asm).
By creating a custom user settings file, you are less likely to be
impacted by future changes because you will only be inheriting most
of your settings which will be updated by authors as RomWBW evolves.
RomWBW uses the concept of a "platform" and "configuration" to
define the settings for a build. Platform refers to one of the core
systems supported. Configuration refers to the settings that
customize the build. The configuration is modifies the platform
defaults as desired.
The platform names are predefined. Refer to the following table
to determine the <plt> component of the configuration filename:
SBC Z80 SBC (v1 or v2) w/ ECB interface
ZETA Standalone Z80 SBC w/ SBC compatibility
ZETA2 Second version of ZETA with enhanced memory bank switching
N8 MSX-ish Z180 SBC w/ onboard video and sound
MK4 Mark IV Z180 based SBC w/ ECB interface
UNA Any Z80/Z180 computer with UNA BIOS
RCZ80 RCBUS based system with 512K banked RAM/ROM card
RCZ180 RCBUS based system with Z180 CPU
EZZ80 Easy Z80, Z80 SBC w/ RCBUS and CTC
SCZ180 Steve Cousins Z180 based system
DYNO Steve Garcia's Dyno Micro-ATX Motherboard
RCZ280 Z280 CPU on RCBUS or ZZ80MB
MBC Andrew Lynch's Multi Board Computer
RPH Andrew Lynch's RHYOPHYRE Graphics Computer
Z80RETRO Peter Wilson's Z80-Retro Computer
S100 S100 Computers Z180-based System
DUO Andrew Lynch's Duodyne Computer
HEATH Les Bird's Heath Z80 Board
EPITX Alan Cox' Mini-ITX System
MON Jacques Pelletier's Monsputer
GMZ180 Doug Jacksons' Genesis Z180 System
NABU NABU w/ Les Bird's RomWBW Option Board
FZ80 S100 Computers FPGA Z80
Configuration files are found in the Source\HBIOS\Config
directory. If you look in the this directory, you will see a
series of files named <plt>_<cfg>.asm. By convention, all
configuration files start with the platform identifier followed
by an underscore. You will see later that the build process does
require this naming convention and it allows you to easily see which
configuration files apply to each of the platforms supported.
Each of the possible platforms has at least one configuration file. In
many cases, there will be a standard ("std") configuration for the
platform. For example, there is a file called MK4_std.asm. This is
the standard ("std") configuration for a Mark IV CPU board.
The <cfg> portion of the filename can be anything desired. To create
your own custom configuration, you can modify an existing configuration
file or (preferably), you could copy an existing configuration file
to a new name of your choosing and make your changes there. For
example, you could copy "MK4_std.asm" to something like "MK4_cust.asm".
Now, you can make changes to your private copy of the configuration
and easily revert back to the original if you have problems.
It is important to understand how configuration files are processed.
They start by inheriting all of the default settings for the
platform. This is accomplished via the "#INCLUDE" directive near
the top of the file. For the "MK4_std.asm" configuration file,
this line reads:
#INCLUDE "cfg_MK4.asm"
When the configuration file (MK4_std.asm) is processed, it will first
read in all the default platform settings from "cfg_MK4.asm". All of
the platform default configuration files are found in the parent
directory (the HBIOS directory). You will see a "cfg_<plt>.asm" for
each platform in the parent directory.
If you look at the platform configuration file, you will see that it
has many more settings than you found in the build configuration file.
The platform configuration file contains *all* possible settings for
the platform and defines their default value. The settings in the
build configuration file just override the platform default settings.
Note that the settings in the platform configuration file are all
defined using ".EQU" whereas the build configuration file uses ".SET".
This is because ".EQU" defines the initial value for a variable and
".SET" modifies a pre-existing value. You *must* use ".EQU" and ".SET"
correctly or the assembler will complain very loudly.
In our example, let's say you have added a DiskIO V3 board to your
Mark IV system and want to include floppy support. You will see a
couple lines similar to these in the config file:
FDENABLE .SET TRUE ; FD: ENABLE FLOPPY DISK DRIVER (FD.ASM)
FDMODE .SET FDMODE_DIDE ; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3|RCSMC|RCWDC|DYNO|EPWDC]
FDENABLE is already set to TRUE, so that is fine. However, FDMODE
is not correct because it specifies a different board. To fix this,
just modify the line to read:
FDMODE .SET FDMODE_DIO3 ; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3|RCSMC|RCWDC|DYNO|EPWDC]
You are now probably wondering where to find detailed instructions for
each of the configuration settings. Sadly, this is an area where
RomWBW is very deficient. The changes to hardware support happen so
fast that is have been virtually impossible to create such a document.
If it is not obvious what you need to do when looking at the build
configuration file, I recommend that you look at the platform
configuration file in the parent directory. It will contain all of the
possible settings and their default values as well as a brief comment.
In many cases this is enough information to figure out what to do. If
not, you will need to either look at the HBIOS source code or request
help in any of the RomWBW support communities (people are typically
very helpful). You can also post questions or issues on the GitHub
repository.
2. Update/Add/Delete Disk Files
-------------------------------
A major part of the RomWBW build process is the creation of the
ROM disk contents and the floppy/hard disk image files.
The files that are included on the ROM Disk of your ROM are copied
from a set of directories during the build process. This allows
you to have complete flexibility over the files you want included
in your ROM.
The ROM disk process starts in the Source/RomDsk directory. Within
that directory, there are subdirectories for each of the different
possible ROM sizes that can be created. The vast majority of all
ROMs are 512KB, so you will probably be interested primarily in the
ROM_512KB subdirectory.
These subdirectories are already populated in the distribution. You do
not need to do anything unless you want to change the files that are
included on your ROM Disk.
In summary, the ROM Disk embedded in the ROM firmware you build,
will include the files from the ROM_512KB directory (or the
ROM_1024KB directory if building a 1024KB firmware, etc.).
There is a ReadMe.txt document in the \Source\RomDsk directory
with a more detailed description of this process.
Note that the standard 512K ROM disk is almost full. So, if
you want to add files to it, you will need to delete other files
to free up some space.
Creation of the floppy/hard disk images is similar, but these
images are much larger and have many more files. Additionally, the
process pulls in files from multiple places and creates multiple
formats. The Source/Images directory of the distribution handles
the creations of these disk images. There is a ReadMe.txt file there
that describes the process and how to customize your disk images.
3. Run the Build Process
------------------------
Regardless of whether you are using Windows, Linux, or MacOS to perform
the build, you will initiate the build at a command prompt. So, you
start by starting a command window/terminal. Make sure your
command prompt has the root "RomWBW" directory as the default.
For a Windows computer, the build is initiated by simply running the
command "Build". To delete all files created during a build process,
use the "Clean" command. I recommend doing this before each build. It
will operate recursively on all directories.
For Linux or MacOS, you will use the command "make". To delete all
files created during a prior build run, use the command "make clean".
I strongly recommend doing this before each build.
This will launch the build process for a complete RomWBW build including
ROM and disk images. Some of the output may be confusing, so a sample
normal build run is included at the end of this document.
At a point in the middle of the build, you will be prompted to choose
the specific platform and configuration for your ROM. For platform, be
sure to enter the platform identifier that corresponds to the ROM you
are creating. The prompt will look something like this:
Platform [SBC|MBC|ZETA|ZETA2|RCZ80|EZZ80|UNA|N8|MK4|RCZ180|SCZ180|DYNO|RCZ280]:
You will subsequently be prompted for the specific configuration that
you want to build. It will display the available possibilities based
on the platform you previously chose. Notice that you are choosing
the portion of the configuration filename that follows the platform
id:
Configurations available:
> std
> cust
Configuration:
Enter one of the configuration options to build a ROM with the
associated config file.
At this point, the build should continue and you will see output
related to the assembler runs and some utility invocations. Just
review the output for any obvious errors. Normally, all errors
will cause the build to stop immediately and display an error
message in red.
You will see some lines in the output indicating the amount of
space various components have taken. You should check these to
make sure you do not see any negative numbers which would indicate
that you have included too many features/drivers for the available
memory space. Here are examples of the lines showing the space
used:
HBIOS PROXY STACK space: 38 bytes.
HBIOS INT space remaining: 82 bytes.
DSRTC occupies 423 bytes.
UART occupies 716 bytes.
ASCI occupies 580 bytes.
MD occupies 451 bytes.
IDE occupies 1276 bytes.
SD occupies 2191 bytes.
HBIOS space remaining: 21434 bytes.
At the completion of the build process, you will find the resultant
ROM and disk image files in the Binary directory.
There will be many disk image (".img") files created. These are
described in the RomWBW User Guide document. Since RomWBW
encapsulates all hardware interface code in the ROM itself, the
disk image files are generic for all ROMs. The only reason they
are built is to accommodate any disk content changes you may have
made.
4. Deploy the ROM
-----------------
Upon completion of a successful build, you should find the
resulting firmware in the Binary directory. The ROM file
will be called <plt>_<cfg>.rom matching the platform identifier
and configuration you chose.
Three output files will be created for a single build:
<plt>_<cfg>.rom - binary ROM image to burn to EEPROM
<plt>_<cfg>.com - executable version of the system image
that can be copied via X-Modem to a
running system to test the build
<plt>_<cfg>.upd - partial ROM image containing just the
first 128KB which can be used to update
only the "code" portion of your ROM
and not modify the ROM disk
The actual ROM image is the file ending in .rom. It will normally be
512KB. Simply burn the .rom image to your ROM and install
it in your hardware. The process for programming your ROM depends
on your hardware, but the .rom file is in a pure binary format (it
is not hex encoded).
You can alternatively reprogram your ROM in-situ (most hardware
supports this) using the FLASH application included with RomWBW. This
is described in the "Upgrading" section of the RomWBW User Guide.
Refer to the document ReadMe.txt in the Binary directory for more
information on the other two file extensions created.
Specifying Build Options on Command Line
----------------------------------------
If you are repeatedly running the build process, you may prefer to
specify the platform and configuration on the command line to avoid
being prompted each time.
Under Windows, you can specify the platform and configuration
like this:
Build MK4 cust
Under Linux or MacOS, you can do the same thing like this:
make ROM_PLATFORM=MK4 ROM_CONFIG=cust
In this case, you will not be prompted. This is useful if you wish
to automate your build process.
In the past, the size of the ROM could be specified as the third
parameter of the command. This parameter is now deprecated and
the size of the ROM is specified in your configuration file
using the ROMSIZE variable.
Example Build Run (Windows)
---------------------------
C:\Users\Wayne\Projects\RomWBW>build
Building PropIO...
Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved
Compiled for i386 Win32 at 08:17:48 on 2009/07/20
Loading Object PropIO
Loading Object AnsiTerm
Loading Object vgacolour
Loading Object E555_SPKEngine
Loading Object Keyboard
Loading Object safe_spi
Loading Object Parallax Serial Terminal Null
Program size is 13416 longs
Compiled 2227 Lines of Code in 0.054 Seconds
1 file(s) moved.
Building PropIO2...
Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved
Compiled for i386 Win32 at 08:17:48 on 2009/07/20
Loading Object PropIO2
Loading Object AnsiTerm
Loading Object vgacolour
Loading Object E555_SPKEngine
Loading Object Keyboard
Loading Object safe_spi
Loading Object Parallax Serial Terminal Null
Program size is 13420 longs
Compiled 2227 Lines of Code in 0.053 Seconds
1 file(s) moved.
Building ParPortProp...
Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved
Compiled for i386 Win32 at 08:17:48 on 2009/07/20
Loading Object ParPortProp
Loading Object AnsiTerm
Loading Object vgacolour
Loading Object E555_SPKEngine
Loading Object Keyboard
Loading Object safe_spi
Loading Object Parallax Serial Terminal Null
Loading Object FullDuplexSerial
Program size is 15484 longs
Compiled 2631 Lines of Code in 0.065 Seconds
1 file(s) moved.
TASM Z180 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
TASM Z180 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
1 file(s) copied.
1 file(s) copied.
Building CBIOS for RomWBW...
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
CBIOS extension info occupies 6 bytes.
UTIL occupies 525 bytes.
INIT code slack space: 2184 bytes.
HEAP space: 4034 bytes.
CBIOS total space used: 6144 bytes.
tasm: pass 2 complete.
tasm: Number of errors = 0
Building CBIOS for UNA...
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
CBIOS extension info occupies 6 bytes.
UTIL occupies 525 bytes.
INIT code slack space: 2025 bytes.
HEAP space: 3887 bytes.
CBIOS total space used: 6400 bytes.
tasm: pass 2 complete.
tasm: Number of errors = 0
Building ccpb03...
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
Building bdosb01...
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
CP/M MACRO ASSEM 2.0
D7F2
00BH USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 1887 bytes (075FH) to file P0:CCP.BIN
Start address: D000H Ending address: D7BAH Bias: 0000H
Saved image size: 2048 bytes (0800H, - 16 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
E5EE
017H USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 3453 bytes (0D7DH) to file P0:BDOS.BIN
Start address: D800H Ending address: E5B2H Bias: 0000H
Saved image size: 3584 bytes (0E00H, - 28 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
D7F2
008H USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 1906 bytes (0772H) to file P0:CCP22.BIN
Start address: D000H Ending address: D7CCH Bias: 0000H
Saved image size: 2048 bytes (0800H, - 16 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
E633
012H USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 3518 bytes (0DBEH) to file P0:BDOS22.BIN
Start address: D800H Ending address: E5EDH Bias: 0000H
Saved image size: 3584 bytes (0E00H, - 28 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
D7F2
00BH USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 1887 bytes (075FH) to file P0:OS2CCP.BIN
Start address: D000H Ending address: D7BAH Bias: 0000H
Saved image size: 2048 bytes (0800H, - 16 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
E5EE
017H USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 3453 bytes (0D7DH) to file P0:OS3BDOS.BIN
Start address: D800H Ending address: E5B2H Bias: 0000H
Saved image size: 3584 bytes (0E00H, - 28 records)
++ Warning: program origin NOT at 100H ++
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
os2ccp.bin
os3bdos.bin
..\cbios\cbios_wbw.bin
1 file(s) copied.
os2ccp.bin
os3bdos.bin
..\cbios\cbios_una.bin
1 file(s) copied.
loader.bin
cpm_wbw.bin
1 file(s) copied.
loader.bin
cpm_una.bin
1 file(s) copied.
CP/M MACRO ASSEM 2.0
D7EF
00EH USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 1888 bytes (0760H) to file P0:ZCPR.BIN
Start address: D000H Ending address: D7EEH Bias: 0000H
Saved image size: 2048 bytes (0800H, - 16 records)
++ Warning: program origin NOT at 100H ++
CP/M MACRO ASSEM 2.0
01B3
000H USE FACTOR
END OF ASSEMBLY
MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988
by NightOwl Software, Inc.
Loaded 179 bytes (00B3H) to file P0:BDLOC.COM
Start address: 0100H Ending address: 01B2H Bias: 0000H
Saved image size: 256 bytes (0100H, - 2 records)
No Fatal error(s)
Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft
Data 0100 08FF < 2047>
51771 Bytes Free
[0000 08FF 8]
No Fatal error(s)
Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft
Data 0100 091A < 2074>
51744 Bytes Free
[0000 091A 9]
ZMAC Relocating Macro Assembler v 1.7, 04/09/93
Copyright 1988,1989 by A.E. Hawley
P0:ZSDOS.Z80 assembled with NO ERRORS
..To produce:
P0:ZSDOS.REL, P0:ZSDOS.PRN
Source Lines 3345 Unused Memory 7995H
Labels 429 Total Code Size 0DF6H
Macros -Read none
-Expanded none
=== SEGMENT SIZES ===
ASEG =empty CSEG =0DF6H DSEG =empty BLANK =empty
Named COMMON segments
_BIOS_
LINK 1.31
/_BIOS_/ E600
ABSOLUTE 0000
CODE SIZE 0E00 (D800-E5FF)
DATA SIZE 0000
COMMON SIZE 0000
USE FACTOR 1C
TASM Z80 Assembler. Version 3.2 September, 2001.
Copyright (C) 2001 Squak Valley Software
tasm: pass 1 complete.
tasm: pass 2 complete.
tasm: Number of errors = 0
..\zcpr-dj\zcpr.bin
zsdos.bin
..\cbios\cbios_wbw.bin
1 file(s) copied.
..\zcpr-dj\zcpr.bin
zsdos.bin
..\cbios\cbios_una.bin
1 file(s) copied.
loader.bin
zsys_wbw.bin
1 file(s) copied.
loader.bin
zsys_una.bin
1 file(s) copied.
*** CPM Loader ***
CP/M RMAC ASSEM 1.1
0A00
015H USE FACTOR
END OF ASSEMBLY
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
UTIL/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 136 Program Bytes.
12 Symbols Detected.
1 file(s) copied.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
BIOSLDR/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 1127 Program Bytes.
142 Symbols Detected.
1 file(s) moved.
1 file(s) moved.
LINK 1.31
COUT 0FAB ADDHLA 0F67 BCD2BIN 0FC9 BIN2BCD 0FDC
CIN 0F9F CRLF 0FBC CRLF2 0FB9 PHEX16 0F6C
PHEX8 0F77
ABSOLUTE 0000
CODE SIZE 0EEF (0100-0FEE)
DATA SIZE 0000
COMMON SIZE 0000
USE FACTOR 1E
1 file(s) moved.
1 file(s) copied.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
BIOSLDR/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 1203 Program Bytes.
145 Symbols Detected.
1 file(s) moved.
1 file(s) moved.
LINK 1.31
CIN 0FEB COUT 0FF7 ADDHLA 0FB3 BCD2BIN 1015
BIN2BCD 1028 CRLF 1008 CRLF2 1005 PHEX16 0FB8
PHEX8 0FC3
ABSOLUTE 0000
CODE SIZE 0F3B (0100-103A)
DATA SIZE 0000
COMMON SIZE 0000
USE FACTOR 1F
1 file(s) moved.
*** Resident CPM3 BIOS ***
1 file(s) copied.
1 file(s) copied.
CP/M RMAC ASSEM 1.1
023E
00AH USE FACTOR
END OF ASSEMBLY
CP/M RMAC ASSEM 1.1
0000
002H USE FACTOR
END OF ASSEMBLY
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
BOOT/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 655 Program Bytes. 324 Data Bytes.
125 Symbols Detected.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
CHARIO/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 128 Program Bytes.
28 Symbols Detected.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
MOVE/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 84 Program Bytes.
14 Symbols Detected.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
DRVTBL/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 32 Program Bytes.
22 Symbols Detected.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
DISKIO/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 188 Program Bytes. 1835 Data Bytes.
114 Symbols Detected.
Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234
UTIL/MF
End of file Pass 1
End of file Pass 2
0 Error(s) Detected. 136 Program Bytes.
12 Symbols Detected.
LINK 1.31
@ADRV 07F7 @RDRV 07F8 @TRK 07F9 @SECT 07FB
@DMA 07FD @DBNK 0800 @CNT 07FF @CBNK 023D
@COVEC FE24 @CIVEC FE22 @AOVEC FE28 @AIVEC FE26
@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 04EC
@DTBL 05A1 @CRDMA FE3C @CRDSK FE3E @VINFO FE3F
@RESEL FE41 @FX FE43 @USRCD FE44 @MLTIO FE4A
@ERMDE FE4B @ERDSK FE51 @MEDIA FE54 @BFLGS FE57
@DATE FE58 @HOUR FE5A @MIN FE5B @SEC FE5C
@CCPDR FE13 @SRCH1 FE4C @SRCH2 FE4D @SRCH3 FE4E
@SRCH4 FE4F @BOOTDU 04A3 @BOOTSL 04A4 @HBBIO 0599
ADDHLA 067D BCD2BIN 06DF BIN2BCD 06F2 DPH0 094F
@HBUSR 059C DPH1 0976 DPH10 0AD5 DPH11 0AFC
DPH12 0B23 DPH13 0B4A DPH14 0B71 DPH15 0B98
DPH2 099D DPH3 09C4 DPH4 09EB DPH5 0A12
DPH6 0A39 DPH7 0A60 DPH8 0A87 DPH9 0AAE
@SYSDR 067C CIN 06B5 COUT 06C1 CRLF 06D2
CRLF2 06CF PHEX16 0682 PHEX8 068D
ABSOLUTE 0000
CODE SIZE 0705 (0000-0704)
DATA SIZE 096B (0705-106F)
COMMON SIZE 0000
USE FACTOR 21
CP/M 3.0 System Generation
Copyright (C) 1982, Digital Research
Default entries are shown in (parens).
Default base is Hex, precede entry with # for decimal
Use GENCPM.DAT for defaults (Y) ?
Create a new GENCPM.DAT file (N) ?
Display Load Map at Cold Boot (Y) ?
Number of console columns (#80) ?
Number of lines in console page (#24) ?
Backspace echoes erased character (N) ?
Rubout echoes erased character (N) ?
Initial default drive (A:) ?
Top page of memory (FD) ?
Bank switched memory (N) ?
Double allocation vectors (N) ?
Accept new system definition (Y) ?
Setting up Allocation vector for drive A:
Setting up Checksum vector for drive A:
Setting up Allocation vector for drive B:
Setting up Checksum vector for drive B:
Setting up Allocation vector for drive C:
Setting up Checksum vector for drive C:
Setting up Allocation vector for drive D:
Setting up Checksum vector for drive D:
Setting up Allocation vector for drive E:
Setting up Checksum vector for drive E:
Setting up Allocation vector for drive F:
Setting up Checksum vector for drive F:
Setting up Allocation vector for drive G:
Setting up Checksum vector for drive G:
Setting up Allocation vector for drive H:
Setting up Checksum vector for drive H:
Setting up Allocation vector for drive I:
Setting up Checksum vector for drive I:
Setting up Allocation vector for drive J:
Setting up Checksum vector for drive J:
Setting up Allocation vector for drive K:
Setting up Checksum vector for drive K:
Setting up Allocation vector for drive L:
Setting up Checksum vector for drive L:
Setting up Allocation vector for drive M:
Setting up Checksum vector for drive M:
Setting up Allocation vector for drive N:
Setting up Checksum vector for drive N:
Setting up Allocation vector for drive O:
Setting up Checksum vector for drive O:
Setting up Allocation vector for drive P:
Setting up Checksum vector for drive P:
Setting up directory hash tables:
Enable hashing for drive A: (N) ?
Enable hashing for drive B: (N) ?
Enable hashing for drive C: (N) ?
Enable hashing for drive D: (N) ?
Enable hashing for drive E: (N) ?
Enable hashing for drive F: (N) ?
Enable hashing for drive G: (N) ?
Enable hashing for drive H: (N) ?
Enable hashing for drive I: (N) ?
Enable hashing for drive J: (N) ?
Enable hashing for drive K: (N) ?
Enable hashing for drive L: (N) ?
Enable hashing for drive M: (N) ?
Enable hashing for drive N: (N) ?
Enable hashing for drive O: (N) ?
Enable hashing for drive P: (N) ?
Setting up Blocking/Deblocking buffers: