Installing an Old Harddrive?

S

Skeleton Man

This is a pretty interesting development, however:
I don't know why I didn't do this before, but performing a dir /ah on the
maxtor drive as a slave in XP yields:
05/31/1994 06:22 AM 40,774 IO.SYS
05/31/1994 06:22 AM 38,138 MSDOS.SYS
09/20/1995 04:56 AM 8,472,576 386SPART.PAR
09/30/1993 06:20 AM 64,246 DBLSPACE.BIN
05/31/1994 06:22 AM 66,294 DRVSPACE.BIN
05/31/1994 06:22 AM 512 DRVSPACE.MR1
07/05/1996 12:50 AM 112,671,232 DRVSPACE.000
12/17/1994 04:55 PM 109 DRVSPACE.INI
01/05/2005 11:37 PM <DIR> System Volume Information

Most definately compressed with drivespace then.. all your data is contained in
DRVSPACE.000.. You either need to boot from that drive or setup a dos boot disk
with drivespace so you can mount your drive and copy the data..

Regards,
Chris
 
T

Trent©

When bringing up the system with only the Maxtor HD and a bootitNG floppy, a
single partition is found.

Now I think I remember...which BootIt has verified...

The compression program...DriveSpace, which you are running on that
drive...creates a hidden file...not a hidden partition. But its
always a good idea to know for sure that nothing else is on the drive.
Also, the bootit
creation of the EMBR fails on HD0, and reading the manual, this is
indicative of write-protected media. Could this drive somehow be write
protected?

I doubt it. But we'll know soon enough. We're gonna write to it.
I sure didn't do it, but that might explain why it won't boot.

You don't write when you boot...you only read.
Or
maybe whatever physical component responsible for disk writes is now
inoperative? I've been tentative to test write to the Maxtor, for fear of
ruining the data somehow.

Reading ahead...we need to create an autoexec.bat file and a
config.sys file...and put them on the hard drive...so that we can load
the drivers for the compressed volume.

Too bad you don't have a program similar to R-studio...that can bring
back deleted files. You could just get those from the drive.
This is a pretty interesting development, however:
I don't know why I didn't do this before, but performing a dir /ah on the
maxtor drive as a slave in XP yields:

F:\>dir /ah
Volume in drive F has no label.
Volume Serial Number is 1D91-5DCC

Directory of F:\

05/31/1994 06:22 AM 40,774 IO.SYS
05/31/1994 06:22 AM 38,138 MSDOS.SYS
09/20/1995 04:56 AM 8,472,576 386SPART.PAR
09/30/1993 06:20 AM 64,246 DBLSPACE.BIN
05/31/1994 06:22 AM 66,294 DRVSPACE.BIN
05/31/1994 06:22 AM 512 DRVSPACE.MR1
07/05/1996 12:50 AM 112,671,232 DRVSPACE.000
12/17/1994 04:55 PM 109 DRVSPACE.INI
01/05/2005 11:37 PM <DIR> System Volume Information
8 File(s) 121,353,881 bytes
1 Dir(s) 8,509,440 bytes free

Does this help us at all?

Yup...tremendously. I think all we need is to create an autoexec and
a config...to put on the drive.

The bad news! I don't remember exactly what to put in them. I'll
hafta do some research. Maybe someone else can jump in here who has a
better memory than me. lol
It seems unlikely that there would be a hidden
partition on this drive, as all data (size-wise) is now accounted for. Or is
this faulty logic?

You have all you need. Again, all you need to do is load the
drivers...which happens at boot-up time...from the autoexec and
config.
I guess I have empirical evidence now.

Yup...ya done good!! lol
Again, thanks...

Welcome.

I'll do some research...you can to. And maybe someone will jump in
here.

Basically, we need to create an autoexec and a config with
Notepad...then put those files on the hard drive. That should pretty
much do it. The drive should then boot...with all the info that
you've been looking for.

Then we can go on to phase 2...moving that info to the media of your
choice.

I'll try to get back to you later today.


Have a nice one...

Trent©

Budweiser: Helping ugly people have sex since 1876!
 
T

Trent©

Things you can do while we're searching...

Find the file...drvspace.sys...from somewhere...and copy it to the
Maxtor drive.

Create a file in Notepad...name it 'config.sys'...copy it to the
Maxtor...put this one line in the file...

device=drvspace.sys

Then boot the Maxtor drive...see what happens.

