01-16-2018
I was able to transplant the OS with Microlite - though it took a few hours to get it to work. Had to create a rescue boot CD using Microlite from a fresh SCO6 install in VMware and use that to boot and bring up networking, so we can access the master backup.
Trying to use the Microlite rescue media created within the hardware we're migrating off did not work when booted in VMware - it was not able to bring up network interface.
I suspect a driver issue going on but my workaround worked.
Issue now is my legacy app that uses Thoroughbred BASIC - it is asking for production activation - which is likely tied to hardware and since that has changed it thinks its a new install.
I wonder what my chances are at getting the activation code from the vendor, tbred.com is still around but this is a end of life OS
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm new to the whole Unix thing and have inherited a network running Macs, Windows 2000 and Unix. The Unix side is very suspect at this point and I want to change out the server.
I'd love to use one of the new Apple servers but can't find any info on what "flavors" of Unix it will run. Specificly... (3 Replies)
Discussion started by: matthewd
3 Replies
2. UNIX for Advanced & Expert Users
I'm in the process of installing SCO Open Server 5.05 on the following platform:
Hardware:
IBM 300PL
64 MB RAM
Yamaha 16/4/16 CDRW (Internal defined on SCSI ID 3 LUN 0)
I'm able to boot from the CD and advance to the Installation screen but when it asks for where the media source will... (3 Replies)
Discussion started by: budrito
3 Replies
3. SCO
Dear All,
I am considering installing SCO Open Server as an alternative to MS Exchange. Has anybody had any real world experience of using Open Office?
Thanks,
TC. (1 Reply)
Discussion started by: TCuk
1 Replies
4. SCO
How can I to know procesor type. (1 Reply)
Discussion started by: Batya
1 Replies
5. SCO
I have to purchase SCO Open Server 6.0, so I want to know from where I can get SCO Open Server 6.0 and what is the min. cost in which I can avail this.
Thanks and Regards
Himanshu
Software Engineer
R&D Department (4 Replies)
Discussion started by: ghimanshu
4 Replies
6. UNIX for Dummies Questions & Answers
hi members
i am reading RHEL and i am unable to under stand about PXE boot
and bare metal (1 Reply)
Discussion started by: wagmare
1 Replies
7. HP-UX
How can i make a dvd image ( bare metal backup ) for HP-UX 11i v3 installation on integrity servers , for quick recovery for the os and installed software in case of disaster (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
8. SCO
Hi,
Completely new to UNIX - so be gentle
Cut a long story short, we have a micros 8700 system (eclipse) that needs the Micros 8700 software installed.
The system needs UNIX and I have downloaded and successfully installed SCO open Server 6 and can log into root e.t.c.
Now I have... (13 Replies)
Discussion started by: kennyruss
13 Replies
9. Red Hat
Hi all,
I am working on Linux Bare Metal Restore in which i have few things to be discussed with a person who has his/her hands on in that process.
If anyone kindly give a reply post in this thread.. :) :)
Thanks
Selva (3 Replies)
Discussion started by: selvarajvs
3 Replies
LEARN ABOUT NETBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with NetBSD 2.0, there is a real possibility that the standard tools in /bin and /sbin may become non-
functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows an error message similar to:
init: not found
try booting the system with the boot flag ``-a'' and supplying /rescue/init, which is the rescue init(8), as the init path.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /lib, /libexec, and /sbin, possibly mounting a NetBSD installation CD-ROM and copying
files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the stan-
dard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1)
HISTORY
The rescue utilities first appeared in NetBSD 2.0.
AUTHORS
The rescue system was written by Luke Mewburn <lukem@NetBSD.org>. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>,
based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the curses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
January 20, 2009 BSD