George wrote: I totally do not get your point.
Sorry if I was not clear on that.
I did my homework on the seller, the seller?s feedback,
the types of items the seller deals in, the sellers other
open auctions, and so forth, before I placed a bid.
It all seemed to be quite consistent.
The impression I was left with was that the seller
(or an employee) messed up, and eBay or their policies
helped to ?Fix it?.
Don?t get me wrong here. I don?t have a problem with an
auction being canceled if it was listed in error, nor do
I have a problem with hijacked accounts being returned
to the rightful owner. But I don?t think the latter is
what happened here.
I think that eBay may be trying too hard to accommodate
sellers. (Could it be that the more money that changes
hands the more money eBay makes?)
Thanks,
Mike Gemeny.
eBay wrote:
"As the internet evolves, eBay continues to strike a balance between preserving transparency and
protecting our Community of members. eBay has decided to change how bid history information is
displayed so bad guys cannot target bidders with fake offers using this information. In certain
cases, some bidders will no longer be able to view Bidder User IDs on the Bid History page. Your
User ID will be shown only to you and the seller of the item you're bidding on. Other members will
see an anonymous name, such as Bidder 1, applied consistently to the Bid History page."
Al replied:
"So now, you can't see who you're bidding against.
Frickin' wonderful."
Yea, that would make it a lot easier for a seller to bid against their own buyers, now wouldn't it?
Yes, eBay will argue that sellers bidding on their own items is a violation of their
"Acceptable use policy", but then again "target bidders with fake offers" would also
likely be a violation of the policy and they don't seem to be able to do anything
about that, do they?
On Jan 11 '07 I had placed a bid as the only bidder on an item with no reserve. eBay later
told me that:
"We're writing to let you know that eBay has ended the following item you were bidding on
because the item appears to have been listed without the account holder's permission: ...
We are now working to restore the account to its original owner as soon as possible.
For privacy reasons, we can't share any further details regarding this member's account. ...
As eBay removed the item, you are not obliged to send payment for it. Please don't send money
or respond to any further emails regarding this listing. ..."
Now we see who they are really trying to protect, don't we?
Mike Gemeny.
On the other hand, I have restrained myself from bidding against
people I know unless the item was very rare.
I guess I won't be able to do that any more.
This latest BS only applies to bidding over $200.00 ... or at least that is what
they are saying. Personally, I would still *really* like to see a link on
ClassicCmp.org to VCM as I think that might increase the traffic there. If I
don't know the bidder on classic computer type stuff, I will generally make them
aware of the site. Ebay has a lot of weaknesses, but so far, nobody has been
able to successfully exploit them.
> From: Al Kossow <aek at bitsavers.org>
> "As the internet evolves, eBay continues to strike a balance between preserving transparency and
> protecting our Community of members. eBay has decided to change how bid history information is
> displayed so bad guys cannot target bidders with fake offers using this information. In certain
> cases, some bidders will no longer be able to view Bidder User IDs on the Bid History page. Your
> User ID will be shown only to you and the seller of the item you're bidding on. Other members will
> see an anonymous name, such as Bidder 1, applied consistently to the Bid History page."
>
> --
>
> So now, you can't see who you're bidding against.
> Frickin' wonderful.
"As the internet evolves, eBay continues to strike a balance between preserving transparency and
protecting our Community of members. eBay has decided to change how bid history information is
displayed so bad guys cannot target bidders with fake offers using this information. In certain
cases, some bidders will no longer be able to view Bidder User IDs on the Bid History page. Your
User ID will be shown only to you and the seller of the item you're bidding on. Other members will
see an anonymous name, such as Bidder 1, applied consistently to the Bid History page."
--
So now, you can't see who you're bidding against.
Frickin' wonderful.
> What follows is a ten-point plan outlining the primary issues of digital archaeology
...
> I love it when someone publishes an article without doing any proper
> research.
His total lack of knowledge of the subject was obvious by what he thought
the 10 primary issues were. He seems ignorant of the serious problem of verifying
that a program was copied in its original form (as opposed to have been hacked, or
with viruses) or the need for EVERY archival container to have something like an
MD5 sum to detect corruption in the future.
One of the problems I have as a CHM curator is trying to decide how much of the
on line stuff that is out there from the pre-PC time period to snapshot (there's a
LOT!).
As someone else mentioned, the monoculture and proprietary systems are the real
preservation problems, mid 80's or so and beyond. The best I've been able to come
up with is to try to save as many SDKs as I can find, which at least gives some
level of detail on how they worked.
-------------- Original message ----------------------
From: "Jay West" <jwest at classiccmp.org>
> In a prior life I owned a company that was a Pick dealer (Pick Systems,
> Microdata, GA, Ultimate, etc.), so all kinds of interesting Pick-related
> stuff still floats around the house and I rediscover things from time to
> time. Today one has surfaced that I thought was lost forever. My father sold
> his business recently and in cleaning out things he found a QIC cartridge
> tape I had left there for safekeeping as an off-site backup many years ago.
>
> It's a GA (General Automation) Zebra Pick OS Dealer Sysgen tape. This is a
> tape that was only provided to GA dealers (for dealers to replace an
> end-users lost or damaged boot tapes, or to sell with new systems {the
> licensing was in the terminal ports, not the OS}). It was an Account-Save
> format tape of an account called DEALER-SYSGEN. On that account was stored
> the monitor and ABS sections for every different system GA made. A menu ran
> when you logged on to the account and it asked you what system you wanted to
> make an OS load tape for (1700, 1750, 2820, 3820, 3000, 3500, 5500, 7820,
> 8830, etc.), and what tape media you want the tape created on (QIC or 1/2
> mag tape). It then wrote a complete bootable tape with bootstrap, monitor,
> abs, and files sections for any of those systems. What a find!!! Of course,
> I haven't tried to read this tape, perhaps it's got some worthless datafile
> backup from something else on it. But it still has the original GA Zebra
> lable stating it's the dealer sysgen tape and the write protect is on.... so
> I'm hopeful.
>
> I happen to have a GA1750 and a GA2820 in my collection, so I'm thrilled to
> know that I can make new boot tapes for them now. More importantly, I can
> make boot tapes for any other GA Zebra system. Note that this tape is for
> rev 3.8, which was the last non-R91 Pick GA produced (I wasn't a fan of R91,
> so I'm really glad it's the pinnacle of the 3.8 train). I need to see if I
> can find my manual patch sheets that bring it up to 3.8T1.
>
> Anyways, if anyone has GA Zebra's in their collection and needs a new boot
> tape I can help you out. Now I just need to find the DEALER.ASSY account for
> 3.8 :)
>
> Jay West
>
>
>
>
Hi Jay
My Zebra says 2510 on the botton sticker if I remember correctly
has a 8" drive and a Qic Tape. Still Boots pick OS. I have
the same tape you have but did not know how to to use it.
My machine model did not show up on the label of the tape either.
Jerry
Jerry Wright
JLC inc.
g-wright at att.net
I am trying to identify 3 Motorola chips. I searched on the 'net, but
I didn't come up with anything.
The markings are
SCM10071L
SCM10072L
SCM10073L
The chips were produced in mid 1973 and early 1974. All three chips
are ceramic and have 28 pins.
Thanks for any information you can supply.
--barry
I have a old VAXstation 3100/76 I'm playing around with (it's
surprising how much faster the VAX 4000/200 "seems" - guess it's better
memory and I/O bandwidth). The beastie is not-quite-complete (running
it as a VAXserver, and the external SCSI connector has been replaced
with a HD-50 that isn't functional- not sure if that's bad wiring or
bad SCSI chip), but it does have a full 32MB RAM and all the tests it
fails are explainable (?? on the network (since it's not connected,
that's expected), ? on the serial lines (no kb/mouse connected there)
and the external SCSI (nothing connected and known issues).
Anyway-to the question: Neither NetBSD 2.0 or 3.0 will install
successfully. They both segfault, usually during install but once I got
3.0 installed and it was very limited functionality. Officially the
3176 is supported, but is NetBSD known to be tempermental? (I'm not
sure if it's the VAX or the software - VMS boots fine, but if the
system's wonky I won't bother with it anymore).
Can't test NetBSD on my other VAX (4000-200), since SHAC isn't
supported.
I found the manual for CMD 220 on bitsavers... along with a txt file
for the 220A/TM (which is what I have).
Couple of things:
1. Does anyone have the full manual digitized (or a hard copy you don't want
anymore) that covers the 220A (to be exact, CQD-BV220A/TM) ?
2. In the txt file, it has (formatting neatend... (for fixed point font
anyway)):
W1 OUT Reserved (F)
W2 IN SCSI terminator power enabled (F)
W3 OUT Reserved (F)
W4 1-2 IN Eprom Size 512-Kbit or 1-Mbit (F)
W5 OUT 0 Wait State for Eprom Cycles (F)
W6-1 OUT Adaptive DMA enabled (F)
W6-2 OUT Adaptive DMA Dwell Time enabled (F)
W6-4 W6-5
IN IN 0.8-ms DMA dwell time
OUT IN 1.6-ms DMA dwell time
IN OUT 3.2-ms DMA dwell time
OUT OUT 6.4-ms DMA dwell time
W6-5 OUT Block mode DMA enabled (F)
W6-6 W6-7 Auto-Boot for LSI-11 systems without Boot Roms
OUT IN Auto-Bootstrap address = 773000
IN IN Auto-Bootstrap address = 771000
OUT OUT Auto-Bootstrap disabled (F)
IN OUT Auto-Bootstrap address = 775000
W6-8 IN Reserved (F)
The W6-4, W6-5 pair I believe should be labelled W6-3, W6-4, as
W6-5 is documented twice ... and W6-3 is not documented.
Anyone know if my belief/assumption is correct ?
Anyone know what DMA dwell time should be used in a PDP11/83 ?
Should this board be closest to the CPU, or furthest in a an 11/83 ?
Thanks in advance,
-- Curt
> Adrian wrote
> On Sun, Jan 14, 2007 at 01:12:11AM -0000, arcarlini at iee.org wrote:
>>
>> The wiring inside the VAXstation 3100-76 may well be "non-standard",
>> but the external connector works perfectly well with any SCSI
>> cable which physically connects.
>
> I'm a bit confused. I've got an M76 which I'd love to install a later
> version of VMS on (it's currently on 5.5), but everything I've read
> has said
> that the external SCSI connector is DEC-specific and needs a DEC BC09J
> cable
> to attach normal SCSI devices to (a cable which I've not yet found at a
> reasonable price). Is this not the case?
The connector is proprietary to DEC (same one as used in the
DECstations), but the SCSI that comes out of it is standard. Since that
particular connector hasn't been picked up by anyone else (in that
particular sex)- yes, any SCSI cable that physically connects will
work.
On mine I just pull the lid and connect up whatever I need to the
internal bus, although I do have an InfoServer... hmm, possibilities
that don't require a screwdriver.
This is a little ISA card (made in USA!) with a separate 34-pin
header for a 2.88MB floppy drive. There's a sticker marked "1133-11-
04-9 Model 11". There's a row of jumpers labeled 'B1 B2 B3 B4 PR
SE".
Anyone got the jumper settings for this thing? I think that
PR=primary and SE=secondary and that B1-B4 may be drive types, but
confirmation might save some work.
Thanks,
Chuck
While the drive is not strictly on-topic, the contents are - I have a
30GB Quantum drive that did not survive the rigors of the APO mail
system. I have to admit I was in a bit of a hurry on my way out of
Pole and while virtually all of my stuff survived travelling 12,000
miles in the mail system, something must have shifted in my box of
hard drives and some of the components on the bottom of the drive are
damaged and missing. Sufficient packing materials are hard to come by
at the Pole, and I was counting on double-boxing and pink bubble wrap
to be enough - it obviously wasn't. I think a neighboring drive must
have shifted and rubbed on the circuit board of this one, causing a
patch of visible component damage.
The drive itself does spin up, and gives the expected pattern of
blinks on its lone LED, but the machine does not see it. Given that
there are 3 missing resistors of a size smaller than an 805 package
(don't know the names of the really wee parts) and a few bent pins on
a nearby 104(?) pin 0.5mm pitch QFP, the lack of responsiveness
doesn't really surprise me.
If anyone on the list happens to have an unhappy 30GB Quantum drive,
I'd be interested in its board. The P/N on the lid sticker is an
LM30A011.
Worst case, if I can find another similar drive and a scan of the area
of the board near the LED on an intact drive of the same model, I can
probably harvest a replacement chip and some SMT resistors and
transplant them. The damaged chip in question is badged
Lucent/Quantum, P/N "MS24C13 34".
There's no horrible noises from the HDA - typical spin-up/spin-down
noises, so I think there may be a chance to get at this drive, if I
can repair/replace the board. Yes, I know that drives are cheap these
days - I would just like to get at what's on this one.
Naturally, the other drives in the box, including the blank 18GB
workstation drives, are fine... only my boot drive gets dinged. :-/
Thanks,
-ethan
http://www.issue.org.uk/
Loads and loads and loads of V9K stuph. You'll be like
a kid w/a Vic9K in a candy store.
be sure and read the "personal note".
____________________________________________________________________________________
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains.
http://farechase.yahoo.com/promo-generic-14795097
> I've seen mention of a Hardware Technical Reference for the Victor.
> If anyone has a copy I'd be interested in hearing from you.
I've just uploaded scans of the Tech Ref and several other tech docs
to http://bitsavers.org/pdf/victor/victor9000
I have the Heathkit H77 case where the pieces that hold the front panel to the
chassic got broken off. With JB Weld to the rescue, I went ahead and fixed it
only to find out a "small" problem. It seems that the label on the front of the
case covers the screw holes and I *really* don't want to poke holes in it as it
is in excellent condition. Has anyone tried to remove that front label, and if
so how?
My first thought was to take a heat gun and warm up the adhesive to the point
where the label might come off without damage. My second thought was to ask here
:).
On 15 Jan, 2007, at 18:00, cctalk-request at classiccmp.org wrote:
>
> Message: 1
> Date: Sun, 14 Jan 2007 10:58:12 -0800
> From: "Chuck Guzis" <cclist at sydex.com>
> Subject: Re: Olivetti M20
> To: "General Discussion: On-Topic and Off-Topic Posts"
> <cctalk at classiccmp.org>
> Message-ID: <45AA0CC4.14431.CE01A94 at cclist.sydex.com>
> Content-Type: text/plain; charset=US-ASCII
>
> On 14 Jan 2007 at 16:17, Roger Holmes wrote:
>
>> Can anyone please tell me if the Olivetti M20 used a Z8010 memory
>> management unit?
>
> What would have been the point on a system that can accommodate at
> most, 512K?
1) To prevent one process overwriting the memory belonging to another
process.
Segments did not HAVE to be 64k, that was their maximum size, the
minimum
was 128 bytes.
2) To provide virtual memory.
3) To protect the executive from processes.
4) To allow non contiguous physical address space to appear as a
logical contiguous address space
5) To provide mapping out of faulty blocks of memory
and probably as many reasons I have not thought of off the top of my
head.
Best regards,
Roger.
>
> Cheers,
> Chuck
On 15 Jan, 2007, at 18:00, cctalk-request at classiccmp.org wrote:
>> Can anyone please tell me if the Olivetti M20 used a Z8010 memory
>> management unit?
> ---snip---
>
> Hi Roger
> No, it didn't use a 8010. It could have but I believe that when
> the project was started, the 8010 wasn't ready yet.
> They used a ROM instead. They do a number of interesting
> logical to physical mapping but these could have been done
> with a 8010 just as easily ( and more flexibly ).
> Most of the mapping is to handle the holes that the video
> causes. Some is related to the dual mapped memory.
> Even with the full 512K of memory, I don't know of any
> application that needed more than 384K.
> Dwight
Many thanks Dwight.
A pity they did not at least use RAM instead of ROM.
Roger.