> Does anyone have Docs for the Documation punch card readers? I'd like to
> hook one up to a PDP 8/e or 11, but i'm concerned about finding or making
> the proper interface cable. I think the documation card readers used a
> strange (to me, at least) interface connector that i'm not sure is available
> anymore, plus I dont have the information necessary to create the cable.
IIRC (questionable), they used standart V.35-type connectors. But since
V.35 is generally a serial interface, and the reader would most likely
be parallel, dunno about the pinout...
How hard would it be to figure out which lines were input to the
card reader (there might be an 'enable' line or something like that)?
If it turns out there are no input lines to the reader, then all
lines coming out are output, and in the case of the fairly-recent
Documation readers, they should be TTL-level signals. Hook up a
bank of appropriately-wired LEDs to determine which line are
data and which is strobe.
Just a thought... -dq
> Doug:
>
> The earliest MSC I have is 7.0 which has the 3.1 SDK on
> it (separate disk and separate install program).
That's ok; newcomers are welcome, too!
;-)
I just came across at the local computer surplus four RL02K-DC disk packs.
Non of the shoch-watch indicators were triggered. They have a label about
8650 diagnostics on them.
Anybody need them?
Mike
mmcfadden(a)cmh.edu
> That's what I can come up with without looking. How far off am I?
>>Very good.
Does that mean very good or very bad?
Bad Rich...must study MSDOS Reference...bad Rich...
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Fred Cisin (XenoSoft) [mailto:cisin@xenosoft.com]
Sent: Friday, June 22, 2001 2:31 PM
To: 'classiccmp(a)classiccmp.org'
Subject: RE: MS-DOS version (was: What's best to do?? classically
speaking
On Fri, 22 Jun 2001, Cini, Richard wrote:
> DOS5 != DOS6 differences:
> SmartDrive disk cache
Doesn't count. It was a seperate product that came with Windoze 3.10 well
before 6.00 (and no choice whether to use it) Smartdrive caused MAJOR
problems, which the drive compression got blamed for.
> Boot menus
THAT was fun
> "Large disk" support in FDISK
IIRC, there were some changes in some of the partition types, but the 32M
ended with 3.30, everything 3.31 and on permitted large drives.
> Drive compression
Had a few problems, but MOST of the problems that it got blamed for were
actually the fault of SMARTDRV! It was a third party program (from
Vertisoft after the STAC deal fell through), but there were significant
mods to the OS itself to integrate it.
> That's what I can come up with without looking. How far off am I?
Very good.
There was also SETVER that let the OS lie about its age.
--
Grumpy Ol' Fred cisin(a)xenosoft.com
I just came across at the local computer surplus a DEC Rainbow 100+ in a
pile of computer equipment. I haven't dug down that far yet. I am also
looking for the monitor and keyboard..
Anybody want it? I already have one.
Mike
mmcfadden(a)cmh.edu
> It just occurred to me that it should be possible to write OCR software
> to read punchcards on your scanner. Not that I have any punchcards
> mind you, more of an intellectual exercise, but has anyone written
> such a thing?
Planning on it, as I think I know where there are some binary decks
containing bootstraps for some old RJE stations formerly used at
IU, and I'd like to preserve that software. I planned on scanning
the decks and then eventually writing such a utility or findind
someone who already had.
> Also, if you're desperate for a punchcard reader I suspect you could
> make an acceptable one with Lego Mindstorms. You'd have to use
> one of the popular input multiplexing schemes, and probably program it
> in nqc or legos, but it should be possible. Using the RCX's motor
> controllers and a couple motors and tires you should even be able to make it
> automatic feed. In fact, come to think of it, you SHOULD be able to
> build the thing with... lessee. two motors, a couple tires, and the
> light sensor. 'course your software on the RCX would have to translate
> awhat amounts to the scan of a card into data, but if the sensor is
> precise enough to tell holes from chads, I can think of a couple ways to
> do this.
Dr. Anthony Schaeffer built one that appeared in either BYTE or Interface
Age back in the 70s using a block of wood and what looked like hairpins.
You pulled the cards through manually, one at a time.
-dq
Hello,
I have the following problem. I want to open lif-files (created by my hp 3360 analysator) on my pc operating with Linux and WinNT, but this is impossible, it doesen?t work.I have no idea how to handle it.I?m looking for any information, documentations and codes/programmes refering to this problem which may help me.
Is it possible to solve my problem with RMB?
Please, would you be so kind (only if possible) and give me some advice, where I can get these information/how to handle ist?
Please send any information to my E-Mail Address: FlyingMadman(a)web.de
Thank you very much!
Robert
______________________________________________________________________________
Sie surfen im Internet statt im Meer? Selbst schuld!
Auf zum Strand: http://lastminute.de/?PP=1-0-100-105-1
I second the motion.
There have been examples recently where major libraries have microfilmed old
newspapers, then gotten rid of the originals. Researchers subsequently found
that much information had been lost due to such factors as the copies being
in B/W while the originals had color, the copies were of poor quality, and
the copies were only of the last edition of the day, where news/quotes that
had appeared in earlier editions was no longer included (presumably due to
pressure from the news subject).
For just two examples, see:
http://www.guardian.co.uk/uk_news/story/0,3604,402222,00.htmlhttp://reveille
.stumedia.lsu.edu/archives/november-2000/11-7-00/viewpoints/Richard.html
-----Original Message-----
From: Sellam Ismail [mailto:foo@siconic.com]
Sent: Friday, June 22, 2001 9:48 AM
To: classiccmp(a)classiccmp.org
Subject: Re: preserving / ressurecting old docs?
<snip>
I completely recommend AGAINST destroying the original. Not only is it in
some cases a historical artifact on its own, if the digital copy were ever
to be lost then you're SOL.
Sellam Ismail Vintage Computer
Festival
----------------------------------------------------------------------------
--
International Man of Intrigue and Danger
http://www.vintage.org
> Does anyone know where to find a punched card reader
> these days? I'm looking for a small desktop unit that
> I could interface to a PC.
I would be thinking that a sh*tload of them will be
available in Florida soon, as they have clearly
outlived their political acceptableness.
If any Floridian listers get a line on these (mostly
Documation readers, possibly various models) when
they become available, I'd like to try to get one,
particularly if Pr1me-color-schemed units are among
them.
-dq
> Does anyone know where to find a punched card reader
> these days? I'm looking for a small desktop unit that
> I could interface to a PC.
In the 1976-1978 timeframe my high school leased a desktop reader made
by H-P which would read either mark-sense or punched cards, and output
serial data. It was hooked up in tandem with an ASR33 Teletype for
access to a TOPS-10 timesharing system (BOCES NCODE on Long Island).
It made a goose like "honk" each time it read a card.
I've got some 8" disks that are apparently double density (the
manufacturer label says so). I thought they were Intel ISIS formatted
disks (which Eric Smith said would make them M2FM and uncompatible with
anything other than an Intel MDS development machine) but I'm not so sure,
since I can't seem to access any on the two Intel MDS systems I have set
up.
Both machines have Shugart 801 drives in them, and after doing some web
research, I've come to find out they are single-density only. This would
probably explain why I am not able to access these disks on these
machines.
The disks I am trying to access are supposedly CP/M, but the labelling
indicates they were perhaps used on an Intel development system (they have
filenames on the label with ".HEX" file types; this may not mean
anything). If this is the case, and they were formatted on an Intel MDS
(and therefore M2FM), and since they are double-density, then I may not be
able to read them with the machines I have.
However, I want to check their format on some CP/M machine and see if
perhaps I can read them. If so, then they are probably more standard DD
formatted diskettes, maybe even CP/M since that is what I was told they
are.
If they are in a standard DD format, and I have a computer that can boot a
DD CP/M system master, could I then pop these disks in the drive and do a
DIR to see if I get a directory?
For those who've used these before: when I put any of the disks in
question in the drive, the drive seems to seek for a few seconds, then
goes off for a split second, back on again for half a second, then off
(and the system crashes). The normal boot sequence for a (single density)
system disk is, upon reboot the disk seeks for a few seconds, then stops
for a split second, then starts seeking/reading for a few more seconds and
the ISIS prompt comes up.
It seems the system is trying to read the double density disks and just
not seeing anything intelligible and crashes. With single density
non-system diskettes, the machines will come up with something like "NOT A
SYSTEM DISK".
Suggestions appreciated.
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
Edwin:
Well, Win104 did not have DLLs, but it did have *.DRV drivers. The
balance of Windows was implemented as an overlay file (win100.bin) which has
a standard NE-style format. So, conventional Windows spleunking tools work.
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Edwin P. Groot [mailto:epgroot@ucdavis.edu]
Sent: Thursday, June 21, 2001 9:00 PM
To: classiccmp(a)classiccmp.org
Subject: Re: SDK for Windows 1.04??
George,
I don't think Windows 1.04 had DLLs! It ran in real mode and used
simple .EXE files as programs and nothing else.
Edwin
At 03:26 PM 6/21/2001 -0500, you wrote:
>Two different concepts. The DOS tech refs are refering to the values to
place in ah (I think, or was it al?) before making a DOS or BIOS int call.
This is all pre-DLL days. Richard is referring to
>the ordinal number within a DLL to reference a specific function located
in the DLL. Not all functions in a dll have their names exported and
sometimes the only way to get to them is by ordinal
>number. This is one way that M$ creates 'value added' to their software
by utilizing these undocumented calls.
>
>George
>
>On Thu, 21 Jun 2001 13:42:53 -0400, John Allain wrote:
>
>>From: Cini, Richard <RCini(a)congressfinancial.com>
>>
>>> most of the functions in the DOS Shell code (MSDOS.exe
>>> and MSDOSD.exe) are referenced by ordinal number
>>
>>Early (most?) DOS techinical reference
>>manuals listed function calls by numbers,
>>E.G. 10H = Close file. 01H = Keyboard input, etc.
>>Could this be it?
>>
>>John A.
Fred:
I've used sourcer for many years in other spleunking projects. Below
is some heavily snipped output from Windows Sourcer (this is the code
reached from the NE header of MSDOS.EXE):
;??????????????????????????????????????????????????????????????????????????
; MSDOS_10
;??????????????????????????????????????????????????????????????????????????
; Note: Subroutine does not return to instruction after call
1.0000 MSDOS_10 proc far
1.0000 mov si,364h
1.0003 loc_0003:: ; xref
1.0021
1.0003 ? xor ax,ax ; Zero
register
1.0005 push ds
1.0006 push si
1.0007 push ax
1.0008 push ax
1.0009 push ax
1.000A call far ptr GetMessage
1.000F or ax,ax ; Zero ?
1.0011 jz short loc_0004 ; Jump if
zero
1.0013 push ds
1.0014 push si
1.0015 call far ptr TranslateMessage
1.001A push ds
1.001B push si
1.001C call far ptr DispatchMessage
1.0021 jmp short loc_0003 ; (0003)
1.0023 loc_0004:: ; xref
1.0011
1.0023 mov ah,4Ch
1.0025 int 21h ; DOS
Services ah=function 4Ch
; terminate
with al=return code
MSDOS_10 endp
;??????????????????????????????????????????????????????????????????????????
; SESSIONWNDPROC
;??????????????????????????????????????????????????????????????????????????
1.0027 SESSIONWNDPROC proc far
PARAMETER_1 = 6 ; bp+6
PARAMETER_2 = 8 ; bp+8
PARAMETER_3 = 0Ah ; bp+0Ah
PARAMETER_4 = 0Ch ; bp+0Ch
PARAMETER_5 = 0Eh ; bp+0Eh
LOCAL_2 = -4 ; bp+0FFFCh
LOCAL_1 = -2 ; bp+0FFFEh
{snippage}
You can see that the first two routines contained in MSDOS are
exported differently. The first one is MSDOS_10, the second is
SESSIONWNDPROC. If you look at the NE header, MSDOS.EXE only exports window
procedures by name. Everything else is by ordinal. MSDOS_10 above is clearly
the WinMain (the main message loop--notice the calls to GetMessage,
TranslateMessage and DispatchMessage). SESSIONWINDPROC is the main windows
procedure.
The MSDOSD.EXE file really only includes the equivalent code for
FORMAT and SYS.
I just thought that the Win104 SDK would have some helpful
information in it that may aid in renaming these MSDOS_XX calls.
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Fred Cisin (XenoSoft) [mailto:cisin@xenosoft.com]
Sent: Thursday, June 21, 2001 9:38 PM
To: 'ClassCompList'
Subject: Re: SDK for Windows 1.04??
On Wed, 20 Jun 2001, Cini, Richard wrote:
> Hello, all:
> I was paging through some Sourcer listings that I have of the
> Windows 1.04 code and noticed that most of the functions in the DOS Shell
> code (MSDOS.exe and MSDOSD.exe) are referenced by ordinal number and not
> function name ("MSDOS_23" versus "DoSomeThing"). So, I was wondering if
> anyone had a copy or knows the existence of SDK documentation for Windows
1.
"Sourcer listings" are disassemblies.
You don't want, or need Win SDK for THIS (plenty of use for it for other
stuff!)
What you need is a copy of the DOS Technical Reference, or ANY of the
after-market programmer's references, that will provide you a list of the
MS-DOS (aka INT 21h) functions, so that you can substitute
"DoSomething" in lieu of function "23".
Note: the DOS Technical Reference consists of what used to be the
appendices of the DOS manual in version 2.00 and below. In version 2.10,
they did an appendectomy.
BTW, Norton refers to the functions by DECIMAL numbers, whereas the entire
civilized world always refers to them in hexadecimal. For example,
function 30h of INT 21h reports DOS version, (as opposed to function 48 of
int 33 in Norton-speak)
--
Grumpy Ol' Fred cisin(a)xenosoft.com
Fred:
I'm using the Windows Sourcer program from V Communications. WinSrc
has the ability to generate an import library from any Windows program by
scanning the "exported functions" portion of the file header. So, running
this on kernel.dll would produce a listing of the exported function names.
Some functions are not exported by name, but by ordinal number only. These
are referenced in module.ordinal format (such as "kernel.34"). So,
subroutines disassembled by Sourcer are labeled with their real name
("GlobalLock") or if the name is not available, the ordinal ("KERNEL_34").
This utility works on any Windows program using the NE, P3, LE, or
PE type headers.
My whole point was that the 1.04 SDK would probably give me some
clues as to what the MSDOS_XX functions are since very few are exported by
name. Windows programs were not supposed to call down into MSDOS.EXE or
MSDOSD.EXE (the rough equivalent to win386.exe or vmm.vxd in current
versions), Microsoft exported most functions by ordinal.
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Fred Cisin (XenoSoft) [mailto:cisin@xenosoft.com]
Sent: Thursday, June 21, 2001 11:06 PM
To: classiccmp(a)classiccmp.org
Subject: Re: SDK for Windows 1.04??
On Thu, 21 Jun 2001, George Currie wrote:
> Two different concepts. The DOS tech refs are refering to the values
> to place in ah (I think, or was it al?) before making a DOS or BIOS
> int call. This is all pre-DLL days. Richard is referring to the
> ordinal number within a DLL to reference a specific function located
> in the DLL.
He is referring to the number reported by his disassembler that is
disassembling the Windoze program (into DOS compatible assembly language).
The value placed in AH IS for the purpose of referencing a specific
dunction located in the MS-DOS DOS function handler (INT 21h).
> Not all functions in a dll have their names exported and
> sometimes the only way to get to them is by ordinal number. This is
> one way that M$ creates 'value added' to their software by utilizing
> these undocumented calls.
And there were/are a few undocumented functions in MS-DOS, such as #34h,
and INT 28. And don't forget the "network redirector" (since 3.10) that
is needed even to use MS's CDROM drivers.
--
Fred Cisin cisin(a)xenosoft.com
XenoSoft http://www.xenosoft.com
PO Box 1236 (510) 558-9366
Berkeley, CA 94701-1236
Doug:
The earliest MSC I have is 7.0 which has the 3.1 SDK on it (separate
disk and separate install program).
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Douglas Quebbeman [mailto:dhquebbeman@theestopinalgroup.com]
Sent: Thursday, June 21, 2001 5:13 PM
To: 'classiccmp(a)classiccmp.org'
Subject: RE: SDK for Windows 1.04??
> Hello, all:
>
> I was paging through some Sourcer listings that I have of the
> Windows 1.04 code and noticed that most of the functions in the DOS Shell
> code (MSDOS.exe and MSDOSD.exe) are referenced by ordinal number and not
> function name ("MSDOS_23" versus "DoSomeThing"). So, I was wondering if
> anyone had a copy or knows the existence of SDK documentation for Windows
1.
I think the Windows 1 SDK was bundled with some versions of the
Microsoft C Compiler v 4.0.... or I guess, it would have been
the compiler bundled with the SDK.
In the late 80s, lots of people were buying the SDKs and then stripping
out the compiler packages and selling them. I bought MS C 5.0 that way
>from someone who'd bought a Microsoft OS/2 SDK. I was able to send a
copy of a letter from the seller to Microsoft, who registered me as
a valid licensee! However, they stopped that practice shortly there-
after.
Regards,
-dq
At 07:32 PM 6/21/01 -0700, Fred wrote:
>
>For years I have used noise-cancellation headphones at COMDEX.
>The slowness of the speed of sound limits the practicality of the
>technology to situations where you can have the added signal provided to
>the receiver (your ear) at the same place as the original sound (in the
>headphones). If you tried to produce a unit to silence the neighborhood,
>alas, the delay of the sound reaching the mike, added to the delay of the
>"anti-sound" getting back to the original source, would render it
>impossible to synch up adequately. Even if the mike were at the source,
>eliminating THAT delay, people at different locations would experience
>different phase combinations of the two signals. In fact, at 500
>feet away there would be almost a half a second of delay. Since you want
>either no time delta between the signals (if inverted), enough distance to
>give half the frequency of the sound would completely bollix it.
>
>In other words, you could diminish the sound for yourself, but not cancel
>out the noise level even a few feet away.
Yes, this is inhererent in every 1-dimensional, single driver approach to
sound cancellation. In the end, if you want to null out a source
for everyone, you need to surround it with drivers. Not practical.
But, with two drivers strategically placed apart, you can cancel
the source along one direction. Oh, and you need more than one
mike along every direction for the same reasons.
carlos.
--------------------------------------------------------------
Carlos E. Murillo-Sanchez carlos_murillo(a)nospammers.ieee.org
we fired up an old Rover (Buick) V8 a while ago on someone's driveway with
no exhaust manifolds on it - that really was pretty darn loud. Windows
rattled, and the people 4 doors down the street though a plane was crashing
on their heads :-)
the flames are pretty good, nice blue / orange jets out of the ports in the
heads. Cooked the engine bay pretty well though...
> ----------
> From: Mike Ford[SMTP:mikeford@socal.rr.com]
> Sent: 22 June 2001 09:23
> To: classiccmp(a)classiccmp.org
> Subject: Re: Boom cars (ot for sure...)
>
> >> common occurance that when I start my engine when parked next to an
> >> alarmed car, the alarm goes off. :-)
> >
> >
> >Yeh, those 3/4-race cams and headers have this tendancy to do that . . .
>
> One of my brothers old buddies had his exhaust rigged with a pair of 3"
> electric aircraft fuel valves. Switch up on the dash ran the exhaust thru
> a
> Caddie quiet set of mufflers, down and it went out about a foot behind
> the
> front wheels with no restriction of any kind. Not only rather loud, but
> shot flame a fair distance.
>
>
On Thu, 21 Jun 2001 20:12:06 -0700 Chuck McManis <cmcmanis(a)mcmanis.com>
writes:
> This is a True Story(tm) although it sounds like an urban legend
<Tale of Cellular Mayhem SNIPped>
Yeh, I seen that done. I work for a test equipment manufacturer,
and you can get a cellular test set to fake-out phones pretty
easily (if you have $20k to spend on a test set).
A retired cellular tranceiver (one designed to deliver a control
channel) is a good substitute.
OB Classic: If those tranceivers were the ones I'm familiar
with, they are controlled by a 6809 uP. They're
long, thin, heavy aluminum things with a handle and
audio jacks in the front . . . .
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
Gee, I'm so embarrassed asking this in public, but heck, I played
so little games in my life! Can someone tell me how to get over
those pits once you come down the hill with Quest for Tires? I
recently got an old C64 setup (I grew up with one) and thought
this was a fun game, I just don't see any way to get over those
pits.
Thanks,
-Gunther
No this is not off topic, becasue I just had that thought that
one should rename Lunix/LNG to "True64". After all, Tru64
isn't truly on the C64. The but the C64 has a Unix, so it should
be called True64.
cheers,
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
On Thu, 21 Jun 2001, George Currie wrote:
> Two different concepts. The DOS tech refs are refering to the values
> to place in ah (I think, or was it al?) before making a DOS or BIOS
> int call. This is all pre-DLL days. Richard is referring to the
> ordinal number within a DLL to reference a specific function located
> in the DLL.
He is referring to the number reported by his disassembler that is
disassembling the Windoze program (into DOS compatible assembly language).
The value placed in AH IS for the purpose of referencing a specific
dunction located in the MS-DOS DOS function handler (INT 21h).
> Not all functions in a dll have their names exported and
> sometimes the only way to get to them is by ordinal number. This is
> one way that M$ creates 'value added' to their software by utilizing
> these undocumented calls.
And there were/are a few undocumented functions in MS-DOS, such as #34h,
and INT 28. And don't forget the "network redirector" (since 3.10) that
is needed even to use MS's CDROM drivers.
--
Fred Cisin cisin(a)xenosoft.com
XenoSoft http://www.xenosoft.com
PO Box 1236 (510) 558-9366
Berkeley, CA 94701-1236
Hello, all:
I was paging through some Sourcer listings that I have of the
Windows 1.04 code and noticed that most of the functions in the DOS Shell
code (MSDOS.exe and MSDOSD.exe) are referenced by ordinal number and not
function name ("MSDOS_23" versus "DoSomeThing"). So, I was wondering if
anyone had a copy or knows the existence of SDK documentation for Windows 1.
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
George,
I don't think Windows 1.04 had DLLs! It ran in real mode and used
simple .EXE files as programs and nothing else.
Edwin
At 03:26 PM 6/21/2001 -0500, you wrote:
>Two different concepts. The DOS tech refs are refering to the values to
place in ah (I think, or was it al?) before making a DOS or BIOS int call.
This is all pre-DLL days. Richard is referring to
>the ordinal number within a DLL to reference a specific function located
in the DLL. Not all functions in a dll have their names exported and
sometimes the only way to get to them is by ordinal
>number. This is one way that M$ creates 'value added' to their software
by utilizing these undocumented calls.
>
>George
>
>On Thu, 21 Jun 2001 13:42:53 -0400, John Allain wrote:
>
>>From: Cini, Richard <RCini(a)congressfinancial.com>
>>
>>> most of the functions in the DOS Shell code (MSDOS.exe
>>> and MSDOSD.exe) are referenced by ordinal number
>>
>>Early (most?) DOS techinical reference
>>manuals listed function calls by numbers,
>>E.G. 10H = Close file. 01H = Keyboard input, etc.
>>Could this be it?
>>
>>John A.
A local (to D/FW) used place has some SGI Indy systems (with
monitor, keyboard, and mouse) for sale. Is there any interest
in these? They're asking $150 each. I don't know if that's
a good deal or not, and I don't know if they'll ship, but
if you're interested let me know and I'll email you the phone
number.
I'm not going to buy these and try to auction them. I don't
know what they are worth, I don't collect them, and I don't
want to buy them and try to ship them. I'll let you deal
with them yourself. If they won't ship, but you REALLY need
one, I may be convinced to help you. The box itself wouldn't
be hard to ship, but I hate shipping large monitors.
--
Eric Dittman
dittman(a)dittman.net
On June 21, Richard Erlacher wrote:
> Has anyone got a reliable recommendation on where one might obtain a replacment
> paper tray for the HP DeskJet 11200C printer. I'd like to know whether that
> tray is interchangeable with any other printer or plotter models, in the event
> anyone knows that.
I have a need for the same thing, Dick...if you manage to find one,
please let me know.
Thanks,
-Dave McGuire
At 08:30 AM 6/13/01 -0400, Douglas Quebbeman wrote:
>> Since most vintage machines can't run TCP/IP but CAN run uucp, would
>> there be any interest in a dialup uucp node for retrieving email, files, etc
>> specifically geared toward vintage machines?
>
>I've been thnking of this in a bit wider context.
>With some of the changes happening on the Internet, it's
>not quite as friendly as it used to be.
You can still use the regular Internet as your transport
and do away with the toll calls, can't you? A sledgehammer
approach would be a VPN.
- John
> This is one way that M$ creates 'value added' to their software by utilizing
> these undocumented calls.
And yet another example of why Microsoft's leverage of their OS dominance
is hardly a benign monopoly. >:-/
--
----------------------------- personal page: http://www.armory.com/~spectre/ --
Cameron Kaiser, Point Loma Nazarene University * ckaiser(a)stockholm.ptloma.edu
-- Kiss me twice -- I'm schizophrenic. ----------------------------------------
> Hello, all:
>
> I was paging through some Sourcer listings that I have of the
> Windows 1.04 code and noticed that most of the functions in the DOS Shell
> code (MSDOS.exe and MSDOSD.exe) are referenced by ordinal number and not
> function name ("MSDOS_23" versus "DoSomeThing"). So, I was wondering if
> anyone had a copy or knows the existence of SDK documentation for Windows 1.
I think the Windows 1 SDK was bundled with some versions of the
Microsoft C Compiler v 4.0.... or I guess, it would have been
the compiler bundled with the SDK.
In the late 80s, lots of people were buying the SDKs and then stripping
out the compiler packages and selling them. I bought MS C 5.0 that way
>from someone who'd bought a Microsoft OS/2 SDK. I was able to send a
copy of a letter from the seller to Microsoft, who registered me as
a valid licensee! However, they stopped that practice shortly there-
after.
Regards,
-dq
>>Likewise, as the folks in California will probably consider, the usage of
>>MORE electrical power should not be discounted. If you use what a small
>>household uses, you should get the minimal rate. If you use, 5x what the
>>typical small household uses, you should pay 5x what that household uses,
>>i.e. 5x the amount per kWH, and if you use 1000x kWH's, then you should
>>pay 1000x the amount, per kWH that the small household has to pay. It all
>>gets passed to the end user of the products and services that would be
>>increased in cost. Maybe that would get some folks to turn off the TV and
>>air-conditioning once in a while.
So... If I buy a case of beer, I should pay 24X as much per can?
WTF are you smoking?
SteveRob
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
>I thought compared to vinyl all CD's played backwards!! :-)
Then, when compared to CD's, you would listen to the supposed satanic
messages on Styx albums and such by playing the vinyl forwards but when
compared to other vinyl it would be backwards? <g>
Jeff
A search of the Web did not turn up any specific references to fungus
attacking CD's. The closest was a question from someone in Malaysia as to
whether a certain CD cleaning solution would protect CD's against fungal
damage, so apparently that person has experienced this.
Most of the concerns with the longevity of CD's were with degradation of the
plastics and mechanical separation of the layers.
Oh, come now people. There's no metabolic process that makes aluminum into
food. Undoubtedly, these fungi are eating something organic (glue?) and
producing an acid that is destroying the metalic layer.
At 12:44 AM 6/21/01 -0400, you wrote:
> My jacob's ladder is by far more interesting to look at than any
>two bit lava lamp.
Yeah, I'll bet your neighbors love watching it on their TVs too! :-)
Joe
>
The source code for uucp is availible any number of places; that's probably
the best existing doco. I occasionally have to dust off my ancient UUCP
sk1llz to get files on and off some antique for a client.
BTW...If one wanted to create an out-of-band network, I dunno if I'd pick
UUCP. There are a number of other approaches to doing this out there that
are more functional, more covert and less baroque.
I can almost remember when I was "...!ucbvax!gatech!weasel!ken". Weasel was
a i386sx/20 running SCO Unix in my apartment, and with a 2400 baud dialin, I
was *way* kewler than those BBS weenies. Mail, USENET News and file
transfer...all you really needed. Peter Honeyman was even around to ask
questions, which helped.
Ken Seefried, CISSP
Hey Will, where ya been? Despite mailing you twice, I haven't
received mail from you in a week. I'm eager to continue our
conversation, as I believe you are.
--
Jeffrey S. Sharp
jss(a)ou.edu
Ah, sounds like the IBM RTIC (ARTIC) card... that verdammnt
thing was a b*tch to program, even with the developer kit.
If anyone ever ends up with one and needs some sample
code that actually works (in contrast to what came with
the developer kit), let me know...
Regards,
-dq
> -----Original Message-----
> From: Marvin [mailto:marvin@rain.org]
> Sent: Thursday, June 21, 2001 2:30 AM
> To: classiccmp(a)classiccmp.org
> Subject: IBM Realtime Co-Processor DOS Support V 1.02
>
>
>
> I have no idea what this software package is, but it consists
> of two IBM 5
> 1/4" floppy disks: Dos Support Programs and DOS Support
> User's Guide. There
> is also a 3 1/2" floppy titled "DOS Support User's Guide."
> The description
> on the front of this package says "A productivity aid
> providing installation
> and necessary information to interface DOS software/firmware with the
> Realtime Interface Co-Processor." The proof of license is
> also included
> along with an instruction/warrenty booklet.
>
> First $3.50 for Priority Mail takes it.
>
> > >connection... a lot less than it was back in the days of Trailblazer
> > >modems or earlier. Isn't there some very inexpensive calling plan now
> >
> > I still have one of the Telebit Trailblazer's around here
> > somewhere. A T1000 I believe.
>
> I've got a couple of 'em T1000's, T1500, and a T2500.
> They'll do uucp over dixie cups and damp string.
I doubt it- string's impedance doesn't match Dixie Cups...
you use string with tin cans... with Dixie Cups, ya gotta
use thread.
>From one who knows...
;-)
On Jun 21, 2:53, Netdiablo wrote:
> * Make sure that it includes support for the Indy (older distributions
> didn't). This is often labeled "IRIX 5.3 for Indy R4400" or something
> like that.
All versions of 5.3 support Indys. Some versions of 5.2 may not (I'm not
sure about that). There is one version of 5.3 that won't *boot* on an
R3000 Indigo, but that one will still install if you boot from a diferent
version.
--
Pete Peter Turnbull
Network Manager
University of York
>> I've acquired a SGI Indy system complete with 21" monitor, keyboard and
>> mouse (no IndyCam) but the hard drive has been wiped. Does anyone know
>> where I might get a copy of the IRIX media or what are the licensing
>> terms. Does the hardware come with the right to the OS like NeXT?
>> Looks like a cool system if I can get it up and running. Also are
>> flopptical disks still available?
Congrats on the find! They're wonderful machines. I've got a number of
SGI
machines including the Indigo, the Indy, and the Indigo2. SGI systems
are
by far my favourite desktop UNIX workstations.
In regard to finding the operating system, eBay is really your best bet.
You can find a copy of IRIX 5.3 for probably less than $25. IRIX 5.3
really doesn't get many bids anymore. Note two things, though:
* Make sure that it includes support for the Indy (older distributions
didn't). This is often labeled "IRIX 5.3 for Indy R4400" or something
like that.
* Note that because it uses an older binary format, IRIX 5.3 often
will not be able to run binaries of software that are available out
there on the Internet. SGI does offer the IDO (development environment)
for free for download from their website, though.
IRIX 6.x is definitely the preferred operating environment, but its
more difficult to find, and a bit more expensive too. Depending on
how much RAM and hard disk space the machine has, its a bit more
resource intensive as well.
Resellers are VERY hesitant (if not totally unwilling) to sell you
IRIX media without purchase of a system. Supposedly it has something
to do with SGI licensing terms. If they sell it to you at all, it
will probably be at or near list price (around $300-600, depending
on their persuasion).
I wouldn't waste much time with the floptical drive. You can find
them on eBay relatively often, but I don't think they're useful for
much outside of being a novelty item. The original floptical media
are probably pretty near impossible to find now, and even though
they will read and write standard 1.44 meg disks, its debatable
how necessary this is on a UNIX workstation anyway. As someone
else mentioned, they're probably not super duper reliable, either.
Contrary to popular belief, you can use a standard 2048 byte sector
CD-ROM drive to install IRIX on the Indy, and also the R4000 Indigo,
the Indigo2, and newer machines such as the O2 and Octane. They're
intelligent enough to change the blocksize to 512 bytes before
attempting to use the CD-ROM. They 512 byte sector CD-ROMS are only
necessary on older systems such as the 4D series, Personal IRIS,
Indigo R3000, Crimson (?), etc.
Hope this helps!
--Sean Caron (root(a)diablonet.net) | http://www.diablonet.net
Faltaba apenas un dia para su aniversario de de 18 años. Blanca de Nieve fuera
siempre muy bien cuidada por los enanitos. Ellos le prometieron una *grande*
sorpresa para su fiesta de compleaños. Al entardecer, llegaron. Tenian un brillo
incomun en los ojos...
Hi,
I got a NCD eXplorer Color X-Windows terminal. It is a 14-inch monitor
with a very small base.
(4Megs of display memory, 10BaseT, with installation CDs). Anybody want
it, otherwise it is ending
in the dumpster. This used to be part of my SUN Workstation at home,
but I dont need this part anymore...
Ram
--
,,,,
/'^'\
( o o )
-oOOO--(_)--OOOo-------------------------------------
| Ram Meenakshisundaram |
| Senior Software Engineer |
| OpenLink Financial Inc |
| .oooO Phone: (516) 227-6600 x267 |
| ( ) Oooo. Email: rmeenaks(a)olf.com |
---\ (----( )--------------------------------------
\_) ) /
(_/
On Jun 20, 14:31, Chuck McManis wrote:
> At 07:48 PM 6/20/01 +0000, Pete wrote:
> >But aluminium oxide is Al203 and it's a white powder. Or a rather
> >attractive (and, yes, very hard) crystal, known as carborundum, ruby,
> >emerald, amethyst, etc depending on the impurities :-) The only place
> >you'd get AlO2 (which is also white/clear, by the way) is as aluminate
ions
> >in solution.
>
> My aluminum CDs oxidize black, my aluminum sailboat rigging used to,
> (before I got rid of it), aluminum cans that I tried to melt at one point
> also turned into the a black form of the Aluminum oxide powder. Perhaps
> there are other impurities in it that change its color, I don't know, I
> just observe. Now is someone had a classic HP spectrometer I suppose I
> could put this stuff in there and see what it said it was. :-)
It could be aluminium sulphide (I'm not sure if that's black, but it might
be). Or it could be impurities -- neither your rigging nor the cans will
be pure aluminium. In any case, cans usually have a lacquer coating on the
inside, or paint on the outside. I expect the rigging is also reacting
with something from the water (seawater? lakewater? there's all kinds of
stuff in that), but I don't know what. Usually aluminium corrosion is
whitish-grey. I have no idea about the CDs, though, I must admit.
--
Pete Peter Turnbull
Network Manager
University of York
On Jun 20, 11:13, Zane H. Healy wrote:
> On Jun 20, 12:12, James Rice wrote:
> >I've acquired a SGI Indy system complete with 21" monitor, keyboard and
> >mouse (no IndyCam) but the hard drive has been wiped. Does anyone know
> >where I might get a copy of the IRIX media or what are the licensing
> >terms. Does the hardware come with the right to the OS like NeXT?
> >Looks like a cool system if I can get it up and running. Also are
> >flopptical disks still available?
One or two suppliers stil sell the media. Getting a floptical drive is
rather harder. You might be lucky, though; someone I know picked one up
for a fiver a couple of years ago. However, I'd not recommend spending a
lot of money on one. They are rather sensitive, and in Indys, gather a
*lot* of dust, as the PSU fan sucks air through the floptical. I have a
beautiful example of "why you should keep disk heads clean" pinned to my
wall as a result. If it's just for transferring stuff to/from other
machines, you might find a Zip drive (has to be SCSI for an Indy) or the
network rather more useful.
SGI also supplied SCSI floppies (made by TEAC) in external cases, and other
makes work fine (I've used DEC ones several times).
BTW, Indys are not quite on-topic yet, under the 10-year rule :-) Not long
to go, though, as they were released in 1992/3.
> Unfortunatly your best bet is probably eBay, unless someone on the list
can
> help you. If you want a recent version you'll pay through the nose, and
> even older versions aren't exactly cheap.
Actually, every IRIX system did come with a right to whatever version of
IRIX was supplied with it -- but not to free upgrades. So it's permissible
for a user to obtain and use a copy (including a CD-R copy). This was
discussed at some length on comp.sys.sgi last year, and the concensus was
that SGI ought to provide a reasonably-low-cost copy (as opposed to the
price of an upgrade). However, it seems few SGI sales offices adhere to
this, and the UK office (in my experience) certainly doesn't, even though
they can check to see when the machine was sold and therefore which versin
of IRIX would be appropriate.
James, if you mail me off-list with a note of the machine serial number,
I'll see if I can help out. To boot from CD-ROM, you'll need a CD-ROM
drive capable of delivering 512-byte blocks (not the 2048-byte blocks used
by PCs etc). Many modern ones will be fine, but older ones may not unless
they have a switch or jumpers to set this.
--
Pete Peter Turnbull
Network Manager
University of York
On Jun 20, 15:35, James Rice wrote:
> Sorry about the OT post. I hadn't even looked to see the relase date of
the
> Indy. I was just excited to get one.
Don't take my comment seriously! I doubt if anyone objected. They're nice
machines. I have two myself which I use all the time (look at the first
"Received:" header on this message). Also several Indigos and an O2.
> I was just excited to get one.
And so you should be :-)
--
Pete Peter Turnbull
Network Manager
University of York
On Jun 20, 13:59, healyzh(a)aracnet.com wrote:
> I believe the Indy falls under the cool tech dispensation :^) So it's OK
to
> ask about it here :^)
<aol> I agree! </aol>
--
Pete Peter Turnbull
Network Manager
University of York
On Wed, 20 Jun 2001 14:18:15 -0700 (PDT) Cameron Kaiser
<spectre(a)stockholm.ptloma.edu> writes:
> > Faltaba apenas un dia para su aniversario de de 18 años. Blanca de
> Nieve
> > fuera siempre muy bien cuidada por los enanitos. Ellos le
> prometieron una
> > *grande* sorpresa para su fiesta de compleaños. Al entardecer,
> llegaron.
> > Tenian un brillo incomun en los ojos...
>
> For those of you who don't know Spanish, this is the Snow White
> virus again.
Si.
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
On Jun 20, 10:56, Chuck McManis wrote:
> I had thought it was common knowledge, the reflective layer in many CDs
is
> sputtered aluminum. When exposed to oxygen (as can happen when oxygen
> migrates through the plastic or the plastic is cracked) the Aluminum
> oxidizes and turns black. It does look a bit like a fungus but only
because
> it tends to follow the grain pattern in the deposited aluminum.
> Aluminum-oxide is black and quite hard actually.
>
> I've seen several examples of this in "real life" and while I have never
> seen the process to actually _remove_ Aluminum from the disk it is
> conceivable that the Al02 would form a different crystal matrix and thus
> change its orientation relative to the original sputtering. That could
> leave 'gaps' where the original reflective layer was.
But aluminium oxide is Al203 and it's a white powder. Or a rather
attractive (and, yes, very hard) crystal, known as carborundum, ruby,
emerald, amethyst, etc depending on the impurities :-) The only place
you'd get AlO2 (which is also white/clear, by the way) is as aluminate ions
in solution.
> So folks to don't understand chemistry invent the 'fungus' idea and off
it
> goes into urban legend-dom.
--
Pete Peter Turnbull
Network Manager
University of York
Afternoon, I just received an email with the above virus a few minutes
ago, except now it is all in spanish. It came from classic comp. So
Beware!
Bill