Hey folks. I'm trying to get "Swedish" Pascal v6.3 running under
RSX-11M-Plus v4.6, and have hit a problem. The created PAS.TSK crashes
on invocation, and I suspect it may be due to a patch that gets applied
to a library during the build process. This appears in PAS.BLD:
;
; The above GBLPAT statement patches a branch instruction
; into the system overlay autoload routine AUTO.
; The last few releases of most operating systems have had
; different versions of AUTO. The proper GBLPAT statement
; to use above depends on which AUTO routine you have on
; your system. You can identify which one you have by
; examining the object module ident of module AUTO in
; the system object library, SYSLIB. Use a command such as
; "LBR LB:[1,1]SYSLIB/FU" to do this. The GBLPAT statements
; to use with each AUTO routine are:
;
; AUTO ident GBLPAT statement
; ============ ==================
; ??early?? GBLPAT=ROOT:$AUTO+34:437
; 08 GBLPAT=ROOT:$AUTO+34:435
; 09.08 GBLPAT=ROOT:$AUTO+36:441
; 10.02 GBLPAT=ROOT:$AUTO+36:431
;
The ident of AUTO in my system is 10.05, making that patch potentially
land at the wrong address. However, that's just my suspicion. Has
anyone gotten Swedish Pascal v6.3 running under RSX-11M-Plus v4.6?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
This release contains a lot of fixes and improvements in many areas.
There is one very serious bug in TCP that is fixed in this release which
is why I really encourage people to upgrade.
Highlights:
- Stability and reliability improvements in TCP.
- Improved SPOOF detection.
- Improved stability.
Detailed information on things that have been done since the last release:
Installation process:
- The IPGEN script now more smoothly handles updates to an existing
installation.
Ethernet driver:
- Improved driver reset handling.
- Implemented MTU backoff in ethernet driver, to handle unpatched DEC
XU: driver.
TCP:
- At socket close time, if there were pending packets to process still
in the socket, the system pool could become corrupted, causing a crash
at some random later time.
- Add more spoof processing for suspicious connections.
FTPD:
- Improved error handling for not logged in clients.
HTTP:
- Implemented spoof processing for connections which looks suspicious.
MAILD:
- Implemented spoof processing for connections which looks suspicious.
Mail client:
- Added basic hooks for extending mail to deal with several folders
(still not complete).
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
The firewall for Mim have now been removed, so no need for the alternate
ports, but Mim is still listening to the alternate ports as well.
ftp: 10021
telnet: 10023
As a final word about this release. As always things progress with time,
but I think it's safe to say by now that BQTCP is now a very stable
TCP/IP with almost all features one can expect. There might always be
some more work on the lower level protocols, but at this point, expect
that most work and updates will be more and more on various daemons and
clients.
If there is anything in particular anyone is looking for, let me know.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Before I go looking on Ebay, I thought I'd ask here first.
My Alphaserver 800 5/500 wasn't responding when I came back from a business trip.
And when I rebooted it, I heard the 1-2-4 beep codes and no screen.
Found out it means "Backup cache error. Replace the CPU daughter board"
And I found out in the manual that "The system can be operated with the B-cache disabled until a replacement CPU daughter board is available." After re-seating the CPU board and the memory it still got the error beeps and changed the J1 jumper and it booted up fine.
Does anyone know the impact of running with the B-cache disabled?
The text in the system manual said the jumper setting "Allows the system to run despite bad B-cache until a replacement CPU board is available." How long can the system be run in this mode?
just curious so I know how much time I have to watch for a reasonable price 5/500 CPU module to show up on ebay (since there aren't many VAX/Alpha geeks in DC on craigslist).
Thanks in advance
Mike
