Get APLawrence.com by RSSText File Extraction
Author: dzkil
Date: Fri Jun 23 14:32:07 2006
Subject: Text File Extraction
I have a box running SCO OpenServer 5.0.6. I've been able to locate the file I wish to extract, but the extraction is causing me pain. After reading the articles, and attempting to replicate other suggestions, I simply cannot pull off the text file. Here is what I've tried:
1. ifconfig and only the lo0 interface shows up though an ethernet adapter is installed on the motherboard. it would have been nice (and easier) to allow the OS to capture an IP from the DHCP server and then I could copy the file to the network. I am unsure how to bring up the interface (besides ifconfig en0 up) because it seems even the hardware isn't being recognized.
2. copying the file to a 1.44 mb diskette. this failed. it returned the error message "tape write error" for multiple instances or different diskettes.
Please advise, as I do not know much about the OS, or further, how to troubleshoot this issue.
Thank you,
David
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 2 | 6 | 24 | 336 | 2,178 |
/Forum/dzkil1.html copyright June 2006 dzkil All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Your ad here - $24.00 yearly!
UBB Computer Services Support for Openserver, Unixware and Linux. Windows integration with Unix/Linux servers. Hardware, Backup and Networking issues. Located near Sacramento CA, we provide onsite support throughout Northern CA and Nationwide via remote access. We are a SCO Authorized Partner and a Microlite BackupEdge Certified Reseller.
http://bcstechnology.net Full service Linux & UNIX systems integrator; Windows to UNIX/Linux Client-Server Specialist; Secure E-Mail & Website Hosting; Thoroughbred Software Developer; Custom Industrial Automation; Hardware & Electronics Experts; In Business Since 1985.
http://www.breakthru.com.au SCO (Openserver and Unixware), Unix, Solaris and Linux Consulting services including: Secure Networking Solutions; Linux based Firewalls; Backup Solutions; Secure Home to Office Network Setup; Phone, Remote and On-Site Support available - Satisfaction Guaranteed!
Related Posts
Fri Jun 23 14:40:10 2006: Subject: TonyLawrence
Network cards are not added automatically. Run "netconfig" to add the card. If you are running a recent version, it can use DHCP. Older versions will require manual ip config, but that's right in netconfig.
PCI cards should be identified automatically when you add a lan card with netconfig. If it does not, see the network configuration section of http://aplawrence.com/Unixart/inst505.html
How did you attempt to copy to floppy? Did you read http://aplawrence.com/Basics/floppies.html
Sat Jun 24 17:11:22 2006: Subject: NIC Woes BigDumbDinosaur
PCI cards should be identified automatically when you add a lan card with
netconfig. If it does not, see the network configuration section of
http://aplawrence.com/Unixart/inst505.html
Also, are you certain the NIC has an OSR 5.0.6-compatible driver loaded? You shouldn't assume that the NIC is supported just because it's a well-known brand. Speaking of brands, IMPI, the only brand of NIC to use with anything SCO is 3Com (3C905 series).
Also, is the card being recognized by the machine's BIOS at boot time? You should be able to determine that by reading the system configuration screen that is displayed following POST (press the Pause key to stall the system if necessary so you can peruse the sysconfig screen before the Boot: prompt appears). If not, run the BIOS setup, locate the function to clear ESCD, enable it and then exit-with-save from the BIOS. When the system restarts, all notions about what was plugged into the PCI slots will be erased and rebuilt from scratch.
If, after doing all this, you still don't see the NIC listed as a PCI device, you either have a bad NIC (more common than you might think), a system resource allocation error due to a bug in the BIOS (flashing the BIOS might help here) or a flaky PCI slot, a problem that usually shows up in the last (bottom) slot due to design errors in the motherboard itself (ABIT boards come to mind). Speaking of slot usage, don't plug the NIC into the PCI slot immediately adjacent to the AGP video adapter slot. The two slots are wired to the same interrupt line on the board's PIC (programmable interrupt controller). If a NIC is plugged into that PCI slot it will have to share its interrupt with the video adapter, which almost always causes system instability. AGP cards (and some NIC's) are notorious for not gracefully handling shared interrupts. In a few cases, the NIC may be capable of properly handling a shared interrupt but its driver may not.
Sat Jun 24 21:59:04 2006: Subject: Clarification TonyLawrence
By "listed" we do not mean the list of several dozen cards that will come up when it doesn't see a PCI. A PCI card should pop up by itself after you say Add a Lan adaptor - if it doesn't, you don't have the right driver - see http://aplawrence.com/newtosco.html for that.
Sat Jun 24 22:01:32 2006: Subject: TonyLawrence
And if all else fails see
http://aplawrence.com/Unixart/datatran.html
Add your comments
Installation and light training Boston and New England