Well, about two weeks since my last announcement, but I figured I should
do another one.
I've cut a new release of TCP/IP for RSX, and I encourage everyone to
update to this latest release.
A short list of changes since my last release:
Documentation:
. I've worked some on the documentation, and filled out some parts that
were previously TBD.
TCP:
. Performance improvements. In general, I've improved file transfer
performance by about 20% by tuning when TCP ACK messages as well as
window updates are sent. On links where packets are dropped from time to
time, the performance improvements can be significantly higher.
. Bugfix. Retry counter were incorrectly reset under some circumstances.
. Bugfix. TCP did not resend an ACK if the same data was received twice.
. Bugfix. TCP sockets could erronously be left in a closed state with
no task. However, looking at the socket, it looked like a task was
associated.
FTP:
. Size calculation for stream type files in RSX mode was done incorrectly.
Applications:
. I've included a precompiled version of PCL.TSK
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
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
I have two "flippy organizers" (that's around 20 floppies each) full of
these oddball floppies.
Picture at
https://www.flickr.com/photos/131070638 at N02/22020178558/in/dateposted/
They are 8", hard sectored, and the sectors are on the outer edge rather
than the hub, and there is an odd cutout on one edge that goes inside the
drive.
I know I don't have a machine that uses these, so they are available for
trade.
J
I know Chuck Guzis has written about this, but I don't see that he's done
so publicly in the last few years, so I thought I'd ask here about his and
others' views on the perennial question of whether (some) 3.5" DSHD disks
can be reliably used in DSDD-only drives. The oft-repeated claim is that
writing can appear to work just fine, but that even a few months later read
errors will occur.
On <http://www.retrotechnology.com/herbs_stuff/guzis.html> Chuck was quoted
as (actually, correct me if I'm wrong -- it's a little hard to be sure this
was Chuck's words) as saying "Usually, they're just fine, with the error
rate approximately the same, whether or not 2D or HD media was used." Just
before that, he said "I think that the overall quality of DSHD 3.5" media
isn't what it used to be, so that might contribute to the general
impression that 3.5" HD diskettes used as 2D aren't reliable. I have
problems enough finding reliable 3.5" DSHD floppies used as such." Chuck et
al., what's your feeling now, both on the overall reliability of HD disks
in DD drives, and on whether it depends on how recently the disks were
produced?
Elsewhere on the page (I don't recall now if it was Herb or Chuck that said
it) it was conjectured that HD disks that have never been formatted as HD,
-OR- disks that have gone through a good degaussing, will have better luck
retaining data. What does everyone think about this? And would an
electromagnetic library security system (the kind that's like a tube
through which checked-out materials are put; often with a caution not to
put tapes or floppies through it) be a suitable degausser?
--
Eric Christopherson
Hi,
I've built a Harddisk-Controller-Emulator for my system which accesses
a IDE (PATA) harddisk with an ATMega in PIO mode. It works like a charm
except for one WD harddisk. The harddisk itself works fine with MS-DOS
6.22 and FreeBSD but refuses to work with my ATMega.
On reading or writing a sector, right after the command is issued, the
error bit is set in the status register, and the error register indicates
an ABRT.
# ABRT:
# indicates the requested command has been aborted due to a
# drive status error (such as not ready or write fault) or because
# the command is invalid.
Right after power up and after the disk got ready, I issue the IDENTIFY
command and read the data back which works perfectly. After that I
read sector 0 and this fails.
I use LBA since the harddisk states that is supportes LBA. Nevertheless
I also tried accessing the harddisk with CHS mode and got the same error.
I tested other harddisks which support either CHS+LBA or CHS only. All
of them work perfectly.
What happens after powerup to read block 0 of the disk in LBA mode:
- Setup AVR ports and so on
- wait until RDY gets high
- wait until BSY gets low
- issue a Drive/Head register Command with value 0
- wait until BSY gets low
- issue a Command Register Command with value 0xEC (identify device)
- *read data*
- process and print out data
- wait until BSY gets low
- issue a Sector Count register Command with value 0
- issue a Sector Number register Command with value 0
- issue a Cylinder Low register Command with value 0
- issue a Cylinder High register Command with value 0
- issue a Drive/Head register Command with 0 + 0xE0 (LBA, Drive 0)
- issue a Command Register Command with value 0x20 (Read Sector)
- *read data*
*read data*:
- wait until BSY gets low
- check ERR bit in the Status register <- set on cmd 0x20 here
- wait until DRQ gets high
- issue a Data register Command with no data
- put /RD on low
- read 512 bytes of data
- put /RD on high
- check ERR bit in the Status register
Issuing a Command works always like setting /CS0, /CS1, /DA0, /DA1,
/DA2 to low, and then set the needed signals to high so the desired
command is indicated.
When data has to be transfered with this command, the lower 8 bits
are put then onto the port, /WR is set to low afterwards, 3 nop()
are done and /WR is set back to high.
Does anyone see an error what could make the drive behave like I said?
- ATA IDENTIFY works, and the drives data can be read
- after a read or write sector command is issued, the status register
directly goes 0xd0 (busy) and with the 2nd fetch 0x59 (not busy, drq
set, err set)
Regards, Oliver
May be of interest to some list members - appeared, of all places, in the
property section of a local newspaper - the Commodore 64 gets a good mention
but I suspect list members might remember (or reminisce) over the other 9
too or as well.
http://www.domain.com.au/news/10-forgotten-wonders-of-1980s-homes-20151217-g
lpoof/
++++++++++
Kevin Parker
++++++++++
Has any of you took one of them old choose your own adventurer books and
coded it into a text RPG in basic? if so how well did it work as soon as
I get all my Commodore 64 setup on CHRISTmas day that is the first thing
that I am going to start working on. The one I am doing is *" THE DRAGON
OF DOOM "* I have been brushing up on my coding skills with old books
like BASIC COMPUTER GAMES AND SUCH... So wirh me luck and if any of you
have done this brfotr please let me know how it ernt? The only Major
things I have forgotten are...
1. Clear the screen for the next page!
2, doing the page jumps like in the book it will say if your want top
enter turn to page 356 ot
if you want to keep walking turn to page 17 that is the code I have
forgoten But I am sure you all will be able to help me make this game
the best it can be. I wish I fould add hiypointd and damage points find
gold but I guess when I get to that Ill ask only after I dearch th net
for awncers. thanks yall GOD BLESS AND MERRY CHRISTmas!
'
Would you buy the new Commodore 64 ? ? ?
>From PC-World
"
The new Commodore 64 <http://www.commodoreusa.net/CUSA_C64.aspx> is,
like the old 64, an entire system inside a (rather thick) keyboard. The
old Commodore 64
<http://www.pcworld.com/article/195094/ccs64_turns_your_pc_into_a_commodore_…>
originally cost $595 and featured an MOS Technology 6510
<http://en.wikipedia.org/wiki/MOS_Technology_6510> microprocessor, an
impressive 64KB of RAM, and VIC-II
<http://en.wikipedia.org/wiki/MOS_Technology_VIC-II> graphics that
supported a screen resolution of 320 by 200 pixels.
The new system, which also starts at $595, is a little more modern: it's
got a Dual Core 525 Atom processor, an Nvidia Ion2 graphics chipset, 2GB
of RAM (upgradeable to 4GB), a 160GB hard drive, and built-in Wi-Fi. On
the left side of the keyboard there's a slot or tray-load DVD
(upgradeable to Blu-ray), and on the right side there's a multi-format
card reader, along with a USB 2.0 port. The rear features four
additional USB 2.0 ports; mouse and keyboard PS/2 ports; DVI, VGA, and
HDMI ports; Ethernet; and support for 6-channel HD audio. It runs Linux,
but you can install Windows if you like.
Pretty cool for a computer that looks like it's from the 80's. Of
course, if you just want the look--and you want to throw your own stuff
inside--you can also order the "Barebones" package on the new Commodore
64 Website. The Barebones package costs $250 and gets you the case,
chassis, keyboard, and multi-format card reader with USB 2.0 port. On
the other hand, if you'd like to go all out, there's also an $895
"Ultimate" package that includes a Blu-ray drive and a 1TB hard drive.
The new Commodore 64 begins shipping at the end of this month, but you
can order yours now
<http://www.commodoreusa.net/CUSA_C64Select.aspx>--go get your BASIC
<http://en.wikipedia.org/wiki/Commodore_BASIC> on! "
I myself am going to buy one just for a collector sake. The new
Commodore phone seemes to be selling like hotcakes from the research I
have done on it. There is also a switch in the back to boot the original
C-64 I think It will be a fun computer to 0wn.
What are your thoughts I will be wait a year or so because 545.00 is a
bit much for me to spend on it but anyway Like I said what are your
thoughts on it Ill post a youtube link below with the newC-64 review...
Video Link here -------> https://www.youtube.com/watch?v=j7Lo9Q0RiX0
Hi
Went to Starwars last night. Oh boy did they get it right this time!!
Look and feel of the original 1977 version. Really good new actors.
In a way it was like a retelling of history but in a completly new way.
The bombing runs up the trench used the same sighting system as thirty
odd years ago.
Added to that several scenes were filmed at the former US Airbase at
Greenham Common.
Its a mile from where I live and I passed within 50yards of where the
filming took place on my way to the cinema.
The bunkers are in a natural hollow in the ground and surrounded by
triple fences with watch towers.
In the film you can see the typical camoflarge netting in the back
ground. - Nothing to do with the film.
They were trying to hide the set from passing aircraft.
They managed to keep it a secret until one day a guy was passing in his
microlight and spotted the MF
(or at least most of it) parked by the old cruise missile bunkers.. He
was not a fan but his son was.
He calls his son up on his mobile and says:
You know that spaceship you got for Christmas years ago. Well there's
a big one at Greenham Common.
The answer is not repeatable here but he ended by saying I'm on my way
to your landing strip - pick me up.
It was true and it made the local paper before Lucasfilm could do
anything about it.
This Abrams guy really understood what people wanted.
Considering how unwell Carrie Fisher is she gave a really good performance.
She gets my special "The show must go on" award.
Disney must be so pleased and if I know them they will keep the faith.
Rod
I have a mint copy with all the passwords if you need a copy of the
passwords let me know I am going to have to type them in because they
are printed on DARK brown paper with black text you cant scan it I tried
so let me know if any of ya need them...
Also it surprisingly has pretty good graphics for the first version of
Castlevaina or I think it is...