You won't hurt anything...but it might just work with that.

Make a note of any error messages you may get.


Have a nice one...

Trent©

Budweiser: Helping ugly people have sex since 1876!
 
Z

Zip

Trent© said:
Yup...tremendously. I think all we need is to create an autoexec and
a config...to put on the drive.

The bad news! I don't remember exactly what to put in them. I'll
hafta do some research. Maybe someone else can jump in here who has a
better memory than me. lol

This has been my problem as well. I started a thread in alt.msdos related to
this question yesterday, but that's not the most active group. And as far as
I know, the bootdisks at bootdisk.com don't offer support for compressed
volumes.

Here is a config.sys and autoexec.bat from an old 386 SX 25 AST laptop that
miraculously decided to power up:

autoexec.bat:

LH /L:1,13984 C:\DOS\SHARE.EXE /L:500
@echo off
LH /L:0;1,45456 /S C:\dos\SMARTDRV.EXE
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS

config.sys

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
BUFFERS=10,0
FILES=8
DOS=UMB
LASTDRIVE=K
FCBS=16,8
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p
DOS=HIGH
rem DEVICEHIGH /L:0;1,9424 /S =C:\DOS\INTERLNK.EXE
STACKS=9,256
DEVICEHIGH /L:1,39568 =C:\DOS\DRVSPACE.SYS /MOVE

There is a reference to drvspace, but I'm not sure if the laptop is using
it.
I'll do some research...you can to. And maybe someone will jump in
here.

Basically, we need to create an autoexec and a config with
Notepad...then put those files on the hard drive. That should pretty
much do it. The drive should then boot...with all the info that
you've been looking for.

Sounds simple enough. A few things still bother me, though:

1) Out of all the files on the hard disk, why are 'autoexec.bat' and
'config.sys' missing? You made a reference to R-studio, but I just don't
think these files were deleted. This HD has never been out of my control,
and not powered up since.. hmmm... Jul/96 according to the file dates.
Furthermore, I just noticed that WinXP will not show the following files,
for whatever reason: 'autoexec.bat', 'config.sys' and 'command.com'. I have
a bootdisk from bootdisk.com in the A: drive, and WinXP does not show these
3 files (WinXP is set to show hidden files), even though they can be found
outside of WinXP. Perhaps something like this is masking the presence of
autoexec.bat and config.sys on the Maxtor?

2) We know the HD is compressed with drvspace, but there are seemingly a few
files that are uncompressed. Why can't this small collection of files be
found with a DOS boot disk? I understand I need to load the drvspace drivers
to get access to all the files, but these uncompressed files should be
accessible with a simple DOS boot disk, right? They aren't.

I feel like we may be getting close! =)

Thanks...
 
T

Trent©

This has been my problem as well. I started a thread in alt.msdos related to
this question yesterday, but that's not the most active group. And as far as
I know, the bootdisks at bootdisk.com don't offer support for compressed
volumes.

Here is a config.sys and autoexec.bat from an old 386 SX 25 AST laptop that
miraculously decided to power up:

I don't think we even NEED either of these...but I thought it might be
easier to have them.

Create them per below. I forgot that we've got to invoke drvspace.

autoexec.bat:

PROMPT $p$g
PATH C:\;a: (that's a colon after the c:\)
drvspace

We shouldn't need all the rest. You've got a modern machine...and
we're not loading all that much. So you shouldn't need any LH
entries. And you don't have those on that drive anyway.

config.sys

DEVICE=C:\DRVSPACE.SYS

Just make sure you have drvspace.sys on the drive.

There is a reference to drvspace, but I'm not sure if the laptop is using
it.

Do a search for it. If its there, copy it to the Maxtor.

Sounds simple enough. A few things still bother me, though:

1) Out of all the files on the hard disk, why are 'autoexec.bat' and
'config.sys' missing? You made a reference to R-studio, but I just don't
think these files were deleted. This HD has never been out of my control,
and not powered up since.. hmmm... Jul/96 according to the file dates.

Obviously, SOMETHING happened since then...since the drive doesn't
boot. Memory is the 2nd thing to go!! lol

Normally, the program and the drivers are loaded by autoexec and
config...as part of the boot process. That process mounts the
compressed volume...and its then a regular, automated boot.

