home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Brotikasten
/
BROTCD01.iso
/
ms_dos
/
64nt8255.txt
< prev
next >
Wrap
Text File
|
1995-08-15
|
26KB
|
637 lines
This file will contain the newest additions to 64NET for the last few
versions, until each alteration/addition is incorperated into the
64NETMAN.DOC file. So to get the most from the 64NET system it is suggested
that you read the 64NETMAN.DOC file first, then read this file through.
Note that much of this information is aimed primarily at those who write
software more than the typical end user - having said this however, the
typical user could most certainly gain a few pearls from reading this in any
case.
-----------------------------------------------------------------------------
IMPORTANT!!
If you intend to use 64NET with GEOS, please read the READTHIS.TOO file
(the first few sections anyway ;) as it explains the use of the 64NETCFG
programme which greatly simplifies GEOS configuration under 64net!!
If you do not read this additional information you may find yourself in a
spot of bother when you go to copy files to and from GEOS!!
-----------------------------------------------------------------------------
I hope the 64NET system is of much use to you as it is to me!
Paul Gardner-Stephen
64NET v1.82.53 BETA Addendum
----------------------------
(15th August 1995)
1) 64NET now supports a few improved things for GEOS support:
i) Read/Write - Write Protect flag
(In each partition entry just before the drive type byte)
ii) Improved partition creation now handles Add above, add below and
add to end. NOTE: There may be problems with add abovce and add
below where the wrong partition is formatted!!! Please use only
Add to end when creating a partition. The reason why this happens
is a complex one, and there is no easy fix yet! (it has to do with
the virtualisation of the disk images and virtual memory paging
behavior etc.....)
2) Later distributions of this package should now include the GEOS drivers
directly!! If you are still unregistered you will only be able to read
disk images. Your dealer should be able to provide you with a few demo
disk images to demonstrate the power of the 64NET & GEOS combination!
English translations of the GEOS software shouldnt be too far off either!
3) 64NETCFG.EXE does *NOT* handle the old style virtual memory settings in
64NET.INI. This is *intentional* as 64NET is intended to use only the
disk images with GEOS now! As there is no other software which depends
on the Virtual memory system at this stage, i have decided to remove it
from the code at some stage in the near future. IE - you should *always*
have GEOS Virtual Mounting activated (The only reason this setting is
still able to be changed in 64NETCFG.EXE is for people who have been BETA
testing the GEOS software (the very few of them!) so that they have a
chance to transfer their files over to the new system.
64NET v1.82.51 BETA Addendum
----------------------------
(Saturday 22th July 1995)
1) 64NETCFG improved with more functions. It is now officially recommended
that you run 64NETCFG after INSTALL to help you configure 64NET to your
likings.
NOTICE: When ever you tag mounts to add or remove, you *MUST* hit S for
the change to be recorded, and it must be done on that screen! Then
press ESC to go back to the previous.
Appologies as there is currently no German translation of this programme.
2) 64NET can now virtualise the quick mount list into the virtual memory
system, thus allowing GEOS to directly access .D64 and other disk image
files.
You may also create disk images easily via the partition manager, and
these disk image files will automatically be placed in \64NET\GEOS.
NOTE: You may only use the partition numbers 1 to 26 in the quick mounts
if you intend to activate virtualisation, this is done autmatically if you
use the 64NETCFG programme, or create the partitions from in GEOS.
3) If you have been using the "old" GEOS mode in previous versions of 64NET,
you will have to back all of the data yuo wish to keep onto disks, as the
old style partitions are not available under the new scheme. This should
only effect about 3 BETA testers, so it wont be a real problem :)
64NET v1.82.50 BETA Addendum
----------------------------
(Thursday 20th July 1995)
1) Printing under GEOS now works properly (woop woop!;)
Hopefully the GEOS drivers will be included in the 64net distribution
in the very near future.
NOTE: Printing takes almost 100% of the CPU time as there is a constant
character stream coming from the C64/C65/C128 - thus background operation
is disgouraged (and has not been tested yet! - but feel free to try).
2) The printer selection is now improved:
[PRINTER] (or [DRUCKER])
DEV=<LPT1|LPT2|LPT3|LPT4|n:\path\filename.ext>
64NET will attempt to determine if your have specified a port or a file.
Use the 64NETCFG programme described below to set this option with
ease!
3) The 64NET archive now contains a simple configuration programme called
64NETCFG.EXE. This programme will allow you to alter some of the more
useful options in the 64NET.INI, and provides verbose information on
the function of each option. At this stage only nine options are listed,
but expect this to increase!
It is highly recommended that you run this programme as it can be used
to easily set your printer device for use with GEOS amongst other things.
64NET v1.82.45 BETA Addendum
----------------------------
18 July 1995
1) 64NET now attempts to swap into EMS memory when forced to background.
Put a line with just the word EMS under preferences in 64net.ini, eg:
[PREFERENCES]
EMS
This means that background mode is a little slower, but takes less than
8KB!! (I have 615KB free with 64net in background)
Please report any problems with this!
NOTE: To stop "jerky" speed of the foreground process you should override
the SPEED value under preferences to a "nice" value (so that the port
scan is a little to fast to read), otherwise you may notice slightly
crusty performance of the foreground processes. This new mode has only
been tested behind MS-DOS edit and a few other smallish programmes, but
no problems have yet been encountered.
2) Hopefully printer ready detection is working now (after how long!!)
3) Work has begun on 64NET v2.00.00 - this will still be some time away,
but expect such niceties as intrinsic d64/d71/d81/dhd access, much
improved compatibility etc. v2 will also work under UNIX, and over WAN's
(such as Internet)
64NET v1.82.42 BETA Addendum
----------------------------
1) 64NET now resets the ports on termination to $00.
Thus reading a $80 can now be used as a good indicator of 64NET's
presence.
2) New X commands for locking the old style Virtual Memory system.
NOTE: Locks only apply to writes, other parties may still read freely.
XLLXXX - Attempt to lock the virtual memory system.
Returns: $00 if successful, or $0x if failed (where x is the port
number where the lock is currently in use).
$00 - A second zero byte is sent to mark end of packet.
XLUXXX - Attempt to unlock virtual memory. Returns same as above.
XLQXXX - Returns as above, without trying to lock or unlock anything.
(that is, query lock status).
NOTE: A process should only lock the vm file for short periods of time
when writing sensitive data, eg a partition table, or directory etc..
3) Both printer, and virtual memory locks are released during the 'boot' and
login sequences. This ensures that a rogue lock can be removed quickly in
the event of a software failure/'Guru Meditation'. (Messages will be
displayed as the locks are removed).
4) Pressing F7 on the server will now display who has what facilities locked.
This display is not updated continuously for various reasons.
5) Inter process-pipelines now operational!
Use the following DOS commands:
IPPSxMESSAGE - send a message to one or more stations
where x is the destination - 1 ,