gman

Quote:

The answers are in the various posts above in this thread!

Quote:

Put each downloaded file in a separate sub-directory, click on it to run the extraction process, and then you find the *usbaspi.sys* file in the *F2h* directory created by the extraction process.

That's the Panasonic USB DOS driver.  Make up three subdirectories with the version as its name, copy and paste the *usbaspi.sys* file from each extracted file to the appropriate version sub-directory.

Because the driver name is the same for each version, you have to keep them separate--you can not extract the files to the same sub-directory or you will over-write the previous files.  And you can save the *usbaspi.sys* file of the three versions to the same sub-directory because again they will over-write each other.

Re-create your boot disc files, and use the version of *usbaspi.sys* that you want to use in the process.

Quote:

When using the step-by-step boot, when the *usbaspi.sys* file is loaded, it displays the version as part of the load message you will get.

I'm curious, did you ever do that with your *successful* boot floppy that you do not find an autoexec.bat or config.sys file listed--what was the result?

Thank you!  One question before I run anything....

On my current "working boot CD", there is no Usbaspi.sys file.  Can I just add that file to my boot image - the IMA file and then burn it?  Before I burn, do I need to delete a USB driver in the boot image file (name???) that does NOT work on the DELL laptop so that it won't conflict with newer driver(s) you pointed me to ?

thanks!

G!


PS - I tried adding one the 2.20 Usbaspi.sys file and win Image says the "Image is Full".  I guess I have to delete something....

Then I made a new image with a 2.88 file size and added the same file and still had no luck...what am I missing???

I tried to send a pdf file but it didn't work...


here is a jpeg file for the boot contents:

winimage.jpeg

Thanks for all your help....I don't know what I'd do without you.  I feel I'm getting close to solving this crazy problem!

You will not be able to add USB DOS drivers unless you place *ghost.exe* on the data part of the disc, instead of the in the hidden boot sector with the other boot files.  Unless you can change the boot sector to 2.88 MB--but, then your burning program has to support that too!

I did find out that the software will allow me to use 2.88.

Post the contents of *autoexec.bat* and *config.sys*.

I' CONFUSED?  I did post the contents of autoexec.bat and config.sys in the last post.  Did you see it.

I think what I need to know is what file I need to delete on my boot disc that is the USB driver that will potentially conflict with the new ones you pointed me too. 

Which file on the boot image is the USB driver???

I need to knock this problem out today...or I'm going to be fired.  Please help!

What changes do I need to make in autoexec.bat and config sys for adding the updated USB drivers???

Is there any way you can edit my config.sys file and autoexec.bat file with the command lines you feel I need listed and reply with that in your message.  I have no knowledge of computer programming language and writing command lines...

did you get my last message with the 2 file details?

Ok. I added these files to the disc.  Made it 2.88 on winimage and in the burnining software and edited config.sys with the additions and burned.

When the laptop boots, i see a new post that shows he usb panasonic driver loading (hooray!) but it gets hung up and says "...inititializing host controller 1/5..."  It's been there a couple of minutes...no changes.  Any ideas?

thanks for your continued help and follow up with me...

This is such a pain in the butt!


Ok - with USB emulation turned off, I can now see the drive as source and destination.  A FIRST! 

BUT, when I get into ghost, I get hung up and nothing happens once I direct the program to go ahead with creating the image.

I tried several different versions of boot discs, trying to get away from this and one time it started writing, then it failed within about 5-10 minutes after writing about 300MB of data:

here are some details of what I did:


TEST DISC #1

THIS cd  DIDN’T SEE USB IN SOURCE.

CONFIG SYS

device=oakcdrom.sys /d:nightowl
device=aspiuhci.sys
Device=usbaspi.sys /v
Device=di1000dd.sys
lastdrive=z


AUTOEXEC.BAT

path=a:\;x:\
mouse.com
mscdex.exe /d:nightowl /l:x /m:16 /v
@echo off

--
ASPIOHCI.SYS
ASPIUHCI.SYS
**USBASPI.SYS – 11/7/04




TEST DISC 2

CHANGED USB DRIVER TO VER 2.15

THIS DISC DID NOT RECONGNIZE THE USB DRIVE AT ALL – ONLY C DRIVE WAS SEEN IN SOURCE…


Test disc 3

Added Aspiehci.sys to image file

Changed autoexec to include ghost.exe

Config sys

Added
Device=Aspiehci.sys

WAS ABLE TO SEE SOURCE AND DESTINATION USB DRIVE IN GHOST.
WHEN IT LAUNCHES, GHOST SHOWS WEIRD TIME REMAINING AND ELAPSED TIME. 

NOTHING SHOWS IN THE PROGRESS INDICATOR, % COMPLETE, MB/MIN, MB COPIED


TEST DISC #4

DELETED 2 FILES
ASPIUHCI.sys
ASPIOHCI.sys

Could see USB drive in source and destination.  Once directed system to write image, ghost gets hung up and nothing seems to happen.

Unfortunately not.  But I thought we were in!

After messing around and losing another few days of my life with this, here is what I've done:

I bought a USB floppy drive and tried using it changing USb emulation on and off.  Neither worked.

At the same time, I bought the new version of ghost (12) after I called  symantec and thought if the USB drive didn't take, then investing a few bucks to free me (and you) from some serious pain would be more than worthwhile.

I THINK IT WORKED!

I say "I think"  because the interface is so different and the instructions are so weak that I'm flying blind and not sure how to check my work.

The gho ghs files of the past are not more and it seems to me that I can't even access the image files from windows explorer unless i'm in ghost recovery mode.

So, long last after a truly exhaustive search with a lot less hair, I feel a little more at ease.

Here is a believe one of my last questions on this issue (I hope).

If you're familiar with Ghost 12, is there a way to do an integrity check as in ghost 2002, 2003 etc.?

If there is and I can run it, my peace of mind will be put to rest.

I did make a System recovery disc in ghost 12 that is supposed to have all the drivers required for my machine. 

So my friend in cyberspace, I'm am certain you are curious as can be about what the heck is the stop on the 2003 issues, and after already getting an image late yesterday in ghost 12, I did just for grins try your himem.sys just to see.

Please let me know your thoughts on my questions to ghost 12.

With many many thanks.

Gman