In my prior post, I forgot to tell you that you need to start the
drivespace program...from the 'drvspace' command in the autoexec.
Furthermore, I just noticed that WinXP will not show the following files,
for whatever reason: 'autoexec.bat', 'config.sys' and 'command.com'. I have
a bootdisk from bootdisk.com in the A: drive, and WinXP does not show these
3 files (WinXP is set to show hidden files), even though they can be found
outside of WinXP. Perhaps something like this is masking the presence of
autoexec.bat and config.sys on the Maxtor?

Got me! lol I have no idea how the guy from bootdisk.com does things.
But I don't think so. For grins, you might want to open up
drvspace.ini with Notepad...just to see what's in there.

A boot disk is normally only a system disk. I didn't know that he
included an autoexec and a config on the disk. That may be part of
your problem. Take a look at them...see what they say.

2) We know the HD is compressed with drvspace, but there are seemingly a few
files that are uncompressed. Why can't this small collection of files be
found with a DOS boot disk? I understand I need to load the drvspace drivers
to get access to all the files, but these uncompressed files should be
accessible with a simple DOS boot disk, right? They aren't.

Which files?
I feel like we may be getting close! =)

Its hard to remember all this stuff sometimes. I've got a hard time
figuring out how the CoffeeMate got out of the cupboard and into the
refrigerator! lol

This thing might even simply resolve itself once you get drvspace.sys
put on the drive.
Thanks...

Welcome.


Have a nice one...

Trent©

Budweiser: Helping ugly people have sex since 1876!
 
Z

Zip

Trent© said:
Things you can do while we're searching...

Find the file...drvspace.sys...from somewhere...and copy it to the
Maxtor drive.

Create a file in Notepad...name it 'config.sys'...copy it to the
Maxtor...put this one line in the file...

device=drvspace.sys

Then boot the Maxtor drive...see what happens.

You won't hurt anything...but it might just work with that.

Make a note of any error messages you may get.

Same thing: "Boot disk error. Please insert a system disk and press enter"

Someone on alt.msdos brought up a good point. There is a mysterious
directory that has shown up on the drive over the past few days: "System
Volume Information", probably as a result of me trying to browse the drive
in WinXP. This directory name, however, should not be possible on a FAT
formatted drive. Could its presence be prohibiting the drive from booting,
and furthermore, prohibit the drive from being recognized from a DOS 6.X
bootdisk? This would make sense.
 
T

Trent©

Same thing: "Boot disk error. Please insert a system disk and press enter"

Someone on alt.msdos brought up a good point. There is a mysterious
directory that has shown up on the drive over the past few days: "System
Volume Information", probably as a result of me trying to browse the drive
in WinXP. This directory name, however, should not be possible on a FAT
formatted drive. Could its presence be prohibiting the drive from booting,

No...not that I know of. Its not NEEDED, of course. But it shouldn't
be hurting anything.
and furthermore, prohibit the drive from being recognized from a DOS 6.X
bootdisk? This would make sense.

If you think so, simply delete it.

For the present time, forget about what I said about hunting for
drvspace.sys. I don't think we need it...although I recall running it
with my drives. But I think we can ignore it for the time being.

Have you made a backup Ghost of that drive?...to another partition on
a good drive? If you have that capability, it might not be a bad
idea.

What I'm thinking of next...and this may NOT be a good idea...is that
we could do a FDISK/MBR on that drive. But I don't remember if that
will hose up the drive or not. So don't do it yet.

Recap for us how you've got the drive set up now. Are you running any
autoexec or config?

One final thought...

Do you have the BIOS set to 'auto'? If so, that could be part of the
problem. See if the drive has the parameters (heads, cylinder, etc.)
on the top of the drive. If not, see if you can Google for them. We
may want to set the BIOS to those actual numbers...instead of 'auto'.

What files are on that floppy boot disk that yer usin'? Do you have
drvspace.bin and scandisk on that floppy? Don't you have a 98 rescue
disk that you can boot to?


Have a nice one...

Trent©

Budweiser: Helping ugly people have sex since 1876!
 
T

Trent©

I don't recall...

When you boot into that F drive, did you try changing over to the C
drive? Just do a...

c: <enter>

see what happens.


Have a nice one...

Trent©

Budweiser: Helping ugly people have sex since 1876!
 
Z

Zip

Trent© said:
Have you made a backup Ghost of that drive?...to another partition on
a good drive? If you have that capability, it might not be a bad
idea.

