mirror of
https://github.com/wwarthen/RomWBW.git
synced 2026-02-06 14:11:48 -06:00
* added hack to handle tunes * quiet clean * added chmod for execution * suppress warnings * Multi-boot fixes * the windows build somehow thinks that these filesystems are cpm3. * credit and primitive instructions * Update sd.asm Cosmetic fix. * make compile shut up about conditionals * Add bin2asm for linus and update build to process font files under linix * fixed quoted double quote bug, added tests * added tests * added bin2asm for font file source creation * Revert linux bin2asm font stuff * added rule for font source generation * build fonts * added directory mapping cache. if the same directory is being hit as last run, we don't need to rebuild the map. will likely break if you are running more than one at a time, in that the cache will be ineffective. also, if the directory contents change, this will also break. * removed strip. breaks osx * added directory tag so . isn't matched all over the place * added real cache validation * fixed build * this file is copied from optdsk.lib or optcmd.lib * install to ../HBIOS * prerequisite verbosity * diff soft failure and casefn speedup * added lzsa * added lzsa * removed strip. breaks on osx * added clobber * added code to handle multiple platform rom builds with rom size override * added align and 0x55 hex syntax * default to hd64180 * added N8 capability * added SBC_std.rom to default build * added support for binary diff * diff fixes * clean, identical build. font source generator emitted .align. this does not match the windows build * Upgrade NZCOM to latest * Misc. Cleanup * fixed expression parser bug : ~(1|2) returned 0xfe * added diff build option * Update Makefile Makefile enhancement to better handle ncurses library from Bob Dunlop. * Update sd.asm Back out hack for uz80as now that Curt fixed it. * Misc. Cleanup * UNA Catchup UNA support was lacking some of the more recent behavior changes. This corrects most of it. * Add github action for building RomWBW * Bump Pre-release Version * Update build.yml Added "make clean" which will remove temporary files without removing final binary outputs. * Update Makefile Build all ROM variants by default in Linux/Mac build. * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update Makefile * Update for GitHub Build Case issue in TASM includes showing up in GitHub build. This should correct that. * Added an gitignore files to exclude generated files * Removed Tunes/clean.cmd and Tunes/ReadMe.txt - as make clean removes them * Build.sh: marked as executable chmod +x Build.sh * Fix to HBIOS/build.sh When adding files to rom disk, if files were missing, it would error out. It appears the intent is to skip non-existing files. Updated to log out correctly for missing files - and continue operation. * Update Microsoft NASCOM BASIC.docx Nascom manual, text version by Jan S (full name unknown) * Fix issue with Apps/Tune not making If dest directory does not exist, fails to make Apps * Create ReadMe.txt * Update Makefile * Update Build.sh * Make .gitignores for Tools/unix more specific * cpmtools Update Updated cpmtools applications (Windows only). Removed hack in diskdefs that is no longer required. * HBIOS Proxy Temp Stack Enhancement Reuse the bounce buffer area as the temporary stack space required briefly in HBX_INVOKE when transitioning banks. Increases size of temporary stack space to 64 bytes. * Update ReadMe.txt * HBIOS - clean up TMPSTK * Update hbios.asm Minor cosmetic changes. * Build Process Updates Minor udpates to build process to improve consistency between Windows and Mac/Linux builds. * Update hbios.asm Add improved interrupt protection to HBIOS PEEK, POKE, and BNKCPY functions. * hbios - wrap hbx_bnkcpy * hbios - adjust hbx_peek hbx_poke guards * Update hbios.asm Adjusted used of DI/EI for PEEK and POKE to regain a bit of INTSTK space. Added code so that HB_INVBNK can be used as a flag indicating if HBIOS is active, $FF is inactive, anything else means active. * Add HBIOS MuTex * Initial Nascom basic ecb-vdu graphics set and reset for 80x25b screen with 256 character mod * Finalize Pre-release 34 Final support for FreeRTOS * Update nascom.asm Optimization, cleanup, tabs and white spaces * IDE & PPIDE Cleanup * Clean up Make version include files common. * Update Makefile * Update Makefile * Build Test * Build Test * Build Fixes * Update nascom.asm Cleanup * Update nascom.asm Optimization * hbios - temp stack tweak * Update hbios.asm Comments on HBX_BUF usage. * Update nascom.asm Optimization * Update nascom.asm Setup ECB-VDU build option, remove debug code * Update nascom.asm Set default build. update initialization * Update nascom.asm Make CLS clear vdu screen * Update nascom.asm Fixup top screen line not showing * Add SC131 Support Also cleaned up some ReadMe files. * HBIOS SCZ180 - remove mutex special files * HBIOS SCZ180 - adjust mutex comment * Misc. Cleanup Includes some minor improvements to contents in some disk images. * Delete FAT.COM Changing case of FAT.COM extension to lowercase. * Create FAT.com Completing change of case in extension of FAT.com. * Update Makefile Remove ROM variants that just have the HBIOS MUTEX enabled. Users can easily enable this in a custom build. * Cleanup Removed hack from Images Makefile. Fixed use of DEFSERCFG in various places. * GitHub CI Updates Adds automation of build and release assets upon release. * Prerelease 36 General cleanup * Build Script Cleanups * Config File Cleanups * Update RomWBW Architecture General refresh for v2.9.2 * Update vdu.asm Removed a hack in VDU driver that has existed for 8 years. :-) * Fix CONSOLE Constant Rename CIODEV_CONSOLE constant to CIO_CONSOLE because it is a unit code, not a device type code. Retabify TastyBasic. * Minor Bug Fixes - Disk assignment edge case - CP/M 3 accidental fall thru - Cosmetic updates * Update util.z80 * Documentation Cleanup * Documentation Update * Documentation Update * Documentation Updates * Documentation Updates * Create Common.inc * Documentation Updates * Documentation Updates * doc - a few random fixes * Documentation Cleanup * Fix IM 0 Build Error in ACIA * Documentation Updates * Documentation Cleanup * Remove OSLDR The OSLDR application was badly broken and almost impossible to fix with new expanded OS support. * Bug Fixes - Init RAM disk at boot under CP/M 3 - Fix ACR activation in TUNE * FD Motor Timeout - Made FDC motor timeout smaller and more consistent across different speed CPUs - Added "boot" messaging to RTC * Cleanup * Cleanup - Fix SuperZAP to work under NZCOM and ZPM3 - Finalize standard config files * Minor Changes - Slight change to ZAP configuration - Added ZSDOS.ZRL to NZCOM image * ZDE Upgrade - Upgraded ZDE 1.6 -> 1.6a * Config File Tuning * Pre-release for Testing * cfg - mutex consistent config language * Bump to Version 3.0 * Update SD Card How-To Thanks David! * update ReadMe.md Remove some odd `\`. * Update ReadMe.txt * Update ReadMe.md * Update Generated Doc Files * Improve XModem Startup - Extended startup timeout for XM.COM so that it doesn't timeout so quickly while host is selecing a file to send. - Updated SD Card How-To from David Reese. * XModem Timing Refinements * TMS Driver Z180 Improvements - TMS driver udpated to insert Z180 I/O waitstates internally so other code can run at full speed. - Updated How-To documents from David. - Fixed TUNE app to properly restore Z180 I/O waitstates after manipulating them. * CLRDIR and ZDE updates - CLRDIR has been updated by Max Scane for CP/M 3 compatibility. - A minor issue in the preconfigured ZDE VT100 terminal escape sequences was corrected. * Fix Auto CRT Console Switch on CP/M 3 * Handle lack of RTC better DSRTC driver now correctly returns an error if there is no RTC present. * Minor RTC Updates * Finalize v3.0.1 Cleanup release for v3.0 * New ROMLDR and INTRTC driver - Refactored romldr.asm - Added new periodic timer based RTC driver * CP/M 3 Date Hack - Hack to allow INTRTC to increment time without destroying the date * Update romldr.asm Work around minor Linux build inconsistency * Update Apps for New Version * Revert "Update Apps for New Version" This reverts commitad80432252. * Revert "Update romldr.asm" This reverts commit4a9825cd57. * Revert "CP/M 3 Date Hack" This reverts commit153b494e61. * Revert "New ROMLDR and INTRTC driver" This reverts commitd9bed4563e. * Start v3.1 Development * Update FDISK80.COM Updated FDISK80 to allow reserving up to 256 slices. * Update sd.asm For Z180 CSIO, ensure that xmit is finished, before asserting CS for next transaction. * Add RC2014 UART, Improve SD protocol fix - RC2014 and related platforms will autodetect a UART at 0xA0 and 0xA8 - Ensure that CS fully brackets all SD I/O * ROMLDR Improvements .com files can now be started from CP/M and size of .com files has been reduced so they always fit. * Update commit.yml Run commit build in all branches * Update commit.yml Run commit build for master and dev branches * Improved clock driver auto-detect/fallback * SIO driver now CTC aware The SIO driver can now use a CTC (if available) to provide much more flexible baud rate programming. * CTC driver fine tuning * Update xmdm125.asm Fixed a small issue in core XM125 code that caused a file write error message to not be displayed when it should be. * CF Card compatibility improvement Older CF Cards did not reset IDE registers to defaults values when reset. Implemented a work around. * Update ACIA detection ACIA should no longer be detected if there is also a UART module in the system. * Handle CTC anomaly Small update to accommodate CTC behavior that occurs when the CTC trigger is more than half the CTC clock. * Update acia.asm Updated ACIA detection to use primary ACIA port instead of phantom port. * Update acia.asm Fix bug in ACIA detection. Thanks Alan! * MacOS Build Improvement Build script updated to improve compatibility with MacOS. Credit to Fredrik Axtelius for this. * HBIOS Makefile - use env vars for target Allow build ROM targets to be restricted to just one platform thru use of ENV vars: ROM_PLATFORM - if defined to a known platform, only this platform is build - defaults to std config ROM_CONFIG - sets the desired platform config - defaults to std if the above ENVs are not defined, builds all ROMs * Added some more gitignores * Whitespace changes (crlf) * HBIOS: Force the assembly to fail for vdu drivers if function table count is not correct * Whitespace: trailing whitespaces * makefile: updated some make scripts to use when calling subdir makefiles * linux build: update to Build.sh fix for some platforms The initialization of the Rom dat file used the pipe (|) operator to build an initial empty file. But the pipe operator | may sometimes return a non-zero exit code for some linux platforms, if the the streams are closed before dd has fully processed the stream. This issue occured on a travis linux ubuntu image. Solution was to change to redirection. * Bump version * Enhance CTC periodic timer Add ability to use TIMER mode in CTC driver to generate priodic interrupts. * HBIOS: Added support for sound drivers New sound driver support with initial support for the SN76489 chip New build configuration entry: * SN76489ENABLE Ports are currently locked in with: * SN76489_PORT_LEFT .EQU $FC ; PORTS FOR ACCESSING THE SN76489 CHIP (LEFT) * SN76489_PORT_RIGHT .EQU $F8 ; PORTS FOR ACCESSING THE SN76489 CHIP (LEFT) * Miscellaneous Cleanup No functional changes. Co-authored-by: curt mayer <curt@zen-room.org> Co-authored-by: Wayne Warthen <wwarthen@gmail.com> Co-authored-by: ed <linux@maidavale.org> Co-authored-by: Dean Netherton <dnetherton@dius.com.au> Co-authored-by: ed <ed@maidavale.org> Co-authored-by: Phillip Stevens <phillip.stevens@gmail.com> Co-authored-by: Dean Netherton <dean.netherton@gmail.com>
266 lines
12 KiB
Plaintext
266 lines
12 KiB
Plaintext
|
||
RELEASE.NOT - UPDATE INFORMATION ON NZCOM
|
||
|
||
|
||
Please understand that unlike purely commercial enterprises, Z-System is
|
||
mainly the work of enthusiasts. As such, Z-System never truly reaches
|
||
completion; each new development is more of a plateau upon which further
|
||
innovation occurs. Though we have done our best, the printed documentation
|
||
inevitably lags behind the most recent enhancements. Try to consult as
|
||
much material as possible about a given command before proceeding; if there
|
||
is a help or document file pertaining to the command, it supercedes printed
|
||
instructions, especially with regard to such matters as syntax or technical
|
||
specifications.
|
||
|
||
|
||
Notes of September 12, 1991
|
||
===========================
|
||
|
||
Release 1.2H involves a significant updating of the support utilities that
|
||
we distribute as a courtesy with NZCOM. We suggest that any Z-System user who
|
||
is not in regular contact with a Z-Node consider taking advantage of the Z-
|
||
System Software Update Service (ZSUS). Here are some of the important changes
|
||
with this release.
|
||
|
||
ZCNFG.COM, CONFIG.LBR:
|
||
Al Hawley has introduced a powerful and convenient method for
|
||
configuring programs. ZCNFG works either with individual CFG files or
|
||
with CFG files stored in the CONFIG.LBR library. For example, try
|
||
running the command "ZCNFG ZLT". ZCNFG will automatically extract
|
||
ZLT15.CFG from CONFIG.LBR.
|
||
|
||
NZBLITZ.COM, NZBLTZ14.HZP, NZBLTZ14.CFG:
|
||
These programs can be used to coldboot an NZCOM system very rapidly
|
||
with the complete system, including error handlers, shells, and TCAPs
|
||
already in place. Run "HELP NZBLTZ14" to learn more about it. Some
|
||
of its features can be tailored by running "ZCNFG NZBLITZ" with the
|
||
CFG file in the same directory.
|
||
|
||
LBREXT.COM:
|
||
This replaces LGET for extracting member files from LBR library files.
|
||
|
||
HELP.COM, LBRHELP.COM, HLPFILES.LBR:
|
||
HELP (actually HELPC14) is an improved version of the help utility.
|
||
It can work with normal help files (HLP) and crunched help files
|
||
(HZP). LBRHELP can work with normal or crunched help files that are
|
||
stored in a library (which is where we have put all the help files
|
||
distributed with NZCOM and Z3PLUS).
|
||
|
||
DOCFILES.LBR:
|
||
Documentation and help files have been collected into an LBR file.
|
||
|
||
ZLT.COM:
|
||
This is a full Z-System replacement for LT, and it handles the latest
|
||
LZH-compressed files.
|
||
|
||
COPY.COM:
|
||
This is the version of COPY from the ZSDOS/ZDDOS release. Enter "COPY
|
||
//" for syntax information. It replaces a dangerously defective copy
|
||
program provided with earlier releases.
|
||
|
||
LSH.COM, LSH.WZ, LSH-HELP.COM, LSHINST.COM, ZERR.COM:
|
||
These are the latest LSH command history shell and command-line editor
|
||
and the associated error handler (fixed-log versions). These
|
||
completely replace EASE.
|
||
|
||
CLEDINST.COM, CLEDSAVE.COM:
|
||
A transient history shell like LSH can be slow on floppy systems with
|
||
sluggish disk drives, even if the files have been placed in optimal
|
||
locations. Some of the RCP modules supplied no include an RCP-
|
||
resident command-line editor called CLED. Its features can be
|
||
configured using CLEDINST.COM, and the history can be saved to a file
|
||
using CLEDSAVE.COM.
|
||
|
||
TCAP.LBR, XTCAP.COM:
|
||
A number of programs now require a terminal capabilities descriptor
|
||
(TCAP) with extended functions. The standard TCAPs loaded with
|
||
TCSELECT do not have these functions. TCAP.LBR is a collection of
|
||
extended TCAPs for some terminals. XTCAP.COM is a program that can
|
||
add the most important extensions to a standard TCAP (it is a quick-
|
||
and-dirty fix until the full set of TCAPs is updated).
|
||
|
||
VIEW.COM:
|
||
This is Bridger Mitchell's file viewing utility. It is very powerful
|
||
(but it requires an extended TCAP).
|
||
|
||
NAME.COM:
|
||
This program can quickly add or remove a name for a single directory.
|
||
|
||
TCJ.INF:
|
||
TCJ has a new publisher (one of our own Z-Node sysops), and this file
|
||
tells how to take out a subscription (which all Z-System users
|
||
absolutely should do!).
|
||
|
||
ZFILEB38.LZT:
|
||
This is the BRIEF listing of all the support programs currently
|
||
available for use with Z-System. There is another file which includes
|
||
descriptions of all the programs, but it would fill up an entire
|
||
diskette!
|
||
|
||
|
||
Notes of November 5, 1989
|
||
=========================
|
||
|
||
1. NEW FILES: NZCPR.LBR, FCP.LBR, RCP.LBR.
|
||
2. TCSELECT PROBLEM.
|
||
3. ERA.COM, REN.COM, SAVE.COM, ETC.
|
||
4. LSH REPLACES EASE.
|
||
5. NZBLITZ IS HERE!
|
||
6. MINOR UPDATE NOTES.
|
||
7. TO NEW Z-SYSTEM USERS.
|
||
8. ALERT ABOUT NZCPM.COM AND NZCOM.CCP
|
||
9. CHANGE IN MKZCM DEFAULT AND STANDARD RCP
|
||
10. NZBIO+.ZRL
|
||
|
||
1. NEW FILES: NZCPR.LBR, FCP.LBR, RCP.LBR.
|
||
|
||
The main NZCOM.LBR now contains only the standard configurations of the
|
||
CPR, FCP, and RCP modules to minimize disk space requirements. Alternative
|
||
versions of these modules are now supplied in separate libraries. Modules
|
||
can be loaded directly from these libraries, or individual files can be
|
||
extracted and put into NZCOM.LBR to replace the default files. Each
|
||
library has a brief DOC file describing the modules (one of which is the
|
||
default version included in NZCOM.LBR).
|
||
|
||
|
||
2. TCSELECT PROBLEM.
|
||
|
||
A problem has been discovered with the operation of TCSELECT as described
|
||
in the manual. TCSELECT is a Z-System program and does not function
|
||
reliably under CP/M (on some systems it causes a crash). Fortunately there
|
||
is a simple fix: reverse the order of the instructions in the manual. Boot
|
||
up NZ-COM before attempting to create MYTERM.Z3T, and run TCSELECT only
|
||
after NZ-COM is running. Remember that you need both TCSELECT.COM and
|
||
Z3TCAP.TCP to generate your .Z3T file. The entries in the Z3TCAP library
|
||
for the Xerox computers has been patched to correct a long-standing error.
|
||
|
||
|
||
3. ERA.COM, REN.COM, SAVE.COM, ETC.
|
||
|
||
The standard configuration of Z-System does not include resident commands
|
||
for REN, DIR, or SAVE. These are provided instead as transient programs
|
||
(COM files), and you should copy any that you need to your working disk.
|
||
Several other functions that are often resident (but not always) are also
|
||
provided as COM files. Many of these are type-4 programs (see the manual).
|
||
We recommend using SDZ.COM as your standard directory display utility. It
|
||
is far more functional than the resident DIR commands in either Z-System or
|
||
CP/M, and it is designed to work properly under both.
|
||
|
||
|
||
4. LSH REPLACES EASE.
|
||
|
||
EASE has been replaced by a newer, more versatile, and well-behaved program
|
||
named LSH (Log SHell). Like EASE, LSH allows you to edit command lines
|
||
using WordStar-like control. Consult LSH.WZ before use for general
|
||
information and/or run HELPLSH while running LSH for a display of LSH's
|
||
capabilities. LSHINST installs and customizes LSH to taste. Error
|
||
handling is now taken care of by ZERR.COM, a separate program. Our great
|
||
thanks to Rob Friefeld for writing these superb Z-System tools and for
|
||
allowing us to include them with NZ-COM.
|
||
|
||
|
||
5. NZBLITZ IS HERE!
|
||
|
||
NZBLITZ is now included with NZ-COM. True to its name, NZBLITZ loads NZCOM
|
||
(and ZSDOS/ZDDOS, if present) in a flash, making it extremely helpful in
|
||
saving and reloading a given system configuration. Once you have configured
|
||
your system as wanted, log to drive A0: and type NZBLITZ NZLOAD. From now
|
||
on, your startup to Z-System is MUCH faster; just type "NZLOAD". Be
|
||
forewarned that NZBLITZ saves EVERYTHING as currently active, so be sure you
|
||
are at the directory (usually A0:) you wish the system to start in, and be
|
||
sure all active shells, flow states, terminal definitions, and so on are the
|
||
desired ones before proceeding. See NZBLITZ.NZT for more information.
|
||
|
||
|
||
6. MINOR UPDATE NOTES.
|
||
|
||
- The RCP WHLQ command no longer used. "WHL" alone displays the current
|
||
wheel status. As before, "WHL password" turns the wheel byte on. "WHL
|
||
xxx" now turns the wheel byte OFF if xxx is something other than the
|
||
correct password.
|
||
|
||
- ARUNZ is now a type-4 program which loads at the highest possible
|
||
memory location so as to save lower memory for immediate re-execution
|
||
with GO. See ARUNZ09R.DZC and TCJ31.MZG (as well as your NZ-COM or
|
||
Z3PLUS manual) for more on the amazing ARUNZ.
|
||
|
||
- VLU is no longer included, as it was not reliable. Please use LDIR,
|
||
LGET, LPUT, and LT instead to manipulate library files.
|
||
|
||
- At this writing, we are sorry to note that both Z-Node Central and the
|
||
Lillipute Z-Nodes mentioned in Chapter 7 of your manual are out of
|
||
service. Z-Nodes 2 and 3 are still going strong, however, as are the
|
||
many others listed in ZNODES.LST. Z-Node 2 is the new Z-Node Central.
|
||
We cannot recommend highly enough that you get a modem and investigate at
|
||
least one Z-Node as a source of inspiration and support.
|
||
|
||
- Version 5.0 of the ZEX batch processor replaces earlier versions. ZEX
|
||
now runs under both NZ-COM and Z3PLUS and is a very powerful means of
|
||
customizing programs and commands. The ZEX.RSX file mentioned in the
|
||
manual is no longer required. See ZEX50.DZC for help.
|
||
|
||
|
||
7. TO NEW Z-SYSTEM USERS.
|
||
|
||
- All files whose middle filetype character is "Z" (e.g., SAMPLE.DZC) are
|
||
"crunched" files which must be uncompressed with LT.COM or UNCRUNCH.COM
|
||
before use.
|
||
|
||
- As outlined in section 4.3.2 of your manual, most Z-System programs
|
||
have built-in help; type the name of any program followed by "//" for a
|
||
short description if you are confused.
|
||
|
||
- Finally, it is not at all necessary to master every nuance of the system
|
||
before it becomes useful. Please don't try to devour all of Z-System at
|
||
once. Instead, we suggest that you decide what aspects of the system you
|
||
will find most helpful and try to master one or two of those before
|
||
exploring further. We think you will find that if you choose wisely,
|
||
learning one aspect fully not only makes that aspect of your computing
|
||
world easier, it also equips you with the skills and confidence with
|
||
which to surmount other aspects of Z-System more confidently.
|
||
|
||
|
||
8. ALERT ABOUT NZCPM.COM AND NZCOM.CCP
|
||
|
||
Some users have been tripped up by the way NZCOM handles the generation of
|
||
an NZCPM.COM file: it writes such a file only if one does not already exist.
|
||
This speeds up loading of the system. However, should you ever make any
|
||
change to your base CP/M system (such as installing ZSDOS/ZDDOS or a new
|
||
version of the BIOS), you should be sure to erase the NZCPM.COM file so that
|
||
NZCOM will create a new one the next time it is run. You should also be
|
||
sure to use NZCOM and not NZBLITZ to load the system the first time after
|
||
such a change.
|
||
|
||
You should also be aware that warmboots of the NZ-COM Z-System are performed
|
||
by loading the NZCOM.CCP file containing the image of the current command
|
||
processor. This means that you must not change the diskette in the A: drive
|
||
unless you have copied the **CURRENT** NZCOM.CCP file (if you only use one
|
||
system configuration, the current version will not change) to the diskette
|
||
you are going to place in the A: drive.
|
||
|
||
|
||
9. CHANGE IN MKZCM DEFAULT AND STANDARD RCP
|
||
|
||
Carson Wilson and Rob Friefeld have made some major changes in the RCP code
|
||
(see the DOC file in RCP.LBR). The standard RCP module is now 18 records
|
||
long instead of 16. MKZCM.COM has been patched to provide this value as a
|
||
default.
|
||
|
||
|
||
10. NZBIO+.ZRL
|
||
|
||
The BIOS in some computers uses the Z80 index and alternate registers
|
||
without
|
||
saving them on the stack and restoring them. These computers include the
|
||
TeleVideo 80x machines, the Oneac On!, the Zorba, and a number of other
|
||
machines. Some programs (JETLDR and EDITNDR, for example) will not function
|
||
properly under these conditions. The file NZBIO+.ZRL in NZCOM.LBR is a
|
||
special version of the NZ-COM virtual BIOS that protects the Zilog registers
|
||
across all BIOS calls. To use this BIOS, you much use MKZCM to allocate 4
|
||
records to the BIOS. If you observe strange behavior on your system with
|
||
NZ-COM, you might want to try using this special BIOS.
|
||
|
||
|
||
|
||
- End of RELEASE.NOT -
|
||
|