I have a full-length ISA board marked "Cheetah Int'l Cheetah Cub
2Mbyte Fast Memory". Copyright 1986
It has 4 banks of 18 socketed memory chips marked:
USA 8726 B
MT 1259-10
I'm guessing those are 10ns 32KB chips?
I'm really curious what this board will work with and its history.
Google seems not to know it exists.
Doc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cromemco RDOS 02.52
no boot
Found the disconnected HD power connector and reattached it. The HD is now
spinning but what is the command to get it to boot from the harddrive?
OR
does anyone have a spare 8" floppy with a cromemco system three boot setup?
- --
Collector of vintage computers
http://www.ncf.ca/~ba600
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAxzQmLPrIaE/xBZARAjlWAJ9MEgqHP6KQZoSijKAZxWINcr332wCgigoY
kADFFprB2IJHSMFAUXzBG+U=
=RsyK
-----END PGP SIGNATURE-----
>Does anyone have a copy of OS/2 (any version, but I'm really looking for all
>of them...) for my Virtual PC collection of antique operating systems?
>
>I'm not sure how folks here feel about the piracy of software that is no
>longer available. I would, of course, be willing to pay for a legal copy,
>as long as the price was reasonable.
You should have asked a week ago... I just gave two full copies of OS/2
Warp (2.0? 3.0?) to someone else on this list. Maybe if he doesn't want
them he will contact you and give/sell you one (I don't know what his
needs for them were... they were in a box of software that I told him to
pick thru and take what he wanted... so he may or may not be willing to
give one up)
-chris
<http://www.mythtech.net>
Hello,
I saw your posting to a newsgroup that you made about 1/2 year ago, and was wondering if you could give me the openvms media. I'm trying to get the media running on the x86 version of simh as an experiment, and need an iso image to install the media from. Is it possible that I can download the media from you?
-- Michael S.
---------------------------------
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger
> And thusly chris spake:
> >
> > So does anyone have any other recommended solutions? I'd
> like this to be
> > as transparent to the users as possible (they currently run
> the software
> > in a DOS session under Win95, so the closest I can come to that
> > functionality, the better).
> >
>
> Chris,
>
> Have you tried DOSbox? --> http://dosbox.sourceforge.net .
>
> Cheers,
>
> Bryan Pope
Here's an othere one: http://www.freedos.org/
- Henk, PA8PDP
>> Its a medical scheduling application called Perfect Care.
>
>presumably not related to the "Perfect Software" office suite
>of 20 years ago
Er, I don't know. http://www.sticomputer.com/
I did just realize their NY Metro office is in Oakland, which is only a
short drive for me (10-15 minutes depending on traffic). And I will
actually be in Oakland Thursday morning anyway. Maybe I'll just stop in
to their office and see if I can have a talk with someone. Although I
know when I called the NY Metro office earlier, they redirected me to an
800 number for support, so there may be no one available in Oakland to
help me.
If I can at least get out of them what fails under XP, I may be able to
find a work around.
-chris
<http://www.mythtech.net>
>WHAT "application"? It really DOES matter.
>"old"? "legacy"?
Its a medical scheduling application called Perfect Care.
>WHO told you? the author of the program?? Uncle Charlie??
The support guys at the company that made the software. Their exact
statement was "we've had major problems getting it to run in DOS under
XP". When asked if per chance this was unique to XP, the answer was no,
it was a problem with the entire NT line's DOS ability. Their recommended
solution? Upgrade to their new Windows based product. That's more or less
what is going to happen, but not for another few months (the upgrade is
going to a different product, but regardless it will be upgraded, so I
need a solution that will run for 4-6 months)
>Have YOU tried it?
No, but I plan to. But the location is 3 hours away from me, so it isn't
something I'm going to drive to give a whirl. It will wait until I am at
the location doing the rest of the upgrades. It may be a simple work
around, or it may be very complex, I won't know more info until I get
there next week.
>Sorry to seem harsh, but "been told it won't run" is
>quite a bit different from "it won't run".
Agreed... but I've been "told" it won't run, and I need to make it run,
so I want to arrive at the site armed with options on how to get it to
run.
>The DOS box in NT (which XP is one of) is just fine
>for running "old legacy DOS application"s (PROGRAMS).
>BUT,...
>NT will NOT permit certain kinds of hardware access,
>such as writing disk sectors, "for security reasons".
>Therefore, XenoCopy can not run in any version of NT
>(NT3,NT4,Win2K,XP).
All this I knew. It may be doing some kind of hardware access, I don't
know.
>If the reason that the "old legacy DOS application" won't
>run is because it needs to do something that has been
>blocked "for security reasons" (such as writing disk sectors),
>then it won't run any better with VPC.
Won't it? VPC makes the software think it is running on its own computer.
So I would think the software could write to "disk sectors" inside VPC.
>From there VPC would take care of altering that into whatever method XP
wishes to be used.
>So, it DOES run in a Windoze DOS box. There are few things that
>will run in a Win95 DOS box that won't run in an XP DOS box,
>other than "security risks"
Correct, they are currently doing it inside Win95. But like mentioned
above, the software developers say it doesn't work inside the NT
structure. So they may do something that is restricted (they may also
just need a very tweaked PIF and don't bother telling anyone that in an
effort to get them to upgrade to a newer version... I really can't say).
>What kind of partition does the system have?
>Does the "old legacy DOS application" need access to the hard disk?
>(ones that REALLY are "old" would not)
Don't know and don't know. I have not yet stepped foot on site, and the
salesman that did originally spec'd out using a Terminal Emulator to
access the legacy system. When I questioned why we had to purchase a new
program to access something they are currently doing in Windows (ie: why
not just run whatever program they are running now to access it), that is
when I was put on the hunt to find the answer. After talking to the site
myself, it now appears the salesman was incorrect and it is in fact
running a DOS application. BUT, I haven't been there myself yet, so maybe
it will turn out to just be some terminal front end. The people on the
site don't really know themselves, all they could do is tell me what they
do to make it run, and from that I get the impression it is a DOS
application (that and talking to the developers, they said it is a DOS
app).
>1) Boot from floppy with DOS 6.2x. If it DOES need the hard disk,
>then make a small FAT16 partition for it to use.
>
>2) install a dual boot of XP and Win98, and make the drive,
>or a partition of it, FAT32.
No can do. The app needs to be run side by side with other XP/2000 based
apps (the new app that is dictating this hardware/OS upgrade requires
either XP or 2k). So I can't do a dual boot as it will prohibit both the
legacy and the new app from running at the same time (I can do a VPC type
solution since that will run in a window inside XP... but VPC's pricing
will probably be an issue for something that I need 5 copies for only a
few months)
-chris
<http://www.mythtech.net>
>From: ard(a)p850ug1.demon.co.uk
>
>> Find out why it's not working? [Tony's standard rant here, but replace
>> 'hardware' with 'software' ;-)]
>
>:-)
>
>Yes, my comments apply to software, hardware, electronics, mechanical
>stuff, just about anything... You will never solve a problem by making
>random changes in the hope it goes away (it might well seem to be cured,
>but it may also come back to 'bite' you later).
Hi
One most often introduces more problems by random fiddling.
>
>Fautlfinding is done by making 'measurments' (in the widest possible
>sense -- in other words gathering evidence), thinking about what you've
>observed, and then working out what to do to put it right.
I'd like to add this here. Fault finding is a cycle:
1. Gather evidence
2. Make hypothesis consistent with the evidence
3. Create test to verify hypothesis
4. Repeat from 1 if that test didn't work
and add this new result as new evidence.
Number 4 may include replacing a part but usually not unless you
are really sure that you've exhausted all the angles. The first
rule of intelligent tinkering is, of course, "save all the pieces".
The second rule is "don't fix it if it ain't broken". The second
rule applies to step 4 as far as doing random replacements.
Swapping boards is not all that bad if you are sure you have the
right board from repeated steps 1 to 4. When working on old computers,
expect to spend time repairing that board as well.
Just my thoughts.
Dwight
>
>Yes, this is a rant of mine. I've been caught too often by idiots who
>don't follow this method...
>
>-tony
>
Sorry to all those who are waiting on emails from me. My mailbox has hit
3000 emails and I just can't make myself go through it all yet, so I'm
pretty much only responding to 'emergency' emails.
I do plan on making it to VCF east, as long as several other people are
planning to be there with certain gear. Was hoping to bring up a bunch of HP
cabinets and 7906 drives and 13037 controllers and a 21mx or two. I know I
promised the 7906 drives would be refurbed, but I"m not sure I'll get to
that in time. The 13037's have been refurbed though. Hopefully I'll be
bringing a big load of stuff back and some DEC rack sidepanels! woohoo!
Anyways, my apologies to all who are patiently waiting for me to respond.
I'll wade through it all sometime fairly soon.
Jay