Not sure what a backup Ghost is, but I have copied all the files from the
Maxtor to the WinXP drive to be on the safe side. I'm beginning to think
there may be a physical problem with the Maxtor. 8 of the 9 files copied
correctly, but when trying to copy 386SPART, I get the message: "Cannot copy
386SPART: The drive cannot find the sector requested.
What I'm thinking of next...and this may NOT be a good idea...is that
we could do a FDISK/MBR on that drive. But I don't remember if that
will hose up the drive or not. So don't do it yet.

Sounds fun... ;)
Recap for us how you've got the drive set up now. Are you running any
autoexec or config?

Earlier Tests:

1) Removed "System Volume Information" directory, as well as all data
created after 1/1/05, and tried to boot the Maxtor as a master single ->
"Boot disk error. Please insert a system disk and press enter."

2) Created a bootdisk with autoexec.bat and config.sys as specified above.
Only drive recognized is A:. I tried initiating 'drvspace' at the end of
autoexec.bat, but that initiates a menu GUI to create a new compressed
drive. I'm not sure it's necessary, or even helpful, for getting at an
already compressed volume.

I was going to try and put these autoexec.bat and config.sys directly on the
Maxtor, but as I said above, I think there is a physical problem with the
disk prohibitting it from booting, and I think the bootdisk approach is
probably best.
One final thought...

Do you have the BIOS set to 'auto'? If so, that could be part of the
problem. See if the drive has the parameters (heads, cylinder, etc.)
on the top of the drive. If not, see if you can Google for them. We
may want to set the BIOS to those actual numbers...instead of 'auto'.

I will check this out.
What files are on that floppy boot disk that yer usin'?

SYS.COM
COMMAND.COM
ATTRIB.EXE
CHKDSK.EXE
DELTREE.EXE
EMM386.EXE
FDISK.EXE
LABEL.EXE
MEM.EXE
MSCDEX.EXE
QBASIC.EXE
UNDELETE.EXE
CD2.SYS
EDIT.HLP
UNDELETE.INI
C.BAT
HIMEM.SYS
CONFIG.SYS ->{DEVICE=A:\DRVSPACE.SYS}
AUTOEXEC.BAT ->{PROMPT $p$g PATH C:\;a:}
MOUSE.@@@
CD3.SYS
EDIT.EXE
EDIT.INI
DOSKEY.COM
UNFORMAT.COM
TREE.COM
FIND.EXE
RESTORE.EXE
SETVER.EXE
SCANDISK.EXE
SHARE.EXE
XCOPY.EXE
QBASIC.HLP
MOUSE.INI
SCANDISK.INI
MOUSE.SYS
CD4.SYS
CD1.SYS
FORMAT.COM
MOUSE.COM
DRVSPACE.SYS
CONFIG.BAK
AUTOEXEC.BAK
IO.SYS
MSDOS.SYS
DRVSPACE.BIN
DRVSPACE.INI
Do you have
drvspace.bin and scandisk on that floppy?
Yes.

Don't you have a 98 rescue
disk that you can boot to?

Not off hand, but I'll bet bootdisk.com offers one.
 
Z

Zip

Trent© said:
I don't recall...

When you boot into that F drive, did you try changing over to the C
drive? Just do a...

c: <enter>

see what happens.

Well, the only time I have ever had access to the Maxtor and it's data is
been when I have set the Maxtor as a slave through WinXP. So I'm assuming
that performing a "C:" from the maxtor (F:) would just bring me back to the
WinXP drive
 
Z

Zip

Trent© said:
Here's a pretty good link...

http://64.233.167.104/search?q=cach...133175/EN-US/+scandisk+mount&hl=en&lr=lang_en

Watch the wrap.

You might try #6.

I'm guessing you haven't run a scandisk on it yet.

No, and based on the sector error I got earlier, this was going to be my
next move. The only problem is that WinXP is the only thing that recognizes
the Maxtor, thus, I'm going to have to use WinXP to perform the scandisk,
and not a DOS boot floppy like I'd like to. Do you think this would be a
problem?
 
Z

Zip

Trent© said:
Here's a pretty good link...

http://64.233.167.104/search?q=cach...133175/EN-US/+scandisk+mount&hl=en&lr=lang_en

Watch the wrap.

You might try #6.

I'm guessing you haven't run a scandisk on it yet.

Just ran 'chkdsk F: /F /R

Result:

