If anyone is willing to help I would defenitely appreciate it!

The situtation is that we have a client that had a "falling out" with their software/hardware vendor and now aren't able to get support for their machines and software.

What's happening is they're using SCO-Unix and a medical software called SDM (Scientific Data Management, which was later Vital-Works, which is now Cerner) and they're getting database errors related to not having enough drive space. Usually when I GHOST a HDD I'm able to adjust the sizes of the partitions to the destination but when I GHOST this hard drive onto a bigger one it won't let me do it. So basically the original hard drive is ~4GB, single partition. The new hard drive is ~20GB. After Ghosting to the new drive I have the ~20GB drive split into 2 partitions. The ~4GB and then the ~16 unallocated space. Is there an easy way to resize/reallocate that ~4GB or ~16GB to just be ONE drive. Oh yeah, and to make this more fun. I don't have any SCO Floppies to boot from but I do have a tape backup (which I'm not even totally sure what it has on there).

Any help to some tutorials or readings would be fantastic!

Thank YOU!

Stressed,

Partie™

Buy this product, and use it for backup as well as resizing partitions etc.(www.microlite.com)

If the Veritas file manager is installed on the system, you can use it to resize the partitions.
Symantec Ghost up to version 2003 will not resize EAFS file systems

jgt,

Thank you for the quick reply and sorry for the slow response. I have been messing around with this thing. I've found something else already on the system called Lone-Tar and used that. It seems to be going well but I'm still getting errors!!! It's driving me nuts. I can't figure out what's wrong. It tells me the database needs maintenance on a screen with some text that says "Pro/5" from BASIS international. I looked them up but really couldn't find much info on repairing my problem. There's only 1 consulting firm I was able to contact about this software and they want nearly $15,000 and they don't guarantee anything so I might as well do it myself!

Anyone here know what Pro/5 is and why I'm getting a warning about a database needing maintenance????

Thank You,

Partie™

Is a Basic compiler for Business Basic applications.
What version do you have, I have a copy of it from at least 5 years ago.
The problem that you are having may be because there is a protection scheme built into the software that requires that one of the files have a specific inode number.
If so you may have to re-install the compiler from the diskettes???? There are three in the version that I have.
Jack

I'm not sure of any version numbers but here is what I see on the screen when I get the error:

"PRO/5 Copyright (C) 1985-1998 BASIS International LTD
All Rights Reserved.

Level 5 Rev 2.04
Build: Oct 15 1998 08:07:50

Pro557504

Network Enhancements

Warning: DATABASE SYSTEM REQUIRES MAINTENANCE. Please notify system supervisor."

If it helps, the client machines are running windows 98 and are connecting to this unix server via serial connections (COM Ports) ttys.

Also, what do you mean by "that one of the files have a specific inode number". Please forgive me but I know UNIX about as much as I know how to do brain surgery.

Thanks again for your responses and the insight you've given me.

Partie™

There are several ways to copy protect software in unix.
One is to use a file that contains the inode number of that file, so that when the entire product is copied to another machine the probability of that file having the same inode number is miniscule.
Another is to use a sparse file. This is a file purposely fragmented (to use Microsoft words) when it is created. If this file is copied to another location, the 'gap' disappears and the file becomes contiguous.

However, after re-reading your original post, I think that copy protection is probably not the case, but rather that because you ran out of disk space, the data files are out of sync.
What I mean by that is Pro5 uses ISAM files that are made up of a data file, and a separate index file (eg CUST.DAT and CUST.IDX). There should be a utility that will allow you to rebuild corrupted databases, so that, in the example above, CUST.IDX is forced to reflect the data that is found in CUST.DAT
Sorry to sound so vague about the rebuild, but I haven't used this software for at least 5 years, and we just moved, and and the documentation is somewhere deep in a 48 foot trailer.

Jack