Not Recognizing 2nd Drive

[christopher]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

I have a Gateway 98se system which has only one hard drive. I have installed
a 2nd drive as slave so I can read a drivespace compressed file from it and
move it to my XP system. After assuring the jumpers are correct (according
to mfg specs) the drive letter is not listed in the main directory. So,
looking at Set-up during boot: the drive manufacturer's name is listed as the
Primary IDE Slave, but when I press enter to look at the specs, all are
disabled except for "Auto".

On my XP system the drive is recognized and drive letter listed in directory
and will show the directory of the drive, but I can't use XP to read the
drivespace.000 compressed file.



--
Christopher

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

It's possible that you also have to change the jumper on the primary hard
drive. Some have 3 different jumper settings - one if the drive is the only
drive on the chain, another if it's the primary of two drives and the third
if it's the slave of two drives.

If your computer isn't recognizing it in the BIOS, then Windows won't
recognize it either. Your problem is most likely in the cables or jumper
settings so double-check those. When it shows up in the BIOS, it should
also show up in Windows.

PattyL

"Christopher" <Christopher@discussions.microsoft.com> wrote in message
news:E1F0DA3B-97CA-46E8-975B-F37A763534A6@microsoft.com...
>I have a Gateway 98se system which has only one hard drive. I have
>installed
> a 2nd drive as slave so I can read a drivespace compressed file from it
> and
> move it to my XP system. After assuring the jumpers are correct
> (according
> to mfg specs) the drive letter is not listed in the main directory. So,
> looking at Set-up during boot: the drive manufacturer's name is listed as
> the
> Primary IDE Slave, but when I press enter to look at the specs, all are
> disabled except for "Auto".
>
> On my XP system the drive is recognized and drive letter listed in
> directory
> and will show the directory of the drive, but I can't use XP to read the
> drivespace.000 compressed file.
>
>
>
> --
> Christopher

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Yes, as PattyL says, especially if it's a Western Digital, you may need
to change a jumper on the Master drive to say it is a Master with Slave
attached. Another possibility...

(a) START button, Programs, MS-DOS Prompt
(b) MEM /D /P
NOTE: /P causes it to PAUSE after each page. Hit any key to
continue.
(c) In the "Upper Memory Detail" section, do you see "LASTDRIVE=Z"?

Here is what mine looks like...
C:\>MEM /D /P
Upper Memory Detail:
2,288 (2K) LASTDRIVE=Z

If you don't see that, then "START button, Run, SysEdit" & look in
Config.sys for a "Lastdrive=". Remove it, & Lastdrive=Z will be set as
default by IO.sys.

........Quote C:\Windows\Config.txt........
LASTDRIVE/LASTDRIVEHIGH
=======================
This command specifies the maximum number of drives you can
access. Use the LASTDRIVEHIGH command to load the LASTDRIVE
data structures in the upper memory area. You can use these
commands only in your Config.sys file.

The value you specify represents the last
valid drive that MS-DOS is to recognize.

Syntax

LASTDRIVE=x
LASTDRIVEHIGH=x

Parameter

x
Specifies a drive letter in the range A through Z.
......EOQ......................


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Christopher" <Christopher@discussions.microsoft.com> wrote in message
news:E1F0DA3B-97CA-46E8-975B-F37A763534A6@microsoft.com...
| I have a Gateway 98se system which has only one hard drive. I have
installed
| a 2nd drive as slave so I can read a drivespace compressed file from
it and
| move it to my XP system. After assuring the jumpers are correct
(according
| to mfg specs) the drive letter is not listed in the main directory.
So,
| looking at Set-up during boot: the drive manufacturer's name is listed
as the
| Primary IDE Slave, but when I press enter to look at the specs, all
are
| disabled except for "Auto".
|
| On my XP system the drive is recognized and drive letter listed in
directory
| and will show the directory of the drive, but I can't use XP to read
the
| drivespace.000 compressed file.
|
|
|
| --
| Christopher

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

"Christopher" <Christopher@discussions.microsoft.com> wrote in message
news:E1F0DA3B-97CA-46E8-975B-F37A763534A6@microsoft.com...