Windows replaced bad clusters in file \386SPART.PAR
of name (null).
File and folder verification is complete.
Windows is verifying free space...
Bad sectors found.ted...
Free space verification is complete.
Windows has made corrections to the file system.

129,931,264 bytes total disk space.
121,362,432 bytes in 8 hidden files.
55,296 bytes in 1 files.
8,484,864 bytes in bad sectors.
28,672 bytes available on disk.

2,048 bytes in each allocation unit.
63,443 total allocation units on disk.
14 allocation units available on disk.

Thought just fixing the bad sectors would allow the drive to boot, maybe,
but no luck...
 
N

N9WOS

No, and based on the sector error I got earlier, this was going to be my
next move. The only problem is that WinXP is the only thing that
recognizes the Maxtor, thus, I'm going to have to use WinXP to perform the
scandisk, and not a DOS boot floppy like I'd like to. Do you think this
would be a problem?

A few notes here......
Go to the old laptop with dos on it
Go to the DOS directory and copy the MSD.EXE file,
from there, on to a boot floppy.

MSD.EXE is a general diagnostic, and information program.
You should be able to run it and see what drives are available anywhere on
the system.

(IE) if DriveSpace relocated the C: to another drive letter,
but couldn't mount the compressed volume to assign it as C:\

Don't worry about the 386spart.par file
It's just the win 3.X swap file.
If it's lost, you have lost nothing.

Are you running the drive in the same drive geometry settings
as it's original installation?
Those old drives can be set to FOUR different geometries.

One for newer computers,
and three that can work on older computers with the
x head x number cylinders and x sector limitations.

If you had it set in the compatible geometry setting, and formatted it,
Then put it in an auto detect computer,
The auto detect may set it to the default setting.
When you try to read it, you may get the directory listing,
but all the information will be messed up and unusable.
(ie) won't boot.

Hear is the possible settings.


J13/J14 Power-up Configuration
------------------------------------------
J14 J13 Cyl Hds Sec MB
---------------------------------------------------------
CLOSED CLOSED 936 16 17 130.3 (default)
OPEN OPEN 1024 14 17 124.8
CLOSED OPEN 762 8 39 121.7
OPEN CLOSED 900 15 17 117.5


Make a note of the setting on your drive,
and then see if the computer bios shows the same values.
If it does not, then manually set the values in the bios setup to match the
drive.
 
C

CBFalconer

Zip said:
No, and based on the sector error I got earlier, this was going to be my
next move. The only problem is that WinXP is the only thing that recognizes
the Maxtor, thus, I'm going to have to use WinXP to perform the scandisk,
and not a DOS boot floppy like I'd like to. Do you think this would be a
problem?

DOS 6 etc used chkdsk, not scandisk.
 
N

N9WOS

Thought just fixing the bad sectors would allow the drive to boot, maybe,
but no luck...

A few step by step things here.

Under win xp.
Hit the start button.
Select "my computer"
Go to "view"
Select "details"

If the "file system" header is not present.
Then right click the header bar, and put a check by the "file system"
selection.

Tell me what it list for the Maxtor drive!

(ie) fat 16, fat 32, or NTFS.
It should be FAT 16.
If not, stop and tell us.

Hit the start button again.
Right click "my computer".
Select "manage" from the list.
Go to "disk management."
You should see both of the hard drives listed there.
Make sure that it says "healthy" under the status header
for the second hard drive.

Right click the little icon for the second hard drive.
In the popup menu you should see a selection for "mark partition as active."
If it is grayed out, then the partition is set active.
If it is not grayed out, then select it to set the
primary partition on the second drive as active.

That way, it will be bootable.

Double check the drive geometry settings that I mentioned in the other post.
And then try booting from it, as the primary drive with no CD/DVD drives
hooked up.

It should work.
If it doesn't, then next step.

Get a dos 6.22 boot floppy with MSD.EXE on it, WITHOUT the Drive space
drivers.
.............................................................................................
To remove DriveSpace drivers from the floppy, do the following.
Put the floppy in the computer with Win xp running.
Bring up the floppy drive folder (A:\) on win xp.
Go into the "tools" button on the top of the folder, and
Select "folder options"
Select "View" tab
Under the "advanced settings" section
Select "show hidden files and folders"
Uncheck "Hide extensions for known file types"
Uncheck "Hide protected operating system files"
It will give you a warning but tell it that you are sure you wan to do that.
Select "OK" to get back to the A:\ folder and you should see stuff like
IO.SYS
MSD.SYS
DRVSPACE.BIN
If you see nothing with DRVSPACE on the front,
then there is no drive space drivers.
You can proceed to the next step.
If there is files with DRVSPACE on the front,
!!!!!!!!! ON THE FLOPPY DRIVE !!!!!!!!!!!
Remove everything that starts with DRVSPACE.
!!!!!!!!! ON THE FLOPPY DRIVE!!!!!!!!!!!!
.........................................................................


