Assigning a Drive letter to External USB connected Hard Drive

September 29, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Frog" <frog@pond.com> wrote in message news:eWghdAgAIHA.1168@TK2MSFTNGP02.phx.gbl...

>> Bill Blanton wrote:

>>> The 120GB disk is not being read correctly and is showing as 3.5GB.

>>>

>>> Is it jumpered correctly? Do you know how to get into the BIOS setup?

>>> There may be a message when you first start the machine, such as "Press

>>> [this key] to enter BIOS....If so, check what the BIOS reports for the size of

>>> the drive and whatever "modes" are listed.

>> OOOPS, I forgot that this Secondary Slave connector was once used for CD-ROM device---and the BIOS-Main tab was set up

>> accordingly. I changed Type [CD-ROM] to Type [Auto]. It now looks like this:

>>

>>> Secondary Slave [WDC WD1200JB-00REA0]

>> Type [Auto]

>> Cylinders [1024]

>> Head [255]

>> Sector [63]

>> CHS Capacity 8422MB

>> Maximum LBA Capacity 120034MB

>>

>> Multi-Sector Transfer [Maximum]

>> SMART Monitoring [Disabled]

>> PIO Mode [4]

>> ULTRA DAM Mode [2]

>

> That corrected that variable, which resulted in too few cylinders. Unfortunately

> the partition tables as reported by the new partinfo are still the same goo.

>

>>> The first sector which contains the partition information is usually readable (AFAIK)

>>> regardless of any [incorrrect] geometry. Yours appears to be corrupt. I don't know

>>> if this has to do with the USB interface writing to the drive in a proprietary format,

>>> if it's not being recognised correctly, orif the drive is possibly faulty..

>>> How was the drive connected when you made the origianl backup?

>> It was connected via USB cable. The hard drive was housed externally at the time.

>

> I can't imagine the external's USB => ATA controller doing disk I/O any differently

> than the mainboard ATA controller, but I'm not 100% sure. Given the sector

> read errors you previously reported, I suggest you check the disk with WD's

> diags (Lifeguard) while it is still connected to the mainboard. You may have

> them on disk (CD/floppy), or you can download them from Western Digital's

> site.

>

>>> I loaded Acronis TI just to see how it works and it does write a "file" to a formatted

>>> volume. The backup image (*.tib) should be on a (visible to Windows explorer) FATx

>>> volume.

>> I am almost certain it was a *.tib file that was created when I made the backup.

>

> Meaning there should be a partition structure with a formatted volume somewhere

> on the disk.

>

I have a problem with the Western Digital Data Lifeguard Diagnostic for

Windows (file name WinDLG.zip). I un-zipped the file and then installed

it on my system. Next, I tried to run the software. It worked up to

the point where it identified the hard drives on my system. It only

hard drive found was the original internal hard drive...not the internal

(previously external) hard drive that I want to check. How do I get it

to find the problem hard drive?

Thanks,

Frog

September 29, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

> Bill Blanton wrote:

>> "Frog" <frog@pond.com> wrote in message news:eWghdAgAIHA.1168@TK2MSFTNGP02.phx.gbl...

>>> Bill Blanton wrote:

>>>> The 120GB disk is not being read correctly and is showing as 3.5GB.

>>>>

>>>> Is it jumpered correctly? Do you know how to get into the BIOS setup?

>>>> There may be a message when you first start the machine, such as "Press

>>>> [this key] to enter BIOS....If so, check what the BIOS reports for the size of

>>>> the drive and whatever "modes" are listed.

>>> OOOPS, I forgot that this Secondary Slave connector was once used for CD-ROM device---and the BIOS-Main tab was set up

>>> accordingly. I changed Type [CD-ROM] to Type [Auto]. It now looks like this:

>>>

>>>> Secondary Slave [WDC WD1200JB-00REA0]

>>> Type [Auto]

>>> Cylinders [1024]

>>> Head [255]

>>> Sector [63]

>>> CHS Capacity 8422MB

>>> Maximum LBA Capacity 120034MB

>>>

>>> Multi-Sector Transfer [Maximum]

>>> SMART Monitoring [Disabled]

>>> PIO Mode [4]

>>> ULTRA DAM Mode [2]

>>

>> That corrected that variable, which resulted in too few cylinders. Unfortunately

>> the partition tables as reported by the new partinfo are still the same goo.

>>

>>>> The first sector which contains the partition information is usually readable (AFAIK)

>>>> regardless of any [incorrrect] geometry. Yours appears to be corrupt. I don't know

>>>> if this has to do with the USB interface writing to the drive in a proprietary format,

>>>> if it's not being recognised correctly, orif the drive is possibly faulty..

>>>> How was the drive connected when you made the origianl backup?

>>> It was connected via USB cable. The hard drive was housed externally at the time.

>>

>> I can't imagine the external's USB => ATA controller doing disk I/O any differently

>> than the mainboard ATA controller, but I'm not 100% sure. Given the sector

>> read errors you previously reported, I suggest you check the disk with WD's

>> diags (Lifeguard) while it is still connected to the mainboard. You may have

>> them on disk (CD/floppy), or you can download them from Western Digital's

>> site.

>>

>>>> I loaded Acronis TI just to see how it works and it does write a "file" to a formatted

>>>> volume. The backup image (*.tib) should be on a (visible to Windows explorer) FATx

>>>> volume.

>>> I am almost certain it was a *.tib file that was created when I made the backup.

>>

>> Meaning there should be a partition structure with a formatted volume somewhere

>> on the disk.

>>

> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file and

> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard drives

> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard drive

> that I want to check. How do I get it to find the problem hard drive?

Not seeing the drive..That's not good...

Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

http://support.wdc.com/download/index.asp#windlg

You'll see detailed instructions after you make the selection.

**Note the difference between the "Quick" and the "Extended" test, regarding your

data. Start with just the "Quick test".

Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

September 29, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file and

>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>> drives

>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard drive

>> that I want to check. How do I get it to find the problem hard drive?

>

> Not seeing the drive..That's not good...

>

> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

> http://support.wdc.com/download/index.asp#windlg

>

> You'll see detailed instructions after you make the selection.

>

> **Note the difference between the "Quick" and the "Extended" test, regarding your

> data. Start with just the "Quick test".

>

> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

(floppy or CD). Running such diags from within Windows is not the prefered method.

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:u9MIWsfAIHA.3508@TK2MSFTNGP06.phx.gbl...

> The 120GB disk is not being read correctly and is showing as 3.5GB.

Wouldn't that indicate the first FDISK may have been used and not an updated one?

--

Brian A. Sesko { MS MVP_Shell/User }

Conflicts start where information lacks.

http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm

How to ask a question: http://support.microsoft.com/kb/555375

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Or Large Drive Support wasn't selected?

--

Brian A. Sesko { MS MVP_Shell/User }

Conflicts start where information lacks.

http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm

How to ask a question: http://support.microsoft.com/kb/555375

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>

>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file and

>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>> drives

>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard drive

>>> that I want to check. How do I get it to find the problem hard drive?

>> Not seeing the drive..That's not good...

>>

>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>> http://support.wdc.com/download/index.asp#windlg

>>

>> You'll see detailed instructions after you make the selection.

>>

>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>> data. Start with just the "Quick test".

>>

>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>

> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

> (floppy or CD). Running such diags from within Windows is not the prefered method.

>

Bill,

I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file

DigDiagv504f.exe, made a floppy from this .exe file, shut down my

computer, put the floppy in the A Drive, and restarted my computer. The

very first window only showed the good (always internal) 120GB hard

drive. The problem hard drive, however, was not found. I ran the Quick

Test against the good drive and it gave me the following message: Test

Completed Without Errors - Error/Status Code: 0000. Now how do I make

it find the hard drive that needs to be tested? I was thinking about

removing the one I just tested, and moving the problem hard drive to the

Primary Master position (changing the jumper in the process). Is that a

good idea or not? Anyhow, the floppy did not find the problem disk.

Help!

Frog

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

> Bill Blanton wrote:

>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>

>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file

>>>> and

>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>> drives

>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>> drive

>>>> that I want to check. How do I get it to find the problem hard drive?

>>> Not seeing the drive..That's not good...

>>>

>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>> http://support.wdc.com/download/index.asp#windlg

>>>

>>> You'll see detailed instructions after you make the selection.

>>>

>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>> data. Start with just the "Quick test".

>>>

>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>

>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>

> Bill,

> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file, shut

> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good (always

> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and it

> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard drive

> that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the Primary

> Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find the problem

> disk.

It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

out make sure the BIOS sees it before you run the test.

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Frog set the BIOS to "Auto", and the disk is correctly reporting 120GB.

>Disk 1: 14593 Cylinders, 255 Heads, 63 Sectors/Track.

"Brian A." <gonefish'n@afarawaylake> wrote in message news:eK2iiTwAIHA.1208@TK2MSFTNGP05.phx.gbl...

> Or Large Drive Support wasn't selected?

>

> --

>

> Brian A. Sesko { MS MVP_Shell/User }

> Conflicts start where information lacks.

> http://basconotw.mvps.org/

>

> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm

> How to ask a question: http://support.microsoft.com/kb/555375

>

> <snipped>

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

>> Bill Blanton wrote:

>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file

>>>>> and

>>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>>> drives

>>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>>> drive

>>>>> that I want to check. How do I get it to find the problem hard drive?

>>>> Not seeing the drive..That's not good...

>>>>

>>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>>> http://support.wdc.com/download/index.asp#windlg

>>>>

>>>> You'll see detailed instructions after you make the selection.

>>>>

>>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>>> data. Start with just the "Quick test".

>>>>

>>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>>

>> Bill,

>> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file, shut

>> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good (always

>> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and it

>> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard drive

>> that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the Primary

>> Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find the problem

>> disk.

>

> It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

> out make sure the BIOS sees it before you run the test.

>

Bill,

Moving the hard drive from the Secondary Slave position to the

Primary Master position worked. First, here is what I observed on my

first attempt last night against the "good" hard drive:

Selected Drive (only drive observed)

Model: WDC WD1200BB-23RDA0

S/N: WD-WCANN1268205

Firmware: 20.00K20

C H S: 232581 16 63

Capacity: 120 G

Drive: 0 Port: 0X1F0

Log File: DLGDIAG.LOG

Quick "Test Completed Without Errors

Error/Status Code: 0000

Now here is what I observed this morning after placing the "bad" hard

drive in the Primary Master position:

Selected Drive (only drive observed)

Model: WDC WD1200JB-00RDA0

S/N: WD-WMANN1467578

Firmware: 20.00K20

C H S: 232581 16 63

Capacity: 120 G

Drive: 0 Port: 0X1F0

Log File: DLGDIAG.LOG

Quick "Test Completed Without Errors

Error/Status Code: 0000

Extended "Test Completed Without Errors

Error/Status Code: 0000

I think it is clear that I did test both hard drives based on the

two different S/Ns.

I'm not sure what comes next, but I do have a pocket full of

thoughts and questions. For example:

The Secondary Slave position was where a CD device once lived. After

considerable help from this group--this device was thought to be faulty.

Thus, it was removed from the system. Now, I attempted to access the

"bad" 120GB hard drive from this same Secondary Slave position and this

also had problems. Could the problem be other than the device plugged

into the Secondary Slave connector--i.e., cable, motherboard

problem/setting, BIOS, etc.? I know that it was originally connected to

the system via USB port--and that originally worked before the meltdown

occurred--not after the meltdown occurred. I now have my mouse plugged

into a USB port and it appears to be working just fine.

NOTE: The Secondary Master is connected to a Plextor CD player and it

works normally. Also, the hard drive, while connected to the Secondary

Slave connector, was recognized in some ways--appeared in the BIOS,

Device Manager, and the Registry. It, for unknown reasons to me, was

not assigned a Drive letter when it was installed on the system.

Well, enough of the beginner philosophy, what comes next.

Frog

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

> Bill Blanton wrote:

>> "Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

>>> Bill Blanton wrote:

>>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file

>>>>>> and

>>>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>>>> drives

>>>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>>>> drive

>>>>>> that I want to check. How do I get it to find the problem hard drive?

>>>>> Not seeing the drive..That's not good...

>>>>>

>>>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>>>> http://support.wdc.com/download/index.asp#windlg

>>>>>

>>>>> You'll see detailed instructions after you make the selection.

>>>>>

>>>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>>>> data. Start with just the "Quick test".

>>>>>

>>>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>>>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>>>

>>> Bill,

>>> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file, shut

>>> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good (always

>>> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and it

>>> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard

>>> drive that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the

>>> Primary Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find the

>>> problem disk.

>>

>> It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

>> out make sure the BIOS sees it before you run the test.

>>

> Bill,

> Moving the hard drive from the Secondary Slave position to the Primary Master position worked. First, here is what I

> observed on my first attempt last night against the "good" hard drive:

>

> Selected Drive (only drive observed)

> Model: WDC WD1200BB-23RDA0

> S/N: WD-WCANN1268205

> Firmware: 20.00K20

> C H S: 232581 16 63

> Capacity: 120 G

> Drive: 0 Port: 0X1F0

> Log File: DLGDIAG.LOG

>

> Quick "Test Completed Without Errors

> Error/Status Code: 0000

>

> Now here is what I observed this morning after placing the "bad" hard drive in the Primary Master position:

>

> Selected Drive (only drive observed)

> Model: WDC WD1200JB-00RDA0

> S/N: WD-WMANN1467578

> Firmware: 20.00K20

> C H S: 232581 16 63

> Capacity: 120 G

> Drive: 0 Port: 0X1F0

> Log File: DLGDIAG.LOG

>

> Quick "Test Completed Without Errors

> Error/Status Code: 0000

>

> Extended "Test Completed Without Errors

> Error/Status Code: 0000

>

> I think it is clear that I did test both hard drives based on the two different S/Ns.

>

> I'm not sure what comes next, but I do have a pocket full of thoughts and questions. For example:

>

> The Secondary Slave position was where a CD device once lived. After considerable help from this group--this device was thought

> to be faulty. Thus, it was removed from the system. Now, I attempted to access the "bad" 120GB hard drive from this same

> Secondary Slave position and this also had problems. Could the problem be other than the device plugged into the Secondary Slave

> connector--i.e., cable, motherboard problem/setting, BIOS, etc.?

It's impossible for us mere mortals to test the motherboard short of swapping

it out, but you could try another cable easily enough. Is the secondary cable

80-wire/40-pin as opposed to 40-wire/40-pin?

> I know that it was originally connected to the system via USB port--and that originally worked before the meltdown occurred--not

> after the meltdown occurred. I now have my mouse plugged into a USB port and it appears to be working just fine.

What exactly was the "meltdown"?

> NOTE: The Secondary Master is connected to a Plextor CD player and it works normally. Also, the hard drive, while connected to

> the Secondary Slave connector, was recognized in some ways--appeared in the BIOS, Device Manager, and the Registry. It, for

> unknown reasons to me, was not assigned a Drive letter when it was installed on the system.

Drive letters are OS logical constructs. A completely blank HDD, or a HDD

with "unknown" partitions will not be given letter(s). According to partinfo

yours falls into the "unknown" partition type category. (it's hard to believe

that partinfo could find the drive,(as previously configured) while WD's

own diagnostics could not)

> Well, enough of the beginner philosophy, what comes next.

Let's try something else..

Get MBRWork,

ftp://terabyteunlimited.com/MBRWORK.ZIP

unzip it and put it on a 98-startup floppy.

With the drive connected as primary master

Reboot to the startup floppy and at the A:\> prompt type-

MBRWork

Choose the option to "Backup the first track."

That will put the contents of the first track in a file on the floppy with the

filename back0.bin. Zip that up and email it to me.

If you don't have a 98 boot disk you can get one here-

http://www.dehning.com/download/utilities/bootdisks/boot98.exe

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message

news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

> Bill,

> Moving the hard drive from the Secondary Slave position to the Primary Master

> position worked. First, here is what I observed on my first attempt last night

> against the "good" hard drive:

>

> Selected Drive (only drive observed)

> Model: WDC WD1200BB-23RDA0

> S/N: WD-WCANN1268205

> Firmware: 20.00K20

> C H S: 232581 16 63

> Capacity: 120 G

> Drive: 0 Port: 0X1F0

> Log File: DLGDIAG.LOG

>

> Quick "Test Completed Without Errors

> Error/Status Code: 0000

>

> Now here is what I observed this morning after placing the "bad" hard drive in the

> Primary Master position:

>

> Selected Drive (only drive observed)

> Model: WDC WD1200JB-00RDA0

> S/N: WD-WMANN1467578

> Firmware: 20.00K20

> C H S: 232581 16 63

> Capacity: 120 G

> Drive: 0 Port: 0X1F0

> Log File: DLGDIAG.LOG

>

> Quick "Test Completed Without Errors

> Error/Status Code: 0000

>

> Extended "Test Completed Without Errors

> Error/Status Code: 0000

>

> I think it is clear that I did test both hard drives based on the two

> different S/Ns.

>

> I'm not sure what comes next, but I do have a pocket full of thoughts and

> questions. For example:

>

> The Secondary Slave position was where a CD device once lived. After considerable

> help from this group--this device was thought to be faulty. Thus, it was removed

> from the system. Now, I attempted to access the "bad" 120GB hard drive from this

> same Secondary Slave position and this also had problems. Could the problem be

> other than the device plugged into the Secondary Slave connector--i.e., cable,

> motherboard problem/setting, BIOS, etc.? I know that it was originally connected

> to the system via USB port--and that originally worked before the meltdown

> occurred--not after the meltdown occurred. I now have my mouse plugged into a USB

> port and it appears to be working just fine.

>

> NOTE: The Secondary Master is connected to a Plextor CD player and it works

> normally. Also, the hard drive, while connected to the Secondary Slave connector,

> was recognized in some ways--appeared in the BIOS, Device Manager, and the

> Registry. It, for unknown reasons to me, was not assigned a Drive letter when it

> was installed on the system.

It's possible there is a problem with the cable, specifically with the connector you

used on the cable for the hard drive and before that for the Samsung CD-ROM.

However, the partinfo you gave Bill earlier still indicates a problem with at least

the way the drive is set up....the partition tables etc.

For now, I would suggest you leave the "bad" drive as the Primary Master and follow

the suggestions below:

If you have a Win98SE CD, take it and a blank floppy disk to any working computer

and insert them both, cancel setup if it starts, then browse the CD using Windows

Explorer or My Computer, to the \tools\mtsutil\fat32ebd folder, double-click the

file named "fat32ebd.exe", and follow the prompts to create a boot disk.

When done, copy the file partinfo.exe that Bill had you download earlier, to the

boot floppy. (Find the partinfo.exe file, right-click it and click Send To> 3-1/2"

Floppy A:).

Now take the boot diskette and use the it to boot your problem computer, then at the

A: prompt, type the following and press Enter:

partinfo.exe > partinfo.txt

Wait for it, as it will write the partinfo.txt to the boot floppy disk. When the

floppy light goes off and it is done, you can take the floppy to your working

computer and copy/paste the partinfo.txt file into a reply here.

PS: Also, while you still have the boot floppy in the problem computer and booted

with it (before you remove it), it might help also to run the following command and

WRITE DOWN what it reports, to post here also:

fdisk /status

--

Glen Ventura, MS MVP Shell/User, A+

http://dts-l.org/

http://dts-l.org/goodpost.htm

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

glee wrote:

> "Frog" <frog@pond.com> wrote in message

> news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

> <snipping for clarity>

>> Bill,

>> Moving the hard drive from the Secondary Slave position to the

>> Primary Master position worked. First, here is what I observed on my

>> first attempt last night against the "good" hard drive:

>>

>> Selected Drive (only drive observed)

>> Model: WDC WD1200BB-23RDA0

>> S/N: WD-WCANN1268205

>> Firmware: 20.00K20

>> C H S: 232581 16 63

>> Capacity: 120 G

>> Drive: 0 Port: 0X1F0

>> Log File: DLGDIAG.LOG

>>

>> Quick "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> Now here is what I observed this morning after placing the "bad" hard

>> drive in the Primary Master position:

>>

>> Selected Drive (only drive observed)

>> Model: WDC WD1200JB-00RDA0

>> S/N: WD-WMANN1467578

>> Firmware: 20.00K20

>> C H S: 232581 16 63

>> Capacity: 120 G

>> Drive: 0 Port: 0X1F0

>> Log File: DLGDIAG.LOG

>>

>> Quick "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> Extended "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> I think it is clear that I did test both hard drives based on the

>> two different S/Ns.

>>

>> I'm not sure what comes next, but I do have a pocket full of

>> thoughts and questions. For example:

>>

>> The Secondary Slave position was where a CD device once lived. After

>> considerable help from this group--this device was thought to be

>> faulty. Thus, it was removed from the system. Now, I attempted to

>> access the "bad" 120GB hard drive from this same Secondary Slave

>> position and this also had problems. Could the problem be other than

>> the device plugged into the Secondary Slave connector--i.e., cable,

>> motherboard problem/setting, BIOS, etc.? I know that it was

>> originally connected to the system via USB port--and that originally

>> worked before the meltdown occurred--not after the meltdown occurred.

>> I now have my mouse plugged into a USB port and it appears to be

>> working just fine.

>>

>> NOTE: The Secondary Master is connected to a Plextor CD player and it

>> works normally. Also, the hard drive, while connected to the

>> Secondary Slave connector, was recognized in some ways--appeared in

>> the BIOS, Device Manager, and the Registry. It, for unknown reasons

>> to me, was not assigned a Drive letter when it was installed on the

>> system.

>

> It's possible there is a problem with the cable, specifically with the

> connector you used on the cable for the hard drive and before that for

> the Samsung CD-ROM. However, the partinfo you gave Bill earlier still

> indicates a problem with at least the way the drive is set up....the

> partition tables etc.

>

> For now, I would suggest you leave the "bad" drive as the Primary Master

> and follow the suggestions below:

I had a problem with leaving the "bad" drive as Primary Master...see

further down.

>

> If you have a Win98SE CD, take it and a blank floppy disk to any working

> computer and insert them both, cancel setup if it starts, then browse

> the CD using Windows Explorer or My Computer, to the

> \tools\mtsutil\fat32ebd folder, double-click the file named

> "fat32ebd.exe", and follow the prompts to create a boot disk.

I attempted to use my XP computer for this task. I, however, was

confronted with a problem. This is what I saw:

D:\tools\mtsutil\fat32ebd\fat32ebd.exe

This utility creates a Fat32 boot disk.

Please insert a 1.44Mb floppy into the A: drive.

Warning! All files on the diskette will be erased.

Enter 'Y' to continue, any other key to exit: (I typed Y)

I was immediately confronted with the following window:

16 bit MS-DOS Subsystem

D:\tools\mtsutil\fat32ebd\fat32ebd.exe

An application has attempted to directly access the hard disk, which

cannot be supported. This may cause the application to function

incorrectly. Choose "Close' to terminate the application.

I clicked Close.

I next removed the "bad" disk from the 98 system and re-installed the

good disk. Here is what I saw:

This utility creates a FAT32 boot disk.

Please insert a 1.44Mb floppy into the A: drive.

Warning! All files on the diskette will be erased!

Enter 'Y' to continue, any other key to exit : (I typed Y)

Writing track 1

Boot image transferred successfully.

Preparing to extract utility files

Extracting............................................

Done!

>

> When done, copy the file partinfo.exe that Bill had you download

> earlier, to the boot floppy. (Find the partinfo.exe file, right-click

> it and click Send To> 3-1/2" Floppy A:).

I did this without a problem. At this point, I removed the "good" disk

from the 98SE computer and re-installed the "bad" disk.

>

> Now take the boot diskette and use the it to boot your problem computer,

> then at the A: prompt, type the following and press Enter:

> partinfo.exe > partinfo.txt

I did as you suggested.

>

> Wait for it, as it will write the partinfo.txt to the boot floppy disk.

> When the floppy light goes off and it is done, you can take the floppy

> to your working computer and copy/paste the partinfo.txt file into a

> reply here.

Here is the partinfo.txt file:

Partition Information Program

Sep 16 2002 - DOS32 Version

Permission is granted for this utility to be freely copied so long

as it is not modified in any way. All other rights are reserved.

PowerQuest, makers of PartitionMagic®, Drive Image and

DriveCopy, can be reached at

Voice: 801-226-6834 Web site: http://www.powerquest.com/support/

Fax: 801-226-8941 Email: help@powerquest.com

BiosExtensions: 0x2100 Subsets (0x00000005): Access EDD

EGeo 0x0000 16383 16 63 234441648 0 512

============================================================================

Disk 0: 14593 Cylinders, 255 Heads, 63 Sectors/Track.

BiosExtensions: 0x2100 Subsets (0x00000005): Access EDD

The BIOS supports INT 13h extensions for this drive.

============================ Partition Tables ==============================

Partition -----Begin---- ------End----- Start Num

Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects

---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ----------

0 0 20 [ 356 97 46] 20 [ 357 116 40] 1919950958

544437093 [Large Drive Placeholders]

53975 107 3 22329 15 41

Actual ValuesWarning: Partition boot flag expected to be 0x00 or

0x80,

not 0x20. This should not be a problem.

Error #107: Partition begins after end of disk.

ucBeginCylinder (53975) must be less than 14593.

Info: Partition didn't begin on head boundary.

ucBeginHead expected to be 0 or 1, not 107.

Info: Partition didn't begin on head boundary.

ucBeginSector expected to be 1, not 3.

Error #109: Partition ends after end of disk.

ucEndCylinder (22329) must be less than 14593.

Info: Partition didn't end on cylinder boundary.

ucEndHead expected to be 254, not 15.

Info: Partition didn't end on cylinder boundary.

ucEndSector expected to be 63, not 41.

Error #116: Starting sector of partition is inconsistent.

ulStartSect = 1919950958

Begin C,H,S = 867115118

Error #110: Number of sectors in partition is inconsistent.

ucSectors = 544437093

end - begin = 3786568549

0 1 61 [ 288 110 57] 6B [ 269 101 57] 1330184202

538976288 [Large Drive Placeholders]

17264 34 61 50813 219 8

Actual ValuesWarning: Partition boot flag expected to be 0x00 or

0x80,

not 0x61. This should not be a problem.

Error #107: Partition begins after end of disk.

ucBeginCylinder (17264) must be less than 14593.

Info: Partition didn't begin on head boundary.

ucBeginHead expected to be 0 or 1, not 34.

Info: Partition didn't begin on head boundary.

ucBeginSector expected to be 1, not 61.

Error #109: Partition ends after end of disk.

ucEndCylinder (50813) must be less than 14593.

Info: Partition didn't end on cylinder boundary.

ucEndHead expected to be 254, not 219.

Info: Partition didn't end on cylinder boundary.

ucEndSector expected to be 63, not 8.

Error #116: Starting sector of partition is inconsistent.

ulStartSect = 1330184202

Begin C,H,S = 277348362

0 2 20 [ 345 32 19] 53 [ 324 77 19] 538989391

1398362912 [Large Drive Placeholders]

33550 137 11 55058 153 54

Actual ValuesWarning: Partition boot flag expected to be 0x00 or

0x80,

not 0x20. This should not be a problem.

Error #107: Partition begins after end of disk.

ucBeginCylinder (33550) must be less than 14593.

Info: Partition didn't begin on head boundary.

ucBeginHead expected to be 0 or 1, not 137.

Info: Partition didn't begin on head boundary.

ucBeginSector expected to be 1, not 11.

Error #109: Partition ends after end of disk.

ucEndCylinder (55058) must be less than 14593.

Info: Partition didn't end on cylinder boundary.

ucEndHead expected to be 254, not 153.

Info: Partition didn't end on cylinder boundary.

ucEndSector expected to be 63, not 54.

Error #110: Number of sectors in partition is inconsistent.

ucSectors = 1398362912

end - begin = 345527072

0 3 80 [ 87 1 0] 49 [ 335 78 2] 1394627663

21337 [Large Drive Placeholders]

21275 142 3 21276 225 45

Actual Values

Error #107: Partition begins after end of disk.

ucBeginCylinder (21275) must be less than 14593.

Info: Partition didn't begin on head boundary.

ucBeginHead expected to be 0 or 1, not 142.

Info: Partition didn't begin on head boundary.

ucBeginSector expected to be 1, not 3.

Error #109: Partition ends after end of disk.

ucEndCylinder (21276) must be less than 14593.

Info: Partition didn't end on cylinder boundary.

ucEndHead expected to be 254, not 225.

Info: Partition didn't end on cylinder boundary.

ucEndSector expected to be 63, not 45.

Error #116: Starting sector of partition is inconsistent.

ulStartSect = 1394627663

Begin C,H,S = 341791823

Disk[0], Part[1330184202]: Error #113: Primary partition starting at

1330184202 overlaps previous partition.

Disk[0], Part[1394627663]: Error #113: Primary partition starting at

1394627663 overlaps previous partition.

Disk[0], Part[1919950958]: Info: MBR Partition Table not in sequential

order.

==================================================================================

Disk 0: 114471.0 Megabytes

============================= Partition Information

==============================

Volume Partition Partition Start

Total

Letter:Label Type Status Size MB Sector # Sector

Sectors

------------- --------------- -------- -------- ---------- - ----------

----------

Unallocated Pri 114470.9 None - 63

234436482

Unallocated Pri 148707.4 None - 234436545

304552846

Type 53 Pri,Boot 682794.4 0 2 538989391

1398362912

Type 6B Pri,Boot 263172.0 0 1 1330184202

538976288

Type 49 Pri,Boot 10.4 0 3 1394627663

21337

Unallocated Pri 256490.9 None - 1394650845

525293370

Type 20 Pri,Boot 265838.4 0 0 1919950958

544437093

>

> PS: Also, while you still have the boot floppy in the problem computer

> and booted with it (before you remove it), it might help also to run the

> following command and WRITE DOWN what it reports, to post here also:

> fdisk /status

>

Here are the results of the fdisk /status:

Fixed Disk Drive Status

Disk - 1

Drv -

Mbytes - 48935

Free - 48935

Usage - %

I hope I have forwarded what you were looking for...if not let me know.

Frog

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Frog" <frog@pond.com> wrote in message news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

>> Bill Blanton wrote:

>>> "Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

>>>> Bill Blanton wrote:

>>>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>>>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>>>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the file

>>>>>>> and

>>>>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>>>>> drives

>>>>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>>>>> drive

>>>>>>> that I want to check. How do I get it to find the problem hard drive?

>>>>>> Not seeing the drive..That's not good...

>>>>>>

>>>>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>>>>> http://support.wdc.com/download/index.asp#windlg

>>>>>>

>>>>>> You'll see detailed instructions after you make the selection.

>>>>>>

>>>>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>>>>> data. Start with just the "Quick test".

>>>>>>

>>>>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>>>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>>>>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>>>>

>>>> Bill,

>>>> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file, shut

>>>> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good (always

>>>> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and it

>>>> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard

>>>> drive that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the

>>>> Primary Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find the

>>>> problem disk.

>>> It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

>>> out make sure the BIOS sees it before you run the test.

>>>

>> Bill,

>> Moving the hard drive from the Secondary Slave position to the Primary Master position worked. First, here is what I

>> observed on my first attempt last night against the "good" hard drive:

>>

>> Selected Drive (only drive observed)

>> Model: WDC WD1200BB-23RDA0

>> S/N: WD-WCANN1268205

>> Firmware: 20.00K20

>> C H S: 232581 16 63

>> Capacity: 120 G

>> Drive: 0 Port: 0X1F0

>> Log File: DLGDIAG.LOG

>>

>> Quick "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> Now here is what I observed this morning after placing the "bad" hard drive in the Primary Master position:

>>

>> Selected Drive (only drive observed)

>> Model: WDC WD1200JB-00RDA0

>> S/N: WD-WMANN1467578

>> Firmware: 20.00K20

>> C H S: 232581 16 63

>> Capacity: 120 G

>> Drive: 0 Port: 0X1F0

>> Log File: DLGDIAG.LOG

>>

>> Quick "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> Extended "Test Completed Without Errors

>> Error/Status Code: 0000

>>

>> I think it is clear that I did test both hard drives based on the two different S/Ns.

>>

>> I'm not sure what comes next, but I do have a pocket full of thoughts and questions. For example:

>>

>> The Secondary Slave position was where a CD device once lived. After considerable help from this group--this device was thought

>> to be faulty. Thus, it was removed from the system. Now, I attempted to access the "bad" 120GB hard drive from this same

>> Secondary Slave position and this also had problems. Could the problem be other than the device plugged into the Secondary Slave

>> connector--i.e., cable, motherboard problem/setting, BIOS, etc.?

>

> It's impossible for us mere mortals to test the motherboard short of swapping

> it out, but you could try another cable easily enough. Is the secondary cable

> 80-wire/40-pin as opposed to 40-wire/40-pin?

It is a 40-wire/40-pin cable.

>

>> I know that it was originally connected to the system via USB port--and that originally worked before the meltdown occurred--not

>> after the meltdown occurred. I now have my mouse plugged into a USB port and it appears to be working just fine.

>

> What exactly was the "meltdown"?

The answer to that is a very long story. I took my 98SE system to the

shop to have a bigger hard drive installed (30Gb to 120GB). I also had

them partition the new hard drive (C, D, E, F and G) and transfer the C,

D, and E partition information on the 30GB drive to the C, D, and E

partitions of the new drive. I made a backup of my 30Gb hard drive on

to the external USB 120Gb hard drive just before taking it to the shop

for this work. I brought the computer home the next day at about 10-11

o'clock in the morning. I then attempted to install the Ubuntu software

onto partition G of my new internal hard drive. This installation was

not successful (can't remember exactly why). I attempted to remove

Ubuntu, and I could not get all of it removed from the system. Back to

the computer shop to have the new disk formatted and the data again read

from the 30Gb hard drive back on to the new internal 120Gb drive.

Again, I brought the computer home in the morning, and everything

started to "meltdown" at about two in the afternoon. I was receiving

error messages one after another. I started noticing that certain

programs were no longer working. At this point, I attempted to update

and run my virus scan against the system. The system would not let me

update this software. (Note: My virus scan is updated normally every 15

minutes, and I never never turn it off.) So I decided to run the virus

scan against the system--no problems were found. Late in the evening, I

decided to make a visit to Program Files. I was shocked--it no longer

existed. The next morning, when I again started my computer, I was

confronted with a list of DLL files that were either missing or corrupt.

It was about noon (roughly 24 hours after arriving home from the shop

with this computer), that I formatted this disk. One problem I see now

was the fact that the external USB connected hard drive, with my backup

on it, was turned on during this episode. I then put the 30Gb hard

drive back into the system. My bad luck continued--it went the way of

the 120Gb hard disk. Well, I (with the help from many individuals on

this discussion group) eventually got the system working again. I,

however, did this from an old (May 2006) Image for DOS backup. Well,

when it was made, I was connected to the Internet via dial-up. I had

one heck of a time making it connect to my new Verizon FiOS hookup.

That eventually worked. Next, I was faced with a problem involving one

of my two CD players. In short, it was decided that this drive was

faulty, and I removed it from the system. Now, I am trying to access

the files, photos, etc. from what was the external USB connected hard

drive. I was hoping that it would be possible to read the information

from this external USB drive to the internal drive. That is about where

we are at this point. I hope I didn't lose you in this history...maybe

you are sorry you asked about my meltdown.

>

>> NOTE: The Secondary Master is connected to a Plextor CD player and it works normally. Also, the hard drive, while connected to

>> the Secondary Slave connector, was recognized in some ways--appeared in the BIOS, Device Manager, and the Registry. It, for

>> unknown reasons to me, was not assigned a Drive letter when it was installed on the system.

>

> Drive letters are OS logical constructs. A completely blank HDD, or a HDD

> with "unknown" partitions will not be given letter(s). According to partinfo

> yours falls into the "unknown" partition type category. (it's hard to believe

> that partinfo could find the drive,(as previously configured) while WD's

> own diagnostics could not)

>

>> Well, enough of the beginner philosophy, what comes next.

>

> Let's try something else..

>

> Get MBRWork,

> ftp://terabyteunlimited.com/MBRWORK.ZIP

> unzip it and put it on a 98-startup floppy.

> With the drive connected as primary master

> Reboot to the startup floppy and at the A:\> prompt type-

>

> MBRWork

> Choose the option to "Backup the first track."

>

> That will put the contents of the first track in a file on the floppy with the

> filename back0.bin. Zip that up and email it to me.

I sent the zip file to your email address. Here is what I saw on the

screen:

MBR Partition Information (HD0):

0: 20 97 46 356 20 116 40 357 1919950958 544437093

1: 61 110 57 288 6b 101 57 269 1330184202 538976288

2: 20 32 19 345 53 77 19 324 538989391 1398362912

3: 80 1 0 87 49 78 2 335 1394627663 21337

>

> If you don't have a 98 boot disk you can get one here-

> http://www.dehning.com/download/utilities/bootdisks/boot98.exe

>

I hope I sent the data you expected.

Frog

September 30, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

It appears the thread has gotten too long for Outlook Express to handle, and is not

accepting more replies where we left off, so I am replying here.......below

"Frog" <frog@pond.com> wrote in message

news:OxU6cIt$HHA.4752@TK2MSFTNGP04.phx.gbl...

"Frog" <frog@pond.com> wrote in message

news:OiaXVI5AIHA.5360@TK2MSFTNGP03.phx.gbl...

> glee wrote:

>> "Frog" <frog@pond.com> wrote in message

>> news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

>>

>> <snipping for clarity>

>> For now, I would suggest you leave the "bad" drive as the Primary Master and

>> follow the suggestions below:

>

> I had a problem with leaving the "bad" drive as Primary Master...see further down.

>>

>> If you have a Win98SE CD, take it and a blank floppy disk to any working computer

>> and insert them both, cancel setup if it starts, then browse the CD using Windows

>> Explorer or My Computer, to the \tools\mtsutil\fat32ebd folder, double-click the

>> file named "fat32ebd.exe", and follow the prompts to create a boot disk.

>

> I attempted to use my XP computer for this task. I, however, was confronted with

> a problem. This is what I saw:

>

> D:\tools\mtsutil\fat32ebd\fat32ebd.exe

> This utility creates a Fat32 boot disk.

> Please insert a 1.44Mb floppy into the A: drive.

> Warning! All files on the diskette will be erased.

> Enter 'Y' to continue, any other key to exit: (I typed Y)

> I was immediately confronted with the following window:

> 16 bit MS-DOS Subsystem

> D:\tools\mtsutil\fat32ebd\fat32ebd.exe

> An application has attempted to directly access the hard disk, which cannot be

> supported. This may cause the application to function incorrectly. Choose

> "Close' to terminate the application.

> I clicked Close.

XP can be a pain sometimes, yes?

>

> I next removed the "bad" disk from the 98 system and re-installed the good disk.

> Here is what I saw:

>

> This utility creates a FAT32 boot disk.

> Please insert a 1.44Mb floppy into the A: drive.

> Warning! All files on the diskette will be erased!

> Enter 'Y' to continue, any other key to exit : (I typed Y)

> Writing track 1

> Boot image transferred successfully.

> Preparing to extract utility files

> Extracting............................................

> Done!

>

>>

>> When done, copy the file partinfo.exe that Bill had you download earlier, to the

>> boot floppy. (Find the partinfo.exe file, right-click it and click Send To>

>> 3-1/2" Floppy A:).

>

> I did this without a problem. At this point, I removed the "good" disk from the

> 98SE computer and re-installed the "bad" disk.

>>

>> Now take the boot diskette and use the it to boot your problem computer, then at

>> the A: prompt, type the following and press Enter:

>> partinfo.exe > partinfo.txt

>

> I did as you suggested.

>>

>> Wait for it, as it will write the partinfo.txt to the boot floppy disk. When the

>> floppy light goes off and it is done, you can take the floppy to your working

>> computer and copy/paste the partinfo.txt file into a reply here.

>

> Here is the partinfo.txt file:

>

snip of essentially the same info as the previous log

>> PS: Also, while you still have the boot floppy in the problem computer and booted

>> with it (before you remove it), it might help also to run the following command

>> and WRITE DOWN what it reports, to post here also:

>> fdisk /status

>>

>

> Here are the results of the fdisk /status:

>

> Fixed Disk Drive Status

> Disk - 1

> Drv -

> Mbytes - 48935

> Free - 48935

> Usage - %

>

> snip

Looks like you are using the original Fdisk that came with Win98, which has a

problem reporting the correct size of disks over 64MB:

http://support.microsoft.com/?kbid=263044

Also appears at least to Fdisk that there is nothing on that drive, but.....

Please email Bill with the results of your MBRWork backup, as he requested. We will

wait for his verdict. ;-)

--

Glen Ventura, MS MVP Shell/User, A+

http://dts-l.org/

http://dts-l.org/goodpost.htm

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message news:OBkkzT6AIHA.4444@TK2MSFTNGP03.phx.gbl...

> Bill Blanton wrote:

>> "Frog" <frog@pond.com> wrote in message news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

>>> Bill Blanton wrote:

>>>> "Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

>>>>> Bill Blanton wrote:

>>>>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>>>>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>>>>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the

>>>>>>>> file

>>>>>>>> and

>>>>>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>>>>>> drives

>>>>>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>>>>>> drive

>>>>>>>> that I want to check. How do I get it to find the problem hard drive?

>>>>>>> Not seeing the drive..That's not good...

>>>>>>>

>>>>>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>>>>>> http://support.wdc.com/download/index.asp#windlg

>>>>>>>

>>>>>>> You'll see detailed instructions after you make the selection.

>>>>>>>

>>>>>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>>>>>> data. Start with just the "Quick test".

>>>>>>>

>>>>>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>>>>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>>>>>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>>>>>

>>>>> Bill,

>>>>> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file,

>>>>> shut

>>>>> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good

>>>>> (always

>>>>> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and

>>>>> it

>>>>> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard

>>>>> drive that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the

>>>>> Primary Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find

>>>>> the

>>>>> problem disk.

>>>> It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

>>>> out make sure the BIOS sees it before you run the test.

>>>>

>>> Bill,

>>> Moving the hard drive from the Secondary Slave position to the Primary Master position worked. First, here is what I

>>> observed on my first attempt last night against the "good" hard drive:

>>>

>>> Selected Drive (only drive observed)

>>> Model: WDC WD1200BB-23RDA0

>>> S/N: WD-WCANN1268205

>>> Firmware: 20.00K20

>>> C H S: 232581 16 63

>>> Capacity: 120 G

>>> Drive: 0 Port: 0X1F0

>>> Log File: DLGDIAG.LOG

>>>

>>> Quick "Test Completed Without Errors

>>> Error/Status Code: 0000

>>>

>>> Now here is what I observed this morning after placing the "bad" hard drive in the Primary Master position:

>>>

>>> Selected Drive (only drive observed)

>>> Model: WDC WD1200JB-00RDA0

>>> S/N: WD-WMANN1467578

>>> Firmware: 20.00K20

>>> C H S: 232581 16 63

>>> Capacity: 120 G

>>> Drive: 0 Port: 0X1F0

>>> Log File: DLGDIAG.LOG

>>>

>>> Quick "Test Completed Without Errors

>>> Error/Status Code: 0000

>>>

>>> Extended "Test Completed Without Errors

>>> Error/Status Code: 0000

>>>

>>> I think it is clear that I did test both hard drives based on the two different S/Ns.

>>>

>>> I'm not sure what comes next, but I do have a pocket full of thoughts and questions. For example:

>>>

>>> The Secondary Slave position was where a CD device once lived. After considerable help from this group--this device was thought

>>> to be faulty. Thus, it was removed from the system. Now, I attempted to access the "bad" 120GB hard drive from this same

>>> Secondary Slave position and this also had problems. Could the problem be other than the device plugged into the Secondary

>>> Slave

>>> connector--i.e., cable, motherboard problem/setting, BIOS, etc.?

>>

>> It's impossible for us mere mortals to test the motherboard short of swapping

>> it out, but you could try another cable easily enough. Is the secondary cable

>> 80-wire/40-pin as opposed to 40-wire/40-pin?

>

> It is a 40-wire/40-pin cable.

That may have been the problem. Later ATA drives require 80-wire cables.

>>> I know that it was originally connected to the system via USB port--and that originally worked before the meltdown occurred--not

>>> after the meltdown occurred. I now have my mouse plugged into a USB port and it appears to be working just fine.

>>

>> What exactly was the "meltdown"?

>

> The answer to that is a very long story. I took my 98SE system to the shop to have a bigger hard drive installed (30Gb to 120GB).

> I also had them partition the new hard drive (C, D, E, F and G) and transfer the C, D, and E partition information on the 30GB

> drive to the C, D, and E partitions of the new drive. I made a backup of my 30Gb hard drive on to the external USB 120Gb hard

> drive just before taking it to the shop for this work. I brought the computer home the next day at about 10-11 o'clock in the

> morning. I then attempted to install the Ubuntu software onto partition G of my new internal hard drive. This installation was

> not successful (can't remember exactly why). I attempted to remove Ubuntu, and I could not get all of it removed from the system.

> Back to the computer shop to have the new disk formatted and the data again read from the 30Gb hard drive back on to the new

> internal 120Gb drive. Again, I brought the computer home in the morning, and everything started to "meltdown" at about two in the

> afternoon. I was receiving error messages one after another. I started noticing that certain programs were no longer working.

> At this point, I attempted to update and run my virus scan against the system. The system would not let me update this software.

> (Note: My virus scan is updated normally every 15 minutes, and I never never turn it off.) So I decided to run the virus scan

> against the system--no problems were found. Late in the evening, I decided to make a visit to Program Files. I was shocked--it

> no longer existed. The next morning, when I again started my computer, I was confronted with a list of DLL files that were either

> missing or corrupt. It was about noon (roughly 24 hours after arriving home from the shop with this computer), that I formatted

> this disk. One problem I see now was the fact that the external USB connected hard drive, with my backup on it, was turned on

> during this episode. I then put the 30Gb hard drive back into the system. My bad luck continued--it went the way of the 120Gb

> hard disk. Well, I (with the help from many individuals on this discussion group) eventually got the system working again. I,

> however, did this from an old (May 2006) Image for DOS backup. Well, when it was made, I was connected to the Internet via

> dial-up. I had one heck of a time making it connect to my new Verizon FiOS hookup. That eventually worked. Next, I was faced

> with a problem involving one of my two CD players. In short, it was decided that this drive was faulty, and I removed it from the

> system. Now, I am trying to access the files, photos, etc. from what was the external USB connected hard drive. I was hoping

> that it would be possible to read the information from this external USB drive to the internal drive. That is about where we are

> at this point. I hope I didn't lose you in this history...maybe you are sorry you asked about my meltdown.

:-)

>>> NOTE: The Secondary Master is connected to a Plextor CD player and it works normally. Also, the hard drive, while connected to

>>> the Secondary Slave connector, was recognized in some ways--appeared in the BIOS, Device Manager, and the Registry. It, for

>>> unknown reasons to me, was not assigned a Drive letter when it was installed on the system.

>>

>> Drive letters are OS logical constructs. A completely blank HDD, or a HDD

>> with "unknown" partitions will not be given letter(s). According to partinfo

>> yours falls into the "unknown" partition type category. (it's hard to believe

>> that partinfo could find the drive,(as previously configured) while WD's

>> own diagnostics could not)

>>

>>> Well, enough of the beginner philosophy, what comes next.

>>

>> Let's try something else..

>>

>> Get MBRWork,

>> ftp://terabyteunlimited.com/MBRWORK.ZIP

>> unzip it and put it on a 98-startup floppy.

>> With the drive connected as primary master

>> Reboot to the startup floppy and at the A:\> prompt type-

>>

>> MBRWork

>> Choose the option to "Backup the first track."

>>

>> That will put the contents of the first track in a file on the floppy with the

>> filename back0.bin. Zip that up and email it to me.

>

> I sent the zip file to your email address. Here is what I saw on the screen:

>

> MBR Partition Information (HD0):

>

> 0: 20 97 46 356 20 116 40 357 1919950958 544437093

>

> 1: 61 110 57 288 6b 101 57 269 1330184202 538976288

>

> 2: 20 32 19 345 53 77 19 324 538989391 1398362912

>

> 3: 80 1 0 87 49 78 2 335 1394627663 21337

> I hope I sent the data you expected.

Yes.

Well, we can quit playing around with partinfos. The disk has no partition structure

and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

small portion of FAT that followed looked like it chained to one big file. Probably? the

*.tib file.

You might try this. Slave the drive to the primary master (remember to set jumpers),

boot to Windows and in the device manager properties sheet, set the drive as "Removable",

and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

software such as RStudio. The problem is that everything is contained in the one large *.tib file.

And you can't recover individual files without TI mounting the file..

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

I had the same problem Glen. Nice hunh..

One solution (courtesy Mike Maltby) is to save the post as a *.nws file, open the file

in an editor and strip all the "References" except the first and last. Save. Open.

Reply to group. That's what I did in my last reply. No idea how it threads in other

readers, or google groups, but OE seems to like it ok.

"glee" <glee29@spamindspring.com> wrote in message news:OXnwJV6AIHA.3780@TK2MSFTNGP05.phx.gbl...

> It appears the thread has gotten too long for Outlook Express to handle, and is not accepting more replies where we left off, so I

> am replying here.......below

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Ahhh...thanks Bill. I'd forgotten that it was the References that were involved.

I'll do that next time.

--

Glen Ventura, MS MVP Shell/User, A+

http://dts-l.org/

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:uzOM9P8AIHA.484@TK2MSFTNGP06.phx.gbl...

>I had the same problem Glen. Nice hunh..

>

> One solution (courtesy Mike Maltby) is to save the post as a *.nws file, open the

> file

> in an editor and strip all the "References" except the first and last. Save. Open.

> Reply to group. That's what I did in my last reply. No idea how it threads in

> other

> readers, or google groups, but OE seems to like it ok.

>

> "glee" <glee29@spamindspring.com> wrote in message

> news:OXnwJV6AIHA.3780@TK2MSFTNGP05.phx.gbl...

>> It appears the thread has gotten too long for Outlook Express to handle, and is

>> not accepting more replies where we left off, so I am replying here.......below

>

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Frog" <frog@pond.com> wrote in message news:OBkkzT6AIHA.4444@TK2MSFTNGP03.phx.gbl...

>> Bill Blanton wrote:

>>> "Frog" <frog@pond.com> wrote in message news:OUOgYu2AIHA.1208@TK2MSFTNGP03.phx.gbl...

>>>> Bill Blanton wrote:

>>>>> "Frog" <frog@pond.com> wrote in message news:uqNGU0xAIHA.1168@TK2MSFTNGP02.phx.gbl...

>>>>>> Bill Blanton wrote:

>>>>>>> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:umSG9QrAIHA.3848@TK2MSFTNGP05.phx.gbl...

>>>>>>>> "Frog" <frog@pond.com> wrote in message news:OfxNEvqAIHA.5160@TK2MSFTNGP05.phx.gbl...

>>>>>>>>> I have a problem with the Western Digital Data Lifeguard Diagnostic for Windows (file name WinDLG.zip). I un-zipped the

>>>>>>>>> file

>>>>>>>>> and

>>>>>>>>> then installed it on my system. Next, I tried to run the software. It worked up to the point where it identified the hard

>>>>>>>>> drives

>>>>>>>>> on my system. It only hard drive found was the original internal hard drive...not the internal (previously external) hard

>>>>>>>>> drive

>>>>>>>>> that I want to check. How do I get it to find the problem hard drive?

>>>>>>>> Not seeing the drive..That's not good...

>>>>>>>>

>>>>>>>> Go here and select the "Data Lifeguard Diagnostics for DOS (Floppy)". (in the righthand box)

>>>>>>>> http://support.wdc.com/download/index.asp#windlg

>>>>>>>>

>>>>>>>> You'll see detailed instructions after you make the selection.

>>>>>>>>

>>>>>>>> **Note the difference between the "Quick" and the "Extended" test, regarding your

>>>>>>>> data. Start with just the "Quick test".

>>>>>>>>

>>>>>>>> Sorry, I should have been more clear that you want the "Diagnostics", not the "Tools".

>>>>>>> Ok, I see you did have the "Diags". I'd still use one of the bootable DOS versions

>>>>>>> (floppy or CD). Running such diags from within Windows is not the prefered method.

>>>>>>>

>>>>>> Bill,

>>>>>> I downloaded "Data Lifeguard Diagnostic for DOS (Floppy)" - file DigDiagv504f.exe, made a floppy from this .exe file,

>>>>>> shut

>>>>>> down my computer, put the floppy in the A Drive, and restarted my computer. The very first window only showed the good

>>>>>> (always

>>>>>> internal) 120GB hard drive. The problem hard drive, however, was not found. I ran the Quick Test against the good drive and

>>>>>> it

>>>>>> gave me the following message: Test Completed Without Errors - Error/Status Code: 0000. Now how do I make it find the hard

>>>>>> drive that needs to be tested? I was thinking about removing the one I just tested, and moving the problem hard drive to the

>>>>>> Primary Master position (changing the jumper in the process). Is that a good idea or not? Anyhow, the floppy did not find

>>>>>> the

>>>>>> problem disk.

>>>>> It wouldn't hurt to try it. Does the BIOS still see the drive? If you swap it

>>>>> out make sure the BIOS sees it before you run the test.

>>>>>

>>>> Bill,

>>>> Moving the hard drive from the Secondary Slave position to the Primary Master position worked. First, here is what I

>>>> observed on my first attempt last night against the "good" hard drive:

>>>>

>>>> Selected Drive (only drive observed)

>>>> Model: WDC WD1200BB-23RDA0

>>>> S/N: WD-WCANN1268205

>>>> Firmware: 20.00K20

>>>> C H S: 232581 16 63

>>>> Capacity: 120 G

>>>> Drive: 0 Port: 0X1F0

>>>> Log File: DLGDIAG.LOG

>>>>

>>>> Quick "Test Completed Without Errors

>>>> Error/Status Code: 0000

>>>>

>>>> Now here is what I observed this morning after placing the "bad" hard drive in the Primary Master position:

>>>>

>>>> Selected Drive (only drive observed)

>>>> Model: WDC WD1200JB-00RDA0

>>>> S/N: WD-WMANN1467578

>>>> Firmware: 20.00K20

>>>> C H S: 232581 16 63

>>>> Capacity: 120 G

>>>> Drive: 0 Port: 0X1F0

>>>> Log File: DLGDIAG.LOG

>>>>

>>>> Quick "Test Completed Without Errors

>>>> Error/Status Code: 0000

>>>>

>>>> Extended "Test Completed Without Errors

>>>> Error/Status Code: 0000

>>>>

>>>> I think it is clear that I did test both hard drives based on the two different S/Ns.

>>>>

>>>> I'm not sure what comes next, but I do have a pocket full of thoughts and questions. For example:

>>>>

>>>> The Secondary Slave position was where a CD device once lived. After considerable help from this group--this device was thought

>>>> to be faulty. Thus, it was removed from the system. Now, I attempted to access the "bad" 120GB hard drive from this same

>>>> Secondary Slave position and this also had problems. Could the problem be other than the device plugged into the Secondary

>>>> Slave

>>>> connector--i.e., cable, motherboard problem/setting, BIOS, etc.?

>>> It's impossible for us mere mortals to test the motherboard short of swapping

>>> it out, but you could try another cable easily enough. Is the secondary cable

>>> 80-wire/40-pin as opposed to 40-wire/40-pin?

>> It is a 40-wire/40-pin cable.

>

> That may have been the problem. Later ATA drives require 80-wire cables.

>

>>>> I know that it was originally connected to the system via USB port--and that originally worked before the meltdown occurred--not

>>>> after the meltdown occurred. I now have my mouse plugged into a USB port and it appears to be working just fine.

>>> What exactly was the "meltdown"?

>> The answer to that is a very long story. I took my 98SE system to the shop to have a bigger hard drive installed (30Gb to 120GB).

>> I also had them partition the new hard drive (C, D, E, F and G) and transfer the C, D, and E partition information on the 30GB

>> drive to the C, D, and E partitions of the new drive. I made a backup of my 30Gb hard drive on to the external USB 120Gb hard

>> drive just before taking it to the shop for this work. I brought the computer home the next day at about 10-11 o'clock in the

>> morning. I then attempted to install the Ubuntu software onto partition G of my new internal hard drive. This installation was

>> not successful (can't remember exactly why). I attempted to remove Ubuntu, and I could not get all of it removed from the system.

>> Back to the computer shop to have the new disk formatted and the data again read from the 30Gb hard drive back on to the new

>> internal 120Gb drive. Again, I brought the computer home in the morning, and everything started to "meltdown" at about two in the

>> afternoon. I was receiving error messages one after another. I started noticing that certain programs were no longer working.

>> At this point, I attempted to update and run my virus scan against the system. The system would not let me update this software.

>> (Note: My virus scan is updated normally every 15 minutes, and I never never turn it off.) So I decided to run the virus scan

>> against the system--no problems were found. Late in the evening, I decided to make a visit to Program Files. I was shocked--it

>> no longer existed. The next morning, when I again started my computer, I was confronted with a list of DLL files that were either

>> missing or corrupt. It was about noon (roughly 24 hours after arriving home from the shop with this computer), that I formatted

>> this disk. One problem I see now was the fact that the external USB connected hard drive, with my backup on it, was turned on

>> during this episode. I then put the 30Gb hard drive back into the system. My bad luck continued--it went the way of the 120Gb

>> hard disk. Well, I (with the help from many individuals on this discussion group) eventually got the system working again. I,

>> however, did this from an old (May 2006) Image for DOS backup. Well, when it was made, I was connected to the Internet via

>> dial-up. I had one heck of a time making it connect to my new Verizon FiOS hookup. That eventually worked. Next, I was faced

>> with a problem involving one of my two CD players. In short, it was decided that this drive was faulty, and I removed it from the

>> system. Now, I am trying to access the files, photos, etc. from what was the external USB connected hard drive. I was hoping

>> that it would be possible to read the information from this external USB drive to the internal drive. That is about where we are

>> at this point. I hope I didn't lose you in this history...maybe you are sorry you asked about my meltdown.

>

> :-)

>

>>>> NOTE: The Secondary Master is connected to a Plextor CD player and it works normally. Also, the hard drive, while connected to

>>>> the Secondary Slave connector, was recognized in some ways--appeared in the BIOS, Device Manager, and the Registry. It, for

>>>> unknown reasons to me, was not assigned a Drive letter when it was installed on the system.

>>> Drive letters are OS logical constructs. A completely blank HDD, or a HDD

>>> with "unknown" partitions will not be given letter(s). According to partinfo

>>> yours falls into the "unknown" partition type category. (it's hard to believe

>>> that partinfo could find the drive,(as previously configured) while WD's

>>> own diagnostics could not)

>>>

>>>> Well, enough of the beginner philosophy, what comes next.

>>> Let's try something else..

>>>

>>> Get MBRWork,

>>> ftp://terabyteunlimited.com/MBRWORK.ZIP

>>> unzip it and put it on a 98-startup floppy.

>>> With the drive connected as primary master

>>> Reboot to the startup floppy and at the A:\> prompt type-

>>>

>>> MBRWork

>>> Choose the option to "Backup the first track."

>>>

>>> That will put the contents of the first track in a file on the floppy with the

>>> filename back0.bin. Zip that up and email it to me.

>> I sent the zip file to your email address. Here is what I saw on the screen:

>>

>> MBR Partition Information (HD0):

>>

>> 0: 20 97 46 356 20 116 40 357 1919950958 544437093

>>

>> 1: 61 110 57 288 6b 101 57 269 1330184202 538976288

>>

>> 2: 20 32 19 345 53 77 19 324 538989391 1398362912

>>

>> 3: 80 1 0 87 49 78 2 335 1394627663 21337

>

>> I hope I sent the data you expected.

>

> Yes.

>

> Well, we can quit playing around with partinfos. The disk has no partition structure

> and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

> boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

> small portion of FAT that followed looked like it chained to one big file. Probably? the

> *.tib file.

>

> You might try this. Slave the drive to the primary master (remember to set jumpers),

> boot to Windows and in the device manager properties sheet, set the drive as "Removable",

> and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

> software such as RStudio. The problem is that everything is contained in the one large *.tib file.

> And you can't recover individual files without TI mounting the file..

>

Bill,

Some good news---the "bad" hard drive is in the Primary Slave

position, and it now has Drive H assigned to this device. Yes, I can

now see two files in Windows Explorer that are loaded on the "bad" hard

disk as follows:

MyBackup1.tib Size: 4,194,300KB Type: TrueImage Backup Archive

Modified: 8/28/07 5:58PM

MyBackup2.tib Size: 1,918,786KB Type: TrueImage Backup Archive

Modified: 8/28/07 6:39PM

I opened the Acronis software, and it could also see Drive H with its

two files. So far, I have only done a little up-front exploring in

Acronis. I decided to "Explore Image". This gave me the following:

Welcome to the Explore Image Wizard!

This wizard will help you to explore a previously created image archive.

You will be able to assign temporary drive letters to the partition

images and easily access these partitions as ordinary logical drives.

I clicked Next.

The window that appeared had the following information on it:

Left side window:

Removable Disk (H);

MyBackup1.tib

MyBackup2.tib

I highlighted MyBackup1.tib.

Right side window:

MyBackup1.tib

No description is available for this image archive.

Date: Tuesday, August 28, 2007 4:28 27 PM

Size 5.83 GB

Under this information are six small squares with the following information:

1 -1118GB

C: - 2...

d: - 2...

E: - 2...

F: - 2...

G: - 25...

Across the bottom of the window is:

File name: H:\MyBackup1.tib

Tiles of type: Image Archives (*.tib)

The left side of the window for MyBackup2.tib is the same as above.

The right side of this window is also the same above except it included

another line as follows: This is volume 2 of multifile archive MyBackup.tib.

The bottom of the page was the same as above.

When I clicked the Next button at the bottom of the page, I saw:

Explore Image Wizard

Assigning Logical Drive Letters

You can assign logical drive letters to the partitions from the

image archive you have chosen.

The partitions from the image archive you have chosen will have

temporary logical drive letters shown in the hard disk graphical layout

below. To change the drive letter, select a partition then, choose

another drive letter in the combo box below the hard disk graphical

layout. Choose "Do not mount" in the combo box, if you do not want to

assign a drive letter to the selected partition. To select a partition

place the mouse pointer over it, and then click the left mouse button.

The window then displayed a table as follows:

Partition - Flags - Capacity - Free Space - Type

Disk 1

Each of the following lines was preceded by a box with a check mark in it.

Charlie (J) - PriAct - 21.49GB - 18.25GB - Fat32(LBA)

Delta (K) - - 21.49GB - 18.86GB - Fat32

Echo (L) - - 21.49GB - 19.64GB - Fat32

FAT32 (M) - - 21.49GB - 21.48GB - Fat32

Fat32(N) - - 25.84GB - 25.83GB - Fat32

I next decided to click the Restore Image button. It gave me the

following window:

Welcome to the Restore Image Wizard!

This wizard will help you to recover lost or corrupted partitions. You

will be able to recover a partition or the whole hard disk drive from

the image archive you have previously created.

I clicked Next and got the following error message:

Error

E000101F9: Cannot get write access to the hard disk drive(s).

Another Acronis application has write access to the hard disk drive(s).

Only one Acronis application can have write access to the hard disk

drive at a time.

I clicked OK, and exited Acronis, since I did not understand the error

message.

My last action before writing this message was to attempt to make CDs of

the two files. Even this stopped me with the following message:

Easy CD Creator

The operation cannot be completed because the file "MyBackup1.tib" is

too large to fit on one track. Increase the amount of usable temp space

and try again.

Well, this stopped me in my track; since I don't understand the message.

This is where I stopped. I decided that I needed to understand how to

restore each of the partitions back to the "good" hard disk before going

any further. I probably will not restore the Charlie partition, because

it does not include my data files.

I very much appreciate your help and patience during this problem-

solving episode. I would have been totally dead in the water, if it

were not for the help of you and others on this discussion group.

Thanks so very much for your time and expertise.

Well, I am off to read about Acronis.

Frog

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message news:ulkQAFFBIHA.1168@TK2MSFTNGP02.phx.gbl...

> Bill Blanton wrote:

>

>> Well, we can quit playing around with partinfos. The disk has no partition structure

>> and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

>> boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

>> small portion of FAT that followed looked like it chained to one big file. Probably? the

>> *.tib file.

>>

>> You might try this. Slave the drive to the primary master (remember to set jumpers),

>> boot to Windows and in the device manager properties sheet, set the drive as "Removable",

>> and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

>> software such as RStudio. The problem is that everything is contained in the one large *.tib file.

>> And you can't recover individual files without TI mounting the file..

>>

> Bill,

>

> Some good news---the "bad" hard drive is in the Primary Slave position, and it now has Drive H assigned to this device. Yes,

> I can now see two files in Windows Explorer that are loaded on the "bad" hard disk as follows:

>

> MyBackup1.tib Size: 4,194,300KB Type: TrueImage Backup Archive Modified: 8/28/07 5:58PM

>

> MyBackup2.tib Size: 1,918,786KB Type: TrueImage Backup Archive Modified: 8/28/07 6:39PM

>

> I opened the Acronis software, and it could also see Drive H with its two files. So far, I have only done a little up-front

> exploring in Acronis. I decided to "Explore Image". This gave me the following:

>

> Welcome to the Explore Image Wizard!

> This wizard will help you to explore a previously created image archive. You will be able to assign temporary drive letters to the

> partition images and easily access these partitions as ordinary logical drives.

> I clicked Next.

> The window that appeared had the following information on it:

> Left side window:

> Removable Disk (H);

> MyBackup1.tib

> MyBackup2.tib

> I highlighted MyBackup1.tib.

> Right side window:

> MyBackup1.tib

> No description is available for this image archive.

> Date: Tuesday, August 28, 2007 4:28 27 PM

> Size 5.83 GB

> Under this information are six small squares with the following information:

> 1 -1118GB

> C: - 2...

> d: - 2...

> E: - 2...

> F: - 2...

> G: - 25...

> Across the bottom of the window is:

> File name: H:\MyBackup1.tib

> Tiles of type: Image Archives (*.tib)

>

> The left side of the window for MyBackup2.tib is the same as above.

> The right side of this window is also the same above except it included another line as follows: This is volume 2 of multifile

> archive MyBackup.tib.

> The bottom of the page was the same as above.

>

> When I clicked the Next button at the bottom of the page, I saw:

>

> Explore Image Wizard

> Assigning Logical Drive Letters

> You can assign logical drive letters to the partitions from the image archive you have chosen.

> The partitions from the image archive you have chosen will have temporary logical drive letters shown in the hard disk

> graphical layout below. To change the drive letter, select a partition then, choose another drive letter in the combo box below

> the hard disk graphical layout. Choose "Do not mount" in the combo box, if you do not want to assign a drive letter to the

> selected partition. To select a partition place the mouse pointer over it, and then click the left mouse button.

> The window then displayed a table as follows:

> Partition - Flags - Capacity - Free Space - Type

> Disk 1

> Each of the following lines was preceded by a box with a check mark in it.

> Charlie (J) - PriAct - 21.49GB - 18.25GB - Fat32(LBA)

> Delta (K) - - 21.49GB - 18.86GB - Fat32

> Echo (L) - - 21.49GB - 19.64GB - Fat32

> FAT32 (M) - - 21.49GB - 21.48GB - Fat32

> Fat32(N) - - 25.84GB - 25.83GB - Fat32

>

> I next decided to click the Restore Image button. It gave me the following window:

>

> Welcome to the Restore Image Wizard!

> This wizard will help you to recover lost or corrupted partitions. You will be able to recover a partition or the whole hard disk

> drive from the image archive you have previously created.

> I clicked Next and got the following error message:

>

> Error

> E000101F9: Cannot get write access to the hard disk drive(s).

> Another Acronis application has write access to the hard disk drive(s). Only one Acronis application can have write access to the

> hard disk drive at a time.

> I clicked OK, and exited Acronis, since I did not understand the error message.

>

> My last action before writing this message was to attempt to make CDs of the two files. Even this stopped me with the following

> message:

>

> Easy CD Creator

> The operation cannot be completed because the file "MyBackup1.tib" is too large to fit on one track. Increase the amount of

> usable temp space and try again.

>

> Well, this stopped me in my track; since I don't understand the message.

>

> This is where I stopped. I decided that I needed to understand how to restore each of the partitions back to the "good" hard disk

> before going any further. I probably will not restore the Charlie partition, because it does not include my data files.

>

> I very much appreciate your help and patience during this problem- solving episode. I would have been totally dead in the water,

> if it were not for the help of you and others on this discussion group. Thanks so very much for your time and expertise.

>

> Well, I am off to read about Acronis.

>

Do you have room on your other HDD? If so, you might copy them off to there.

Can you run the Restore wiz without first running the Acronis explorer. I

don't use Acronis, so don't really know what's going on. Does Acronis have

a forum or email support? Or Glen might have an idea.

BTW, I'd like to know just for my own knowledge base. Is the drive checked off as

"Removable" in Device Manager?

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:OJO17bGBIHA.3848@TK2MSFTNGP05.phx.gbl...

> "Frog" <frog@pond.com> wrote in message news:ulkQAFFBIHA.1168@TK2MSFTNGP02.phx.gbl...

>> Bill Blanton wrote:

>

>>

>>> Well, we can quit playing around with partinfos. The disk has no partition structure

>>> and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

>>> boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

>>> small portion of FAT that followed looked like it chained to one big file. Probably? the

>>> *.tib file.

>>>

>>> You might try this. Slave the drive to the primary master (remember to set jumpers),

>>> boot to Windows and in the device manager properties sheet, set the drive as "Removable",

>>> and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

>>> software such as RStudio. The problem is that everything is contained in the one large *.tib file.

>>> And you can't recover individual files without TI mounting the file..

>>>

>> Bill,

>>

>> Some good news---the "bad" hard drive is in the Primary Slave position, and it now has Drive H assigned to this device.

>> Yes, I can now see two files in Windows Explorer that are loaded on the "bad" hard disk as follows:

>>

>> MyBackup1.tib Size: 4,194,300KB Type: TrueImage Backup Archive Modified: 8/28/07 5:58PM

>>

>> MyBackup2.tib Size: 1,918,786KB Type: TrueImage Backup Archive Modified: 8/28/07 6:39PM

>>

>> I opened the Acronis software, and it could also see Drive H with its two files. So far, I have only done a little up-front

>> exploring in Acronis. I decided to "Explore Image". This gave me the following:

>>

>> Welcome to the Explore Image Wizard!

>> This wizard will help you to explore a previously created image archive. You will be able to assign temporary drive letters to

>> the partition images and easily access these partitions as ordinary logical drives.

>> I clicked Next.

>> The window that appeared had the following information on it:

>> Left side window:

>> Removable Disk (H);

>> MyBackup1.tib

>> MyBackup2.tib

>> I highlighted MyBackup1.tib.

>> Right side window:

>> MyBackup1.tib

>> No description is available for this image archive.

>> Date: Tuesday, August 28, 2007 4:28 27 PM

>> Size 5.83 GB

>> Under this information are six small squares with the following information:

>> 1 -1118GB

>> C: - 2...

>> d: - 2...

>> E: - 2...

>> F: - 2...

>> G: - 25...

>> Across the bottom of the window is:

>> File name: H:\MyBackup1.tib

>> Tiles of type: Image Archives (*.tib)

>>

>> The left side of the window for MyBackup2.tib is the same as above.

>> The right side of this window is also the same above except it included another line as follows: This is volume 2 of multifile

>> archive MyBackup.tib.

>> The bottom of the page was the same as above.

>>

>> When I clicked the Next button at the bottom of the page, I saw:

>>

>> Explore Image Wizard

>> Assigning Logical Drive Letters

>> You can assign logical drive letters to the partitions from the image archive you have chosen.

>> The partitions from the image archive you have chosen will have temporary logical drive letters shown in the hard disk

>> graphical layout below. To change the drive letter, select a partition then, choose another drive letter in the combo box below

>> the hard disk graphical layout. Choose "Do not mount" in the combo box, if you do not want to assign a drive letter to the

>> selected partition. To select a partition place the mouse pointer over it, and then click the left mouse button.

>> The window then displayed a table as follows:

>> Partition - Flags - Capacity - Free Space - Type

>> Disk 1

>> Each of the following lines was preceded by a box with a check mark in it.

>> Charlie (J) - PriAct - 21.49GB - 18.25GB - Fat32(LBA)

>> Delta (K) - - 21.49GB - 18.86GB - Fat32

>> Echo (L) - - 21.49GB - 19.64GB - Fat32

>> FAT32 (M) - - 21.49GB - 21.48GB - Fat32

>> Fat32(N) - - 25.84GB - 25.83GB - Fat32

>>

>> I next decided to click the Restore Image button. It gave me the following window:

>>

>> Welcome to the Restore Image Wizard!

>> This wizard will help you to recover lost or corrupted partitions. You will be able to recover a partition or the whole hard

>> disk drive from the image archive you have previously created.

>> I clicked Next and got the following error message:

>>

>> Error

>> E000101F9: Cannot get write access to the hard disk drive(s).

>> Another Acronis application has write access to the hard disk drive(s). Only one Acronis application can have write access to the

>> hard disk drive at a time.

>> I clicked OK, and exited Acronis, since I did not understand the error message.

>>

>> My last action before writing this message was to attempt to make CDs of the two files. Even this stopped me with the following

>> message:

>>

>> Easy CD Creator

>> The operation cannot be completed because the file "MyBackup1.tib" is too large to fit on one track. Increase the amount of

>> usable temp space and try again.

>>

>> Well, this stopped me in my track; since I don't understand the message.

>>

>> This is where I stopped. I decided that I needed to understand how to restore each of the partitions back to the "good" hard

>> disk before going any further. I probably will not restore the Charlie partition, because it does not include my data files.

>>

>> I very much appreciate your help and patience during this problem- solving episode. I would have been totally dead in the water,

>> if it were not for the help of you and others on this discussion group. Thanks so very much for your time and expertise.

>>

>> Well, I am off to read about Acronis.

>>

>

> Do you have room on your other HDD? If so, you might copy them off to there.

>

> Can you run the Restore wiz without first running the Acronis explorer. I

> don't use Acronis, so don't really know what's going on. Does Acronis have

> a forum or email support? Or Glen might have an idea.

>

> BTW, I'd like to know just for my own knowledge base. Is the drive checked off as

> "Removable" in Device Manager?

You might also want to check the startup axis for any Acronis services. Start > Run... > Msconfig

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Frog" <frog@pond.com> wrote in message news:ulkQAFFBIHA.1168@TK2MSFTNGP02.phx.gbl...

>> Bill Blanton wrote:

>

>>> Well, we can quit playing around with partinfos. The disk has no partition structure

>>> and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

>>> boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

>>> small portion of FAT that followed looked like it chained to one big file. Probably? the

>>> *.tib file.

>>>

>>> You might try this. Slave the drive to the primary master (remember to set jumpers),

>>> boot to Windows and in the device manager properties sheet, set the drive as "Removable",

>>> and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

>>> software such as RStudio. The problem is that everything is contained in the one large *.tib file.

>>> And you can't recover individual files without TI mounting the file..

>>>

>> Bill,

>>

>> Some good news---the "bad" hard drive is in the Primary Slave position, and it now has Drive H assigned to this device. Yes,

>> I can now see two files in Windows Explorer that are loaded on the "bad" hard disk as follows:

>>

>> MyBackup1.tib Size: 4,194,300KB Type: TrueImage Backup Archive Modified: 8/28/07 5:58PM

>>

>> MyBackup2.tib Size: 1,918,786KB Type: TrueImage Backup Archive Modified: 8/28/07 6:39PM

>>

>> I opened the Acronis software, and it could also see Drive H with its two files. So far, I have only done a little up-front

>> exploring in Acronis. I decided to "Explore Image". This gave me the following:

>>

>> Welcome to the Explore Image Wizard!

>> This wizard will help you to explore a previously created image archive. You will be able to assign temporary drive letters to the

>> partition images and easily access these partitions as ordinary logical drives.

>> I clicked Next.

>> The window that appeared had the following information on it:

>> Left side window:

>> Removable Disk (H);

>> MyBackup1.tib

>> MyBackup2.tib

>> I highlighted MyBackup1.tib.

>> Right side window:

>> MyBackup1.tib

>> No description is available for this image archive.

>> Date: Tuesday, August 28, 2007 4:28 27 PM

>> Size 5.83 GB

>> Under this information are six small squares with the following information:

>> 1 -1118GB

>> C: - 2...

>> d: - 2...

>> E: - 2...

>> F: - 2...

>> G: - 25...

>> Across the bottom of the window is:

>> File name: H:\MyBackup1.tib

>> Tiles of type: Image Archives (*.tib)

>>

>> The left side of the window for MyBackup2.tib is the same as above.

>> The right side of this window is also the same above except it included another line as follows: This is volume 2 of multifile

>> archive MyBackup.tib.

>> The bottom of the page was the same as above.

>>

>> When I clicked the Next button at the bottom of the page, I saw:

>>

>> Explore Image Wizard

>> Assigning Logical Drive Letters

>> You can assign logical drive letters to the partitions from the image archive you have chosen.

>> The partitions from the image archive you have chosen will have temporary logical drive letters shown in the hard disk

>> graphical layout below. To change the drive letter, select a partition then, choose another drive letter in the combo box below

>> the hard disk graphical layout. Choose "Do not mount" in the combo box, if you do not want to assign a drive letter to the

>> selected partition. To select a partition place the mouse pointer over it, and then click the left mouse button.

>> The window then displayed a table as follows:

>> Partition - Flags - Capacity - Free Space - Type

>> Disk 1

>> Each of the following lines was preceded by a box with a check mark in it.

>> Charlie (J) - PriAct - 21.49GB - 18.25GB - Fat32(LBA)

>> Delta (K) - - 21.49GB - 18.86GB - Fat32

>> Echo (L) - - 21.49GB - 19.64GB - Fat32

>> FAT32 (M) - - 21.49GB - 21.48GB - Fat32

>> Fat32(N) - - 25.84GB - 25.83GB - Fat32

>>

>> I next decided to click the Restore Image button. It gave me the following window:

>>

>> Welcome to the Restore Image Wizard!

>> This wizard will help you to recover lost or corrupted partitions. You will be able to recover a partition or the whole hard disk

>> drive from the image archive you have previously created.

>> I clicked Next and got the following error message:

>>

>> Error

>> E000101F9: Cannot get write access to the hard disk drive(s).

>> Another Acronis application has write access to the hard disk drive(s). Only one Acronis application can have write access to the

>> hard disk drive at a time.

>> I clicked OK, and exited Acronis, since I did not understand the error message.

>>

>> My last action before writing this message was to attempt to make CDs of the two files. Even this stopped me with the following

>> message:

>>

>> Easy CD Creator

>> The operation cannot be completed because the file "MyBackup1.tib" is too large to fit on one track. Increase the amount of

>> usable temp space and try again.

>>

>> Well, this stopped me in my track; since I don't understand the message.

>>

>> This is where I stopped. I decided that I needed to understand how to restore each of the partitions back to the "good" hard disk

>> before going any further. I probably will not restore the Charlie partition, because it does not include my data files.

>>

>> I very much appreciate your help and patience during this problem- solving episode. I would have been totally dead in the water,

>> if it were not for the help of you and others on this discussion group. Thanks so very much for your time and expertise.

>>

>> Well, I am off to read about Acronis.

>>

>

> Do you have room on your other HDD? If so, you might copy them off to there.

>

> Can you run the Restore wiz without first running the Acronis explorer. I

> don't use Acronis, so don't really know what's going on. Does Acronis have

> a forum or email support? Or Glen might have an idea.

>

> BTW, I'd like to know just for my own knowledge base. Is the drive checked off as

> "Removable" in Device Manager?

Yes, it is checked. Here is what the Device Manager information looks

like for this device:

General Tab:

Generic Disk Type47

Device type: Disk drives

Manufacturer: (Standard disk drives)

Hardware version: Not available

Device status: This device is working properly.

Settings Tab:

Generic IDE Disk Type 47

Target ID: Grayed out

Local unit number: Grayed out

Firmware version: Grayed out

Options:

Disconnect: Grayed out

Sync Data transfer: Grayed out

Auto insert notification: Grayed out

Int 13 unit: Grayed out

Removable: Checked

DMA: Checked

Current drive assignment: H

Reserved drive letter: Nothing selected

End drive letter: Nothing selected

Driver Tab

Generic IDE Type47

Provider: (Standard disk drives)

Date:" 4-23-1999

No driver files are required or have been loaded for this device. To

update the driver files for this device, click Update Driver.

>

Frog

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message

news:OJO17bGBIHA.3848@TK2MSFTNGP05.phx.gbl...

> snip

>

> Can you run the Restore wiz without first running the Acronis explorer. I

> don't use Acronis, so don't really know what's going on. Does Acronis have

> a forum or email support? Or Glen might have an idea.

There's no need or reason I can see to run Acronis Explorer unless you just want to

look at the backups as if they were files and folders, in an Explorer-type

interface, or to access and restore individual files or folders.

It is not used when restoring an entire image....the Acroinis Explorer being in use

is probably the "other" Acronis app holding the image in use and preventing a

restore from proceeding anyway.

Note that Frog reports 2 backup (.tib) files and the second one states:

This is volume 2 of multifile archive MyBackup.tib

I presume from this that the two images together comprise the backup, perhaps as a

full and an incremental backup, or a full and a differential backup.

From the Help file here, under the Recovery heading:

<quote>

If you are to restore files from an incremental backup, Acronis True Image

Enterprise Server will suggest that you select one of successive incremental

archives by date/time of its creation. Thus, you can return the files/folders to a

certain moment, often called a point of restore.

Note

.. To restore data from an incremental backup, you must have all previous incremental

backup archives and the initial complete archive. If any of successive archive is

missing, restoration is impossible.

.. To restore data from a differential backup, you must have the initial full backup

as well.

</quote>

Further:

<quote>

Restore disks or partitions - select this option if you want to restore disks and/or

partitions from the disk backup; restoration of a system partition requires

rebooting and PC will be unavailable for using during the restoration.To restore a

partition (disk) from an image, Acronis True Image Workstation must obtain exclusive

access to the target partition (disk). This means no other applications can access

it at that time. If you receive a message stating that the partition (disk) can not

be blocked, close applications that use this partition (disk) and start over.

</quote>

The procedure:

<quote>

Select the archive to restore.

Select the hard disk for the restoration and click Next to continue.

If there are any partitions on the new disk, they must be deleted first.Choose

between:

.. Yes, I want to delete all the partitions on the destination hard disk drive before

restoring - all existing partitions will be deleted and all their data will be lost.

.. No, I do not want to delete partitions - no existing partition will be deleted,

discontinuing the restoring operation. You will only be able to cancel this

operation and return to select another disk.

To continue, select the first choice and click Next.

You may restore data to their initial location, to another disk/partition or to an

unallocated space. The target partition should be at least the same size as the

uncompressed archive data.To select a location:

.. Click on the partition to select it.

You can restore several partitions during a single task.To restore another

partition:

.. Select Yes, I want to restore another partition or hard disk drive. After this,

you will see the partition selection window again and will have to repeat the

actions mentioned above.

If you want to restore only one disk (partition) or have already selected all of the

partitions you need, don't set this switch and click Next.

</quote>

HTH.

--

Glen Ventura, MS MVP Shell/User, A+

http://dts-l.org/

http://dts-l.org/goodpost.htm

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

Bill Blanton wrote:

> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:OJO17bGBIHA.3848@TK2MSFTNGP05.phx.gbl...

>> "Frog" <frog@pond.com> wrote in message news:ulkQAFFBIHA.1168@TK2MSFTNGP02.phx.gbl...

>>> Bill Blanton wrote:

>>>> Well, we can quit playing around with partinfos. The disk has no partition structure

>>>> and is formatted as a "Removable" drive. Sort of like a 120GB floppy. The volume

>>>> boot sector located at sector 0 shows ~120GB volume formatted as FAT32. The

>>>> small portion of FAT that followed looked like it chained to one big file. Probably? the

>>>> *.tib file.

>>>>

>>>> You might try this. Slave the drive to the primary master (remember to set jumpers),

>>>> boot to Windows and in the device manager properties sheet, set the drive as "Removable",

>>>> and reboot. Can you see the *.tib file now? If so, run TI. If not, you might try file recovery

>>>> software such as RStudio. The problem is that everything is contained in the one large *.tib file.

>>>> And you can't recover individual files without TI mounting the file..

>>>>

>>> Bill,

>>>

>>> Some good news---the "bad" hard drive is in the Primary Slave position, and it now has Drive H assigned to this device.

>>> Yes, I can now see two files in Windows Explorer that are loaded on the "bad" hard disk as follows:

>>>

>>> MyBackup1.tib Size: 4,194,300KB Type: TrueImage Backup Archive Modified: 8/28/07 5:58PM

>>>

>>> MyBackup2.tib Size: 1,918,786KB Type: TrueImage Backup Archive Modified: 8/28/07 6:39PM

>>>

>>> I opened the Acronis software, and it could also see Drive H with its two files. So far, I have only done a little up-front

>>> exploring in Acronis. I decided to "Explore Image". This gave me the following:

>>>

>>> Welcome to the Explore Image Wizard!

>>> This wizard will help you to explore a previously created image archive. You will be able to assign temporary drive letters to

>>> the partition images and easily access these partitions as ordinary logical drives.

>>> I clicked Next.

>>> The window that appeared had the following information on it:

>>> Left side window:

>>> Removable Disk (H);

>>> MyBackup1.tib

>>> MyBackup2.tib

>>> I highlighted MyBackup1.tib.

>>> Right side window:

>>> MyBackup1.tib

>>> No description is available for this image archive.

>>> Date: Tuesday, August 28, 2007 4:28 27 PM

>>> Size 5.83 GB

>>> Under this information are six small squares with the following information:

>>> 1 -1118GB

>>> C: - 2...

>>> d: - 2...

>>> E: - 2...

>>> F: - 2...

>>> G: - 25...

>>> Across the bottom of the window is:

>>> File name: H:\MyBackup1.tib

>>> Tiles of type: Image Archives (*.tib)

>>>

>>> The left side of the window for MyBackup2.tib is the same as above.

>>> The right side of this window is also the same above except it included another line as follows: This is volume 2 of multifile

>>> archive MyBackup.tib.

>>> The bottom of the page was the same as above.

>>>

>>> When I clicked the Next button at the bottom of the page, I saw:

>>>

>>> Explore Image Wizard

>>> Assigning Logical Drive Letters

>>> You can assign logical drive letters to the partitions from the image archive you have chosen.

>>> The partitions from the image archive you have chosen will have temporary logical drive letters shown in the hard disk

>>> graphical layout below. To change the drive letter, select a partition then, choose another drive letter in the combo box below

>>> the hard disk graphical layout. Choose "Do not mount" in the combo box, if you do not want to assign a drive letter to the

>>> selected partition. To select a partition place the mouse pointer over it, and then click the left mouse button.

>>> The window then displayed a table as follows:

>>> Partition - Flags - Capacity - Free Space - Type

>>> Disk 1

>>> Each of the following lines was preceded by a box with a check mark in it.

>>> Charlie (J) - PriAct - 21.49GB - 18.25GB - Fat32(LBA)

>>> Delta (K) - - 21.49GB - 18.86GB - Fat32

>>> Echo (L) - - 21.49GB - 19.64GB - Fat32

>>> FAT32 (M) - - 21.49GB - 21.48GB - Fat32

>>> Fat32(N) - - 25.84GB - 25.83GB - Fat32

>>>

>>> I next decided to click the Restore Image button. It gave me the following window:

>>>

>>> Welcome to the Restore Image Wizard!

>>> This wizard will help you to recover lost or corrupted partitions. You will be able to recover a partition or the whole hard

>>> disk drive from the image archive you have previously created.

>>> I clicked Next and got the following error message:

>>>

>>> Error

>>> E000101F9: Cannot get write access to the hard disk drive(s).

>>> Another Acronis application has write access to the hard disk drive(s). Only one Acronis application can have write access to the

>>> hard disk drive at a time.

>>> I clicked OK, and exited Acronis, since I did not understand the error message.

>>>

>>> My last action before writing this message was to attempt to make CDs of the two files. Even this stopped me with the following

>>> message:

>>>

>>> Easy CD Creator

>>> The operation cannot be completed because the file "MyBackup1.tib" is too large to fit on one track. Increase the amount of

>>> usable temp space and try again.

>>>

>>> Well, this stopped me in my track; since I don't understand the message.

>>>

>>> This is where I stopped. I decided that I needed to understand how to restore each of the partitions back to the "good" hard

>>> disk before going any further. I probably will not restore the Charlie partition, because it does not include my data files.

>>>

>>> I very much appreciate your help and patience during this problem- solving episode. I would have been totally dead in the water,

>>> if it were not for the help of you and others on this discussion group. Thanks so very much for your time and expertise.

>>>

>>> Well, I am off to read about Acronis.

>>>

>> Do you have room on your other HDD? If so, you might copy them off to there.

>>

>> Can you run the Restore wiz without first running the Acronis explorer. I

>> don't use Acronis, so don't really know what's going on. Does Acronis have

>> a forum or email support? Or Glen might have an idea.

>>

>> BTW, I'd like to know just for my own knowledge base. Is the drive checked off as

>> "Removable" in Device Manager?

>

> You might also want to check the startup axis for any Acronis services. Start > Run... > Msconfig

>

Yes, I have three entries in the msconfig/startup tab. I believe two

are duplicates...now what do I do? Here is what I see:

Checked - Acronis True Image Monitor - "C:\Program

Files\Acronis\TrueImage\TrueImageMonitor.exe"

Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

Files\Acronis\Schedule2\schedhlp.exe"

Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

Files\Acronis\Schedule2\schedhlp.exe"

The bottom two are exact duplicates.

Frog

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

"Frog" <frog@pond.com> wrote in message

news:u34o9GHBIHA.4956@TK2MSFTNGP06.phx.gbl...

> Bill Blanton wrote:

> snip

>> You might also want to check the startup axis for any Acronis services. Start >

>> Run... > Msconfig

>>

> Yes, I have three entries in the msconfig/startup tab. I believe two are

> duplicates...now what do I do? Here is what I see:

>

> Checked - Acronis True Image Monitor - "C:\Program

> Files\Acronis\TrueImage\TrueImageMonitor.exe"

>

> Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

> Files\Acronis\Schedule2\schedhlp.exe"

>

> Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

> Files\Acronis\Schedule2\schedhlp.exe"

>

> The bottom two are exact duplicates.

That's normal, not a problem. One is loaded from the Registry Run key, the other

from RunServices. It is a normal duplicate, just like the two LoadPowerProfile

entries that load from the same places.

In XP, one appears in msconfig on the Startup tab, and the other appears on the

Services tab.

--

Glen Ventura, MS MVP Shell/User, A+

http://dts-l.org/

http://dts-l.org/goodpost.htm

October 1, 2007

Re: Assigning a Drive letter to External USB connected Hard Drive

glee wrote:

> "Frog" <frog@pond.com> wrote in message

> news:u34o9GHBIHA.4956@TK2MSFTNGP06.phx.gbl...

>> Bill Blanton wrote:

>> snip

>>> You might also want to check the startup axis for any Acronis

>>> services. Start > Run... > Msconfig

>>>

>> Yes, I have three entries in the msconfig/startup tab. I believe two

>> are duplicates...now what do I do? Here is what I see:

>>

>> Checked - Acronis True Image Monitor - "C:\Program

>> Files\Acronis\TrueImage\TrueImageMonitor.exe"

>>

>> Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

>> Files\Acronis\Schedule2\schedhlp.exe"

>>

>> Checked - Acronis Scheduler2 Service - "C:\Program Files\Common

>> Files\Acronis\Schedule2\schedhlp.exe"

>>

>> The bottom two are exact duplicates.

>

> That's normal, not a problem. One is loaded from the Registry Run key,

> the other from RunServices. It is a normal duplicate, just like the two

> LoadPowerProfile entries that load from the same places.

>

> In XP, one appears in msconfig on the Startup tab, and the other appears

> on the Services tab.

Thanks, that's another concern out of the way.

Frog

Sign In

Assigning a Drive letter to External USB connected Hard Drive

Recommended Posts

Guest Frog

Popular Days

Popular Days

Guest Bill Blanton

Guest Bill Blanton

Guest Brian A.

Guest Brian A.

Guest Frog

Guest Bill Blanton

Guest Bill Blanton

Guest Frog

Guest Bill Blanton

Guest glee

Guest Frog

Guest Frog

Guest glee

Guest Bill Blanton

Guest Bill Blanton

Guest glee

Guest Frog

Guest Bill Blanton

Guest Bill Blanton

Guest Frog

Guest glee

Guest Frog

Guest glee

Guest Frog

Similar Content

Broken Hard Drive

Assign a permanent drive letter

Accessing USB Drive in CMD without knowing Drive Letter

Windows 11 not allocating a drive letter to a new USB CD/DVD Drive

external hard drive doesnt work.

Browse

Activity

Site Info