>From: "Jim Isbell, W5JAI" <jim.isbell at gmail.com>
>
>No, it doent keep them from finding them at the last minute, they are
>just not there to find. With 7 days to look, I dont think I miss very
>many because they are late to the party. If you are a dollar short
>and 6 hours late, tough luck. Do you think a real auction house would
>hold the bidding while someone ran from the parking lot to try to get
>in a bid at the last minute?
>
Hi
You seem to assume that we all have time to watch earlier
items. I find that I can just keep up with one or two
days ahead. Even so, I have to skip maybe 1 or 2 days a week.
Some how, you seem to think that people are just watching
for 7 days. Most are only looking one or two days ahead.
If it is an item that has already gone past my max, I
don't waste time on it. If it is still in my price range,
I'll bid on it. Usually the first bid is just a place holder
below what I expect to make as my final bid.
Dwight
Hi
I rarely bid on an item before the last day. This is
mostly because there are so many items that one
doesn't have time to stay more than a day or so
ahead. Also, some people seem to like to have shorter
time auctions. If I look to far ahead, I might miss
one of these quickies.
I usually do last minute bidding if I'm around a computer
but I also like to put in what I call a place holder bid.
People can then look at my previous bidding and deside
if they want to waste time bidding against me.
I get pissed when someone pulls an item early. It has
only happened a couple of times. One the really ticked me
was that someone had a mod-8 board populated with 1702A's.
I'd just placed my place holder bid and they pulled the
auction. What is worse is that I suspect that they later
pulled the EPROMs from the board to sell separately.
Now the program data that was in the EPROMs are surely
lost :(
Dwight
>
>Subject: Need help with a 11-23+ and a RX-02 , Repost
> From: g-wright <g-wright at worldnet.att.net>
> Date: Tue, 05 Jul 2005 13:28:44 -0400
> To: cctalk at classiccmp.org
>
>Hi,
>
>I'm trying to get one of my 11-23's going and finally
>got around to setting up a TU58 emulator. got it
>to boot RT-11 and now trying to get a RX-02 working.
>
>I have 3 controllers and 3 sets of RX-02's. All do the same
>thing. The just seems to not be able to find track 1 or Home
>or ??? The heads just keep going from home to maybe the
>first tack and back. The heads do load and the system tries
>quit a few times then pauses and tries again. It then errors
>on drive failure or read error directory not found, size
>function failed depends what I ask it to do. I have tried all
>of the boards and drives. all or them seem to do the same
> thing. I do not know how good the drives are but can't
> believe there all bad.
>
>I have recheck the switches in the RX-02 and the Jumpers on
>the cards. Cleaned the drives. tried different disks.
>
>Is there some kind of compatibility issue that i do not know
>about. Or do I have 6 dead drives.
>
>The system is a Micro PDP 11, 8 slot Rack mount, with
>1 M8189 11-23+
>1 M8067 KB 256k Memory
>1 M8639 YA MFM rx50 controller
>1 M8029 RX-02 controller
>- in this order.
>
>Everything else seems to work. I added the floppy card
>but the rest is original.
>
>
>Thanks, Jerry
>
>Jerry Wright
>JLC inc
>
Either you blew the interrupt grant chain (the 8639 should be last!)
or you didn't put a bootable system on the disks.
The boot behavour suggests that the boot track is bare or worse.
You should have done a copy/boot to get the system bootable off floppy.
since you can boot RT via TU58 you should make sure you have the DY
device loaded and do a DUP /bad DY0:. A tu58 system (or emulator)
is big enough to carry all the needed devices and drivers.
As far as compatability, I've used RX02 with every Qbus I have
successfully.
Allison
See Mike's link for an explanation...
http://www.msclub.ce.cctpu.edu.ru/bibl/PCB/ch23.htm#Heading18
Cheers,
Ram
> -----Original Message-----
> From: Jules Richardson [mailto:julesrichardsonuk at yahoo.co.uk]
> Sent: Tuesday, July 05, 2005 4:58 PM
> To: cctalk at classiccmp.org
> Subject: Re: IBM AT Drive Types
>
> Home come entry 15 was reserved? (and why pick 15?)
>
> cheers
>
> J.
>
Hi
Has anyone mentioned measuring the voltages on the control
pins. It would be good to know if it was the controls
or the drive.
Dwight
>From: "Ethan Dicks" <ethan.dicks at gmail.com>
>
>On 7/1/05, Teo Zenios <teoz at neo.rr.com> wrote:
>> Jumper 301 is still in the open position (for a single drive).
>
>Perfect.
>
>> The two 8520's looked ok (nothing shorting pins together or stuff like that,
>> no signs of overheating). I swapped the 2 chips around and still have the
>> same result (external Df2: works while the internal DF0: is dead).
>
>OK... swapping the 8520s and watching the symptoms was a pretty
>standard method back in the day - it's easy and it works, so that
>_probably_ shows your 8520s are OK.
>
>> I checked the floppy cable and didn't see anything out of the ordinary
>> (except a pin in what looks like position 2 of the cable but I think that is
>> a key, since the motherboard does not look like it has a broken pin on it).
>
>That _is_ a key (and needs to be in any Amiga hardware FAQ - I can't
>remember how many times we had to tell people that in our Amiga club -
>every novice who added an internal floppy use to call us up and ask
>how to "replace a broken pin"... they thought that the
>pin had become stuck, and they must have pulled it out when they
>messed with the cable.
>
>> At this point I think it either the floppy cable has a bad line, or the
>> drive is just dead. Since the amiga cable does not look like a standard
>> floppy cable I think I will try setting the drive for Df1: and shorting
>> Jumper 301 to see if its recognized at all.
>
>
>> I did some research and quite a few older DD 3.5" PC drives can be jumpered
>> to Amiga mode (ofcourse I don't have any on the list).
>
>And they support the /DISK-EXCHANGE signal (p 34?) That was what
>always hosed frugal early-adopters of the Amiga - they'd try to use a
>cheap floppy, and the OS wouldn't be able to step the drive in and out
>one track to get the drive to assert the /DISK-EXCHAGE (or whichever
>one it was) so that the drive could 'tell' the OS that the diskette
>that used to be there isn't there any more.
>
>You _can_ hook up a floppy drive that won't assert that signal, but
>that places a burden on the user's head to have to type an AmigaDOS
>command to flush the previous diskette's particulars and to cache the
>new diskette.
>
>-ethan
>
>
Hi Chris,
I was able to get the drivers from SBS. They have the manuals, etc online
and anyone can download them. Better than other companies where it is a
pain to get them. Since I am quite a newbie when it comes to VME, I am not
sure if I installed everything correctly. I got the chassis hooked up and
everything and the showrevs utility does seem to pick up both the PCI and
VMEBus cards. I really want to get this working under Linux, but I want the
windows version up and running first. Here is what I have so far:
1) A VME Chassis with the SBS board connected to slot #0 (System controller)
2) Several transputer VME slave boards on the other slots. I want just the
1st transputer board to be recognized by the VME bus while the others are
there just for power and J2 connections.
3) The drivers I have for the transputer boards are UNIX source files which
I need to convert over to Windows XP/SBS style. I could surely use some
help here (any software that illustrates how to communicate when be
helpful).
4) There seems to be terminators? on both the J1 and J2 on slot #0. What
are they used for? Should I remove them? They are on the back of the VME
Chassis.
5) This is a VERO chassis (if that has any relevance).
Thanks a lot,
Ram
This chassis once held a FORCE SPARC VME controller. It has long since been
removed
by the previous owner. Hence, those terminators are probably from that
board....
Thanks,
Ram
> -----Original Message-----
> From: Ram Meenakshisundaram [mailto:RMeenaks at OLF.COM]
> Sent: Tuesday, July 05, 2005 1:28 PM
> To: General Discussion: On-Topic Posts Only
> Cc: cfandt at netsync.net
> Subject: RE: Help setting up a SBS/Bit3 PCI-to-VMEBus cards
>
>
> Hi Chris,
>
> I was able to get the drivers from SBS. They have the
> manuals, etc online and anyone can download them. Better
> than other companies where it is a pain to get them. Since I
> am quite a newbie when it comes to VME, I am not sure if I
> installed everything correctly. I got the chassis hooked up
> and everything and the showrevs utility does seem to pick up
> both the PCI and VMEBus cards. I really want to get this
> working under Linux, but I want the windows version up and
> running first. Here is what I have so far:
>
> 1) A VME Chassis with the SBS board connected to slot #0
> (System controller)
>
> 2) Several transputer VME slave boards on the other slots. I
> want just the 1st transputer board to be recognized by the
> VME bus while the others are there just for power and J2
> connections.
>
> 3) The drivers I have for the transputer boards are UNIX
> source files which I need to convert over to Windows XP/SBS
> style. I could surely use some help here (any software that
> illustrates how to communicate when be helpful).
>
> 4) There seems to be terminators? on both the J1 and J2 on
> slot #0. What are they used for? Should I remove them?
> They are on the back of the VME Chassis.
>
> 5) This is a VERO chassis (if that has any relevance).
>
> Thanks a lot,
>
>
> Ram
>
Hi,
Does anyone know how to set these boards up? I have a SBS 616 PCI adapter
and its corresponding VMEBus adapter. I also have a VME Chassis and I want
to install some transputer boards on the chassis and access it via Windows.
Anyone have experience in using these???
Thanks,
Ram
> $50k for an S/360 does seem too high, though
Time to start looking..
I know a couple of people who would pay that for a 360/50 system, if
one could be found.
Most were chopped up when the price of gold was high in the '70s.