Need advice: Copying large CSV report files off SCO system

I have a SCO Unix server from 1999 running SCO 5.0.5 and some ancient accounting software called Real World

A report writer program on the system is used to generate CSV files from accounting that we write with DOSCOPY commands to 3.5" floppies

In the next 60 days we will be decommissioning this system and I need to generate many CSV files that are too large for the floppies

The system has USB ports but I've been told that the SCO 5.0.5 does not support USB (It did in the next version of SCO?)

There is no external SCSI port on the box.

How can I hook up a large DOS formatted drive of any sort to write these files to that can then be plugged to a Windows machine to access the CSV files?

Any help or advice would be greatly appreciated.

Thanks

Do you have the host or enterprise version. Enterprise has tcp, host does not.
If you have enterprise, you can ftp the files.
If you only have host, then download them using kermit.
Do you have access to another Unix system? If so you can use diskettes and create multi volume tar files.
You can install and mount a DOS hard disk, and copy the files to it, and then move the disk to another machine.
I need to know the root disk controller, and, if it is SCSI, will the BIOS allow you to boot from it if there is an IDE drive installed in order to tell you how to install a DOS hard disk.

I'm not sure if this is host or enterprise. Have no access to another unix system on site.
This machine is not connected to internet. It's just connected to 5 other PCs through a digiboard and we use terminal emulation software on PCs

Preferred method to copy off large reports from this system would be if I can install another HDD on the SCSI chain, copy the reports to that and then remove the drive and hook to a Windows PC somehow

How do I find out what is the root disk controller?

If I acquire a SCSI HDD and just install to the chain will the system just recognize it? If not, what is the procedure to make the new drive an active device on the system?

Thanks

Step 1.
signed on as root
#custom
This will the display the software installed, (and allow you to add/delete)
One of the items will be OpenServer Enterprise or Host.

Although the fact that the terminals are attached through a multi serial port card strongly suggests that you have host.
The 'hw' command will display the hardware installed.
Use the "mkdev hd" command to add a hard disk.
If you add a SCSI disk, you will also need either a second computer with the same SCSI controller, or a way of booting this machine from diskette or cd.
Add an IDE disk, if the BIOS allows you to boot from SCSI ahead of IDE.

There is a possibility that your terminal emulation software has a file transfer capability. Which one do you use?

I have, in the dim past, used a program in basic to capture stuff coming in on a serial port that was generated by cat and redirected to the connected serial port.

telnet question deleted.

We use Omicom or Alphacom I think it's called

Someone gave me a Zip command today that worked great. I can fit 8 - 9 mb files on a floppy so this should work to solve my problem without messing with an additional HDD

Only problem I have now is the 3.5" FD is having some problems. Have not used it in a few years so it may just be dirty. It's running but I'm getting read and copy errors.

Going to try and blow it out first. There's a few SCSI 3.5 FDDs on ebay for $25 if cleaning doesn't work.

Are all SCSI FDDs the same?

What kind of system has a SCSI diskette drive? A standard (34 pins) floppy drive is about 15 dollars.
I am not surprised that the floppy doesn't work, its usually the intake for the cooling fans.
In order to read the floppy diskettes on a DOS/Windows system, first format them using "dosformat /dev/rfd0135ds18" or "dosformat a:"
Zip the file.
Use "doscp file.zip a:" to copy the file to the diskette.
You could always use the "split" command to break up really large files into sections.
Are you creating DOS or UNIX csv files (crlf or lf line endings)? If you create UNIX files, you can copy them and then read them using notepad++ and save as DOS by changing Settings->Preferences

Ok, I blew out the FDD from the front and tried to format a 3.5 in the system using dosformat /dev/fd0135ds18:

This is what I get:

Formatting...
dosformat: Error formatting drive

Should I just replace the drive?

yes, that would be a good second step. The first would be to

tail -40 /usr/adm/messages | more 

as root. That should show enough of the last boot to see if the fd0 device is seen.

If seen but inoperative, replace.

If not seen you may want to look in the CMOS setup to verify that it and the controller are active.

Here's what I got with that command:

                      SCO OpenServer\(TM\) Release 5

              \(C\) 1976-1998 The Santa Cruz Operation, Inc.
              \(C\) 1980-1994 Microsoft Corporation
                          All rights reserved.

                    For complete copyright credits,
               enter "copyrights" at the command prompt.

device address vec dma comment
-------------------------------------------------------------------------
%kernel - - - rel=3.2v5.0.5 kid=98/07/02
%cpu - - - unit=1 family=6
%cpuid - - - unit=1 vend=GenuineIntel tfms=0:6:7:3
%fpu - 13 - unit=1 type=80387-compatible
%pci 0x0CF8-0x0CFF - - am=1 sc=0 buses=2
%PnP - - - nodes=0
%serial 0x03F8-0x03FF 4 - unit=0 type=Standard nports=1 fifo=yes
%serial 0x02F8-0x02FF 3 - unit=1 type=Standard nports=1 fifo=yes
%console - - - unit=vga type=0 12 screens=68k
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
%kbmouse 0x0060-0x0064 12 - type=Keyboard mouse
%PnP - - - nodes=0
%serial 0x03F8-0x03FF 4 - unit=0 type=Standard nports=1 fifo=yes
%serial 0x02F8-0x02FF 3 - unit=1 type=Standard nports=1 fifo=yes
%console - - - unit=vga type=0 12 screens=68k
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
%kbmouse 0x0060-0x0064 12 - type=Keyboard mouse
%parallel 0x0378-0x037A 7 - unit=0
%adapter 0x01F0-0x01F7 14 - type=IDE ctlr=primary dvr=wd
slha 4.06.00
%adapter 0x1400-0x1480 11 0 type=slha ha=0 id=7 Chip=875 -6 40600
%eeE0 0x1060-0x107F 5 - type=EE PRO/100+ 00:90:27:73:ad:c4
%epca 0x0324-0x0324 - - mem=0x000D0000 ports=16 ISA X(e)m V7.0.5
%cd-rom - - - type=IDE ctlr=pri cfg=mst dvr=Srom->wd
%tape - - - type=S ha=0 id=2 lun=0 bus=0 ht=slha
%disk - - - type=S ha=0 id=0 lun=0 bus=0 ht=slha
%Sdsk - - - cyls=1115 hds=255 secs=63 fts=stdb
mem: total = 130616k, kernel = 12912k, user = 117704k
swapdev = 1/41, swplo = 0, nswap = 393216, swapmem = 196608k
Autoboot from rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: Hz = 100, i/o bufs = 6652k

Tue Jul 12 14:18:30 2011
%Stp-0 - - - Vendor=TANDBERG Product= SLR5 4/8GB

#

Indicates that the OS is aware of it. Time to replace it for read or write errors.

What you are looking at is part of the previous and all of the last hardware list that the OS found on boot. Sometimes problems show up on the list.

Thanks very much for the help!
Swapped in an FDD from a garbage PC in our warehouse and it works fine. Formatted 3.5s and wrote files to them.

Don't know why I thought the drive would have been SCSI, it was not

Anyone know where I can find a users manual for SYNCHRONICS IQ Report Writer Version 3.02.17 ???