> I have a Gateway 98se system which has only one hard drive. I have
installed
> a 2nd drive as slave so I can read a drivespace compressed file from it
and
> move it to my XP system. After assuring the jumpers are correct
(according

Is XP drive compression sufficiently reliable?
Win98 (i.e. Win95) drive compression has been
abandoned by most users since not reliable (e.g.
rarely survives a power failure) and hard drives
are so cheap.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

"Don Phillipson" <d.phillipson@ttrryytteell.com> wrote:

>Is XP drive compression sufficiently reliable?
>Win98 (i.e. Win95) drive compression has been
>abandoned by most users since not reliable (e.g.
>rarely survives a power failure) and hard drives
>are so cheap.

Compression in XP is a function of NTFS, not the OS. It's completely
different from the Win9x drive compression. It can be enabled for a
directory or a single file. Yes, it's entirely reliable.

--
Tim Slattery
MS MVP(DTS)
Slattery_T@bls.gov

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

"Christopher" <Christopher@discussions.microsoft.com> wrote in message
news:E1F0DA3B-97CA-46E8-975B-F37A763534A6@microsoft.com...
> I have a Gateway 98se system which has only one hard drive. I have
installed
> a 2nd drive as slave so I can read a drivespace compressed file from it
and
> move it to my XP system. After assuring the jumpers are correct
(according
> to mfg specs) the drive letter is not listed in the main directory. So,
> looking at Set-up during boot: the drive manufacturer's name is listed as
the
> Primary IDE Slave, but when I press enter to look at the specs, all are
> disabled except for "Auto".
>
> On my XP system the drive is recognized and drive letter listed in
directory
> and will show the directory of the drive, but I can't use XP to read the
> drivespace.000 compressed file.

If no drive letter shows up, then:

1 Either the drive is NOT partitioned

or

2 Windows 98SE is unable to recognize the drive
because of the scheme used to format it.

As you state that the drive contains files,
I must conclude that the drive is formatted NTFS.

Windows 98 can access files on an NTFS volume
over a network. It cannot read them locally.

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

On Fri, 12 Aug 2005 12:32:52 -0400, Tim Slattery <Slattery_T@bls.gov>
>"Don Phillipson" <d.phillipson@ttrryytteell.com> wrote:

>>Is XP drive compression sufficiently reliable?
>>Win98 (i.e. Win95) drive compression has been
>>abandoned by most users since not reliable (e.g.
>>rarely survives a power failure) and hard drives
>>are so cheap.

>Compression in XP is a function of NTFS, not the OS. It's completely
>different from the Win9x drive compression. It can be enabled for a
>directory or a single file. Yes, it's entirely reliable.

Hm. The main drawback of "old" disk compression is that if anything
went wrong, the chances of being able to recover data would be
reduced. Yes, you could access the compressed volume from a DOS boot
diskette, if that had the compression drivers, but if the internal
structure of the compressed volume was hosed, then that was it.

In contrast, NTFS cannot be read by anything other than NT, which only
runs off the HD (unless you go out of your way to set up a Bart PE
CDR, or enable the Set commands so you can use Recovery Console to
copy off files one at a time, by name, no wildcards). Andf the
internal file structure of NTFS is proprietary, and there aren't any
interactive repair tools of structure-aware file system editors.

So already, you have the drawbacks of old-style disk compression, just
by using NTFS. Another bullet won't make you any more dead.



>------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
>------------ ----- ---- --- -- - - - -

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

On Fri, 12 Aug 2005 15:42:30 -0700, "Hugh Candlin" <No@MeansNo.Com>
>"Christopher" <Christopher@discussions.microsoft.com> wrote in message

>> I have a Gateway 98se system which has only one hard drive. I have
>> installed a 2nd drive as slave so I can read a drivespace compressed file
>> from it and move it to my XP system. After assuring the jumpers are
>> correct (according to mfg specs) the drive letter is not listed

Compressed volumes are in fact single large hidden files on a "host"
volume, that are interpreted as "drive" volumes by the compression
driver if directed to do so.

When you boot off a "compressed C:", there's a D??Space.ini file in
the root of the host volume that directs the compression driver to
treat the big hidden file as "C:" while the host volume is to be
treated as a different letter, typically H:

When the same HD is not booted, but dropped into another installation
as an extra drive, the D??Space.ini is not processed. And so the
hidden file is not automatically handled as a volume.

You may be able to "mount" it as a volume via some explicit UI.

>> On my XP system the drive is recognized and drive letter listed in
>> directory and will show the directory of the drive, but I can't use XP
>> to read the drivespace.000 compressed file.

Yup. I'm not sure if XP supports Win9x-era disk compression. XP's
native NTFS compression is applied to individual files rather than the
whole volume as one big file, as the older approach did.

>Windows 98 can access files on an NTFS volume
>over a network. It cannot read them locally.

Win9x can't read NTFS at all. When accessing an NTFS volume via the
network, it doesn't have to; Win98 communicates with the XP system at
a network level, and it is XP that actually manages the NTFS volume



>------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
>------------ ----- ---- --- -- - - - -

 

[Guest]

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote in
message news:mnesf1d4rgg3anm1n2r3jrmnt2h612g4a2@4ax.com...
> On Fri, 12 Aug 2005 15:42:30 -0700, "Hugh Candlin" <No@MeansNo.Com>

> >Windows 98 can access files on an NTFS volume
> >over a network. It cannot read them locally.
>
> Win9x can't read NTFS at all. When accessing an NTFS volume via the
> network, it doesn't have to; Win98 communicates with the XP system at
> a network level, and it is XP that actually manages the NTFS volume

You slip your finger through the handle of the cup,
raise the cup to your lips, and ingest and savor
the brewed contents of the cup.

Me, I drink tea.