Boot from that floppy disk with the Maxtor drive set as primary..

You should see the raw drive as C:\
(ie) 110MB drivespace.000 file and stuff, with 8MB free.

If you don't then run MSD.EXE and check to see if the
C drive has been re listed as some other odd drive name.
If you see any drive listed under "disk drives" other than A:\ that's it
Go to the DOS prompt and see if you can change to that drive..

If you don't see any other drive then stop everything there and tell us.
You have a corrupted master boot record, or some other problem.

If you did see it as drive C:\, then boot to a DOS disk WITH the drive space
drivers on it.
And drive C should be the inside of the compressed drive.
If you can't find C drive, then run MSD.EXE to find out where it's been
relocated.
If you still see the raw uncompressed C:\ drive,
Or it has been relocated to some odd drive number with no C:\ present,
or you had the primary drive come up as some
odd drive number in the previous steps.

Then you will need to manually mount the drive.

Go to the dos laptop and copy all the files out of the dos directory
That have Drvspace on the front half, to the floppy disk WITH drivespace
drivers.
(While you are in the dos directory)
Copy DriveSpace.* a:\
Copy the drive space files to the free space of the raw uncompressed drive.
On the raw uncompressed drive, run "Drvspace/mount"
The compressed drive should show up as the next available drive letter.

If you can't find it, then run MSD.EXE to find the drive letter it assigned
to it.
You should see three drive listed.
The A:\(floppy drive), the raw drive, and the compressed drive.

If anything goes astray from the listed steps, then stop there and tell us.
 
N

N9WOS

"N9WOS kicks himself."
DUUU!!!!!!!!!

Second method.
You said you already made a copy of the Drvspace.000 file on your xp drive.
That is the compressed drive volume
You can mount the compressed volume no mater what drive it's on.

If you have any problem reading the Maxtor drive when you boot from a floppy
then
Just take that 13GB hard drive with the 300MB partition on it, and put it in
as a second
Drive to the win XP hard disk.
Boot to win xp and copy the Drvspace.000 file over to the 300Mb partition.

Then set the 13GB hard drive as primary and boot from the floppy disk
with drive space drivers, and files on it. (from other post.)
And run drive space to decompress the compressed drive volume.
Or you can put a second 300MB partition on the 13GB drive
So that you can copy contents out of the compressed drive.
 
Z

Zip

N9WOS said:
"N9WOS kicks himself."
DUUU!!!!!!!!!

Second method.
You said you already made a copy of the Drvspace.000 file on your xp
drive.
That is the compressed drive volume
You can mount the compressed volume no mater what drive it's on.

If you have any problem reading the Maxtor drive when you boot from a
floppy then
Just take that 13GB hard drive with the 300MB partition on it, and put it
in as a second
Drive to the win XP hard disk.
Boot to win xp and copy the Drvspace.000 file over to the 300Mb partition.

Then set the 13GB hard drive as primary and boot from the floppy disk
with drive space drivers, and files on it. (from other post.)
And run drive space to decompress the compressed drive volume.
Or you can put a second 300MB partition on the 13GB drive
So that you can copy contents out of the compressed drive.

Wow. Such an easy solution, the first one I tried, and it worked. What I did
is create 2 300 MB partitions on the 13 GB hard drive. Copied all 9 files
from the Maxtor to partition 1. Left partition 2 empty. Booted to DOS from
the floppy, making sure that DRVSPACE.INI, DRVSPACE.BIN and DRVSPACE.SYS
were on the floppy, and the line DEVICE=DRVSPACE.SYS was in config.sys.
Well, on the C: drive were all the files I wanted! The D: was, of course,
empty.

One last question, looking at the web, it recommends using:

D:\> xcopy C:\*.* /a /e /k

as the best way to transfer one entire drive to another (what I want to do).
However, I get an "/k is an invalid switch". What's the best way to transfer
an entire volume?

Thanks again, everyone!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top