To all

Why is this a better driver--see my reasons at the end of this post.

I started working on this after I posted this question in this forum and did not receive much response:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1089728699;start=0#0

The original resources I have used are as follows:

http://www.theinquirer.net/?article=10215

http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/

http://www.freedos.org/freedos/news/technote/203.html

http://www.computing.net/dos/wwwboard/forum/13447.html

http://www.bootdisk.com/usb.htm

I will call this the 'Panasonic Universal USB Driver'.

So I have created a boot floppy as follows:

[config.sys]

Device=himem.sys
rem :The following line loads Panasonic's universal USB-controller driver
rem :those are spaces between the file name and each of the switches
rem :The '/e' switch forces USB 2.0 only, remove for USB 1.x also
Device=usbaspi.sys /e /v
rem :The following is an aspi mass storage driver for usb-connected HDD's
rem :and compactflash memory cards
rem :The 'Motto Hairu USB Driver'
Device=di1000dd.sys
Dos=high,umb
Lastdrive=z


[autoexec.bat]

rem :My USB HDD is drive 'l', if you wish, you will have to change this
rem :in your path statement to match your USB HDD drive letter
path=a:\;c:\;c:\pqmagic;l:\;l:\pqmagic
mouse.com
rem :Type 'rem' and a space in front of 'ghost' below
rem :if you do not want ghost to automatically load on bootup
ghost


[Files on the Floppy Disk]

Autoexec.bat
Command.com
Config.sys
Di1000dd.sys
Himem.sys
Io.sys
Mouse.com
Mouse.ini
Msdos.sys
Usbaspi.sys

How to create the boot disk and where to find the files:
(I'm using Win98se for the following)

-Put a blank floppy in the drive
-Open Windows Explorer
-Right-click the '3 1/2 ( A: )
-Choose 'Format...'
-Select 'Full' and 'Display summary when finished'
  and 'Copy system files'
-Make sure you have full capacity and no bad
  sectors after formating, i.e. a good floppy
-Check the files on the floppy, you should have:
  Command.com
  Drvspace.bin
  Io.sys
  Msdos.sys
-I delete the 'drvspace.bin' as it's not needed

-Now create the config.sys and autoexec.bat files
  -open Wordpad and copy and paste the text lines under
   [Config.sys] above into Wordpad
  -then 'save as' config.sys to the floppy in drive A:\

  -then open a new document for Wordpad and copy and paste
   the text lines under [Autoexec.bat] above into Wordpad
  -then 'save as' autoexec.bat to the floppy in drive A:\

-Copy the Himem.sys to the floppy-it can be found in the Windows
   directory

-Mouse.com can be found in this directory if you have installed
  Norton Ghost 2003:  

  C:\WINDOWS\All Users\Application Data\Symantec\Ghost\Template\common

  or if you have PartitionMagic v8.x, it's here:

  C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS
 
  -Put a copy of Mouse.com on the floppy disk

-The first time Mouse.com runs when you boot, it will create Mouse.ini
  on the floppy for you

-The last two files are found on Rad's download page at the bottom where
  it says 'USB-DOS files':  http://radified.com/Files/

-After you download the 'usb-dos.zip' file, you will need to extract the files

-The kxlrw40an.exe is a self-extracting file you have to execute
  -it contains the Panasonic Driver 'usbaspi.sys' in the F2H directory
  -copy the 'usbaspi.sys' file to the floppy

-The mhairudo.zip has the di1000dd.sys file
  -extract the file
  -copy it to the floppy
  -Warning:  There is a 'usbaspi.sys' file here too--it's the wrong
   one!  Use the one above from the kxlrw40an.exe file.

So what have I done here:

Ghost will not fit on the boot floppy with the other drivers and files.  So I have copied the Ghost.exe to the root directory of the C:\ drive.  

PartitionMagic v8.x has a sub-directory labeled 'DOS' (C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS) which has the necessary dos files to run PartitionMagic under dos.  So I created a sub-directory on the C:\ drive and I labeled it 'pqmagic' and copied the files from PartitionMagic's DOS sub-directory to my 'pqmagic' directory.  I chose 'pqmagic' because that's the program name that loads PartitionMagic when using dos and it reminds me what to type to start PartitionMagic.

My USB 2.0 hard drive always gets the drive letter 'L' assigned to it when booting, so I have put drive letter 'L' in the autoexec.bat path statement (you will have to change your path statement to match your USB HDD letter, if you wish this functionality), and also copied Ghost.exe and the 'pqmagic' sub-directory to the USB 2.0 hard drive's root directory.  So if the C:\ drive has been trashed, then the files are available on the USB 2.0 hard drive too.

In the autoexec.bat path statement, I have told the dos session to look for Ghost.exe and Pqmagic.exe in A:\, C:\, C:\pqmagic, L:\, and L:\pqmagic, and once it finds the program file, it will load and open the program.  I have set the command in the autoexec.bat file to run Ghost automatically when I boot.  If you do not want this to happen, delete the 'Ghost' line, or put 'rem + a space' in front of the 'Ghost' line so the line is ignored when read during bootup.

So why is this a better USB 2.0 DOS driver?:

1.  When booting it loads much faster and mounts and assigns drive letters more quickly.

2.  The Panasonic Universal USB driver may be a more 'universal' USB 2.0 driver that is compatible with more USB 2.0 components.  (Symantec clearly states that it's Iomega driver has limited compatibility:  http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999062808022225?

3.  The Panasonic Universal USB driver was able to mount my Adaptec USB 2.0 powered hub and access the HDD through the hub, so I do not have to unplug my USB 2.0 HDD from the hub, and route the wiring directly to the PCI USB 2.0 adapter card port.

4.  The USB 2.0 transfer rate for Ghost was noticeably faster.  Using the Norton's Iomega USB 2.0 driver, I got a image creation speed of 295 MB/min and an image integrity check speed of 374 MB/min.  

With the Panasonic Universal USB driver, I got an image creation speed of 551 MB/min, and an image integrity check speed of 1024 MB/min!

5.  Using the Panasonic Univeral USB driver I was able to use the DOS version of PartitionMagic to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to.

6.   Using the Panasonic Univeral USB driver I was able to use Fdisk under DOS to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to.

7.  Using the Panasonic Univeral USB driver, if a memory card was loaded in my Lexar USB 2.0 Multi-Card Reader, I was able to mount the card reader, and the driver assigned a drive letter to the memory card, and I had access to the files on the memory card under DOS.

I put Ghost.exe on the memory card while in Windows, and then used the memory card to load Ghost after booting to DOS!  And the memory card showed up in Ghost as a drive that could be imaged.  I Ghosted (is that a word? :) ) it and the integrity check was successful!

(Note:--I went back and tested Norton's Iomega USB driver and discovered that it too will mount the Lexar Multi-Card Reader if a memory card is in the reader before booting.)

8.  This driver is the same one mentioned in this thread:  http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1075994733  

and is referenced in the Ghost Guide here at the bottom of the page:  http://ghost.radified.com/ghost_caveat.htm

So based on the information in this thread, the Panasonic driver appears to work fine with a NOTEBOOK & PCMIA CARD USB hardware.

Remember, your mileage may vary--this is what worked on my system.

I'm hoping El_Pescador is willing and able to try this out on his two USB 2.0 external enclosure kits to let us know if this works for those, and if the performance changes any.  See here:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1094192056

Quote:

... I'm hoping El_Pescador is willing and able to try this out on his two USB 2.0 external enclosure kits to let us know if this works for those, and if the performance changes any... NightOwl

I will most certainly be willing and able to do so ... however, it may be a couple of days due to mopping up and squaring away after being sideswiped by Hurricane Ivan and enduring intermittent power outages.

I was so pooped at noonday, I decided to logon and take a break after a cold lunch (chilled romaine letture topped with chunks of cold leftover grilled Atlantic salmon fillet, walnuts halves, fresh lemon juice and Newman's Own Classic Caesar Dressing - plus a Barq's root beer to remain in character ... LOL !!!) to briefly surf the Internet before the electricity poops out once more.

[glb]El Pescador[/glb]

El_Pescador

Sorry to hear you were in the area that has to deal with Ivan's wrath.  Hope things were not too bad for you.  I heard on the radio news that some areas will not get power back for upwards of two months--there's so much damage to repair.

Beware of the power surges!

[glb]IT WORKS !!! - Well, sorta'[/glb]
My Dell Dimension 8100 running WIN XP Home with its USB 2.0 ports routed off a PCI adapter card utilizing a NEC chipset does both Ghost BackUp and Ghost Integrity Checks smoothly and steadily on the Bytecc ME-320U2 using NightOwl's Panasonic Universal USB 2.0 Boot Floppy.  As for preliminary performance stats with the Panasonic Universal USB driver, I got an Image Creation speed of 707 MB/min, and an Image Integrity Check speed of 1,571 MB/min on this first attempt (original image is 23,605 MB).

My Dell Dimension 8300 running WIN XP Pro with its USB 2.0 ports routed directly off the systemboard is another matter altogether.  It is very balky and takes a grossly inordinate amount of time to even start recognizing either the Bytecc or the Mace Group HDD enclosures.  Although it would eventually recognize the entire array of logical drives within the extended partition composing the external HDD - which is far more than I was used to in trying to have the Bytecc detected in DOS-mode previously - Ghost.exe would then BOMB OUT with no sign of executing beyond interminable blinking lights on the HDD kit.  I am going to try tweaking the DOS-mode drive letter assignments some more tomorrow, but I have a hunch that the integral USB 2.0 chipset/driver setup is part of the problem.

[glb]El Pescador[/glb]

El_Pescador

In your two threads below, I could not find mention of whether you tested the Bytecc enclosure on your Dell Demnsion 8100 using the Norton/Iomega USB driver.  Did you try that combination and what was the result?

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1093815351

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1094192056

Quote:

... In your two threads below, I could not find mention of whether you tested the Bytecc enclosure on your Dell Demnsion 8100 using the Norton/Iomega USB driver.  Did you try that combination and what was the result? NightOwl

In USB 2.0 mode, the Bytecc ME-320U2 HDD kit would never complete any DOS-based actions on either PC, Norton Ghost 2003 or otherwise, with the Norton/Iomega driver setup (albeit it would run at USB 1.1 or slower with no drivers provided).  It would always hang as shown in the tenth frame at the post below:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1094192056;start=1#1

I will post more performance stats downstream when tests are completed, PLUS results of a fusion of the NightOwl 'Panasonic Universal USB Driver' and the 'Norton Twin-Diskette MS-DOS USB 2.0 Disaster Recovery Disk Set'.

[glb]El Pescador[/glb]

Lemme know when you think I should include a link to this thread in the guide. I do not use a USB drive myself, but I know that many do.

This could even be made into an addendum page, much like the "Ghosting Across a Network" page was:

http://ghost.radified.com/ghost_network.htm

If we go that route, perhaps we could have a short & more elaborate version. Whatever you guys think is better, as you're the resident USB Ghost gurus.

http://img.photobucket.com/albums/v235/El_Pescador/Watts8.jpg

Once 'you break on through to the other side' then NTFS external HDDs beome fully functional in the USB 2.0 mode - but then and only then.

On my 160GB Maxtor internal HDD, I have an active partition assigned as Drive C: in XP; inside an extended partition I have three NTFS logical drives (G:, H:, I:) and a single FAT32 logical drive assigned as Drive J:.  Only the drive formatted FAT32 is fully visible and accessible within the MS-DOS environment, and its drive letter has been reassigned as C: !!!

Likewise, my USB 2.0 external Seagate 120GB HDD contains three logical drives within an extended partition; the first two (K: and L:) are formatted NTFS while the third is FAT32 and known as M: in XP, but is reassigned as F: in MS-DOS.  The very existence of the assorted NTFS drives (whether active partitions or logical drives within extended partitions) is acknowledged obliquely in MS-DOS, but in the main their content is both masked and inaccessible.

[glb]El Pescador[/glb]

El_Pescador

I don't think Ghost ever claimed that you could access a NTFS partition under DOS using it's software--only that you could image it and restore it, either to FAT partitions or NTFS partitions.

If you want to access NTFS files under DOS you need to install another driver--see here for an example:

http://www.sysinternals.com/ntw2k/freeware/ntfsdos.shtml

Drive letter assignment under DOS will be made to only those drives (partitions) that are FAT xx, such as FAT 16 and FAT 32 HDD's and floppy drives (I think these are FAT 12), CD and DVD ROM's if you load the MS-DOS optical drive driver (MSCDEX), and other card media such as a compact flash card, Xd card, etc., in a card reader.

Under Fdisk, NTFS partitions are 'seen', but identified as 'Non-Dos Partitions', and no letter assignment is made for them, which is also true using PartitionMagic under DOS.

In your post above, what happened to your partitions D, E, and F under WinXP?  And there must be a D, and E being assigned under DOS in order for your FAT 32 partition on your USB 2.0 external Seagate 120GB HDD to be assigned drive letter F.

Quote:

... In your post above, what happened to your partitions D, E, and F under WinXP?  And there must be a D, and E being assigned under DOS in order for your FAT 32 partition on your USB 2.0 external Seagate 120GB HDD to be assigned drive letter F... NightOwl

You are indeed perceptive, NightOwl ... LOL !!!

As I recall, it was something to the effect:

D: .............. 0KB
E: .............. 0KB
F: ...... 40,222KB

In other words, it did acknowledge their existence albeit inaccessible.

Give me a couple of days more to marshal my thoughts (sort of hectic around here right now!), and I will lay out some theories I am mulling over.

[glb]El Pescador [/glb]

El_Pescador

You said in another thread:


Quote:

The Dell Dimesion 8300 has only USB 2.0 ports, and they are routed off the systemboard

So I assume you have a built-in onboard USB controller on the motherboard.  Are there settings in the BIOS for that system that enable/disable the 'legacy support' for USB keyboards and/or mice.  And are there settings to enable/disable for booting from a USB device?  If so, possibly changing the settings (probably to disabled) may help let the Panasonic Universal USB drive work.

Quote:

... So I assume you have a built-in onboard USB controller on the motherboard.  Are there settings in the BIOS for that system that enable/disable the 'legacy support' for USB keyboards and/or mice.  And are there settings to enable/disable for booting from a USB device?  If so, possibly changing the settings (probably to disabled) may help let the Panasonic Universal USB drive work...   Night Owl

If I continue trying to improve upon NightOwl's most elegant 'Panasonic Universal USB Driver', I will have to change my nomme' de guerre to NightOwl II ... LOL !!! - up four nights in a row past 3AM of late.

My Dell Dimension 8300 does indeed have an onboard USB controller on the motherboard, and none of the conceivable permutations of switching USB settings in the BIOS turned out to be productive.

So, will return to that later.

Quote:

...Ghost will not fit on the boot floppy with the other drivers and files.  So I have copied the Ghost.exe to the root directory of the C:\ drive.   PartitionMagic v8.x has a sub-directory labeled 'DOS' (C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS) which has the necessary dos files to run PartitionMagic under dos.  So I created a sub-directory on the C:\ drive and I labeled it 'pqmagic' and copied the files from PartitionMagic's DOS sub-directory to my 'pqmagic' directory.  I chose 'pqmagic' because that's the program name that loads PartitionMagic when using dos and it reminds me what to type to start PartitionMagic... NightOwl

One of the more promising paths I am taking is to make a bootable CD wrapped around  NightOwl's 'Panasonic Universal USB Driver', but including an additonal folder to contain GHOST.EXE and yet another to contain the entire contents of  C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS.  Doing this with Nero in Windows XP is an absolute snap - everything falls right into place - BUT after booting up with the CD in MS-DOS, the directory of A: only reveals the core  'Panasonic Universal USB Driver'.  I surmise that I need to modify either the CONFIG.SYS or AUTOEXEC.BAT to enable MS-DOS to access the masked file folders on the CD, but I must confess my ignorance in such matters and am appealing for advice.

Since Nero will accept a 96MB ZIP disk as the bootable floppy disk, this would be a viable avenue for me if I only had a such a disk with the WIN 98 SE system files already on it to burn onto a CD.  Even using a CD-RW disk rather than a CD-R, the process of making it bootable 'finalizes' it (on one PC for sure, maybe not the other) to where nothing can be added, deleted or modified thereafter - but such is not the case with 1.44MB floppys or 96MB ZIP disks.  

Taking this approach seems to be necessary whenever all the HDD partitions - both internal and external USB 2.0 - are formatted NTFS.  If there is a FAT32 partiton on a HDD anywhere in the loop, then that is where GHOST.EXE and the PQMAGIC folder must reside - and MS-DOS will assign drive letter 'C:' to the first such partition encountered.  

[glb]El Pescador[/glb]

El_Pescador

I think this is what you need to make your CD drive visible in DOS:

[config.sys]

Device=himem.sys

rem :Add this line for CD-Rom Support
device=oakcdrom.sys /d:mscd001

Device=usbaspi.sys /v /w /e
Device=di1000dd.sys
Dos=high,umb
Lastdrive=z


[autoexec.bat]
 
path=a:\;c:\;c:\pqmagic;l:\;l:\pqmagic;x:\;x:\pqmagic

rem :Add this line for CD_Rom Support
mscdex.exe /d:mscd001 /l:x /m:16 /v

mouse.com
ghost


[Files on the Floppy Disk]

Autoexec.bat
Command.com
Config.sys
Di1000dd.sys
Himem.sys
Io.sys
Mouse.com
Mouse.ini
Msdos.sys
Usbasipi.sys

Add these program files to the floppy for CD-Rom support:

oakcdrom.sys
mscdex.exe

Notes:

1.  oakcdrom.sys is the 'universal' CD-Rom driver on the Win98se startup disk.

2.  mscdex.exe will be on the Win98se startup disk, WinME startup disk, and in the Windows/Command directory of Win98se.

3.  The '/l:x' switch on the mscdex.exe line in autoexec.bat file tells DOS to assign the first optical device seen as drive=X:/.  If you want the drive letter to be something else, change it to what you want.

4.  Change your 'path=' statement to include the drive letter of the optical device you want to have your Ghost and PartitionMagic files on.  If Ghost.exe is in the root directory of drive 'X', then the above path statement will work.  If you want a separate directory for Ghost, the the path statement would need to include:

path=a:\;c:\;c:\pqmagic;l:\;l:\pqmagic;x:\;x:\pqmagic;x:\ghost

Again, if you assign a different drive letter for the optical drive, you will have to change the 'x' 's to whichever drive letter you have chosen.

NightOwl -

I am too tired to do much more tonight (now 0150 hr here), but I would like everyone to see the layout scheme of my two Dell Dimensions:

http://img.photobucket.com/albums/v235/El_Pescador/KomboDM.jpg

[glb]El Pescador[/glb]

El_Pescador posed an interesting problem in his reply #11 above regarding using the Panasonic Universal USB Driver--where I have put the DOS Ghost program and PartitionMagic's DOS program files on the internal HDD and the external USB HDD in a FAT-32 partition because they will not fit on a single floppy along with the necessary driver programs.

If you've made the decision to make all your partitions NTFS, you wont be able to run Ghost or PartitionMagic from the NTFS partitions.  El_Pescador proposed making a bootable CD with the DOS Ghost and PartitionMagic files on it.  And I think that's a good solution--but you can do it with floppys too--at least for Ghost--here's how:

If you use Norton Ghost Boot Wizard to create the 'CD/DVD Startup Disk with Ghost', the wizard creates a two floppy disk set, again because the driver files take up too much floppy disk space to fit on one floppy.  The 'config.sys' and 'autoexec.bat' files are fairly complex, but I think you could probably take that two disk set and delete the unnecessary files and add the 'Panasonic Universal USB Driver' files and get it to work, but I found that there's an easier solution:

Create the bootable, system floppy with the 'Panasonic Universal USB Driver' as follows:

[config.sys]

Device=himem.sys
Device=usbaspi.sys /e /v
Device=di1000dd.sys
Dos=high
Lastdrive=z


[autoexec.bat]

mouse.com


[Files on the Bootable System Floppy Disk]

Autoexec.bat
Command.com
Config.sys
Di1000dd.sys
Himem.sys
Io.sys
Mouse.com
Msdos.sys
Usbasipi.sys

Then, on another formated floppy, copy the 'Ghost.exe' DOS program.

After booting with the system floppy and you are at the A:\> prompt, simply put the other floppy in and type 'Ghost'.  You will now load Ghost and you do not have to rely on the 'complex' config.sys and autoexec.bat structure created by the Norton Ghost Boot Wizard nor on a CD for which you need to load additional DOS drivers in order to use.

El_Pescador

I think your 'Reply # 13' with the large screen shot has caused this thread to require a screen that's wider than will fit without having to use the bottom scroll bar.  Makes it hard to read the posts.

Is there any way you can 'modify' your post so it doesn't create the need for the bottom scroll bar?

[glb]HOWZAT ???[/glb]

[glb]El Pescador[/glb]

El_Pescador

That modification worked great!  Thanks.

Looks like you're working on that option I mentioned about using the 'Boot disks' created by the Boot Wizard and substituting the Panasonic files.  Should work if you use the correct mods.

This mod (now moved below) is the one I made reference to some time back using NighOwl's 'Panasonic Universal USB Driver' as its foundation.  Regrettably, I had put it on the 'back-burner' in hopes of working off of a single bootable CD-R rather than two floppy disks or having to rely on a FAT32 HDD being somewhere in the loop containing GHOST.EXE and the PQMAGIC folder for DOS routines.

Using both Nero and CD Creator 5 Platinum, I succeeded in loading anything and everything I wanted onto the CD-R, but failed to make anything accessible in MS-DOS except the contents of the bootable 1.44MB floppy iself.

I hope someone with more smarts than me will pick up the gauntlet and eventually make it work.

Anyway, the two-disk concept using 1.44MB floppys functions quite well and is a natural extension of NightOwl's excellent work.

[glb]El Pescador[/glb]

[glb]More USB 2.0 External HDDs should work as promised now with DOS-based applications !!![/glb]

Behold a fusion of the Norton/Iomega Disaster Recovery MS-DOS 2-Disk Set and NightOwl's 'Panasonic Universal USB Driver'.  Review NightOwl's initial post in this thread to gain the necessary components for the substitutions called for below.  

http://img.photobucket.com/albums/v235/El_Pescador/BigWiz.jpg
STEP ONE: Format two 1.44MB floppys in a WIN 9x PC using the 'Copy system files' option. Then, label them as Disk 1 and Disk 2 respectively prior to submitting them to the Norton Ghost Boot Wizard for undergoing processing as a MS-DOS 2-Disk Disaster Recovery Set.

http://img.photobucket.com/albums/v235/El_Pescador/Panafirst0.jpg
STEP TWO: Following completion of the Norton Ghost Boot Wizard processing, return the 1.44MB floppy labeled Disk 1 to the WIN 9x PC and copy C:\Windows\HIMEM.SYS to the A:\ root as shown above.

http://img.photobucket.com/albums/v235/El_Pescador/Punyfirst1.jpg
STEP THREE: Open the AUTOEXEC.BAT file on BOTH Disk 1 and Disk 2 with Notepad.  Discard GUEST.EXE on the third line and substitute the PATH command as shown above.

http://img.photobucket.com/albums/v235/El_Pescador/Panafirst2.jpg
STEP FOUR: Open the CONFIG.SYS file on Disk 1 with Notepad.  Discard ASPIEHCI.SYS and modify the DEVICE assignments as shown above.

http://img.photobucket.com/albums/v235/El_Pescador/Panafirst3.jpg
STEP FIVE: Duly note that the GHOST folder on Disk 1 is vacant, but contains GHOST.EXE on Disk 2.  Conversely, having a vacant USB folder on Disk 2 would fulfill the PATH statement in AUTOEXEC.BAT, although such is not reflected in the illustrations.

http://img.photobucket.com/albums/v235/El_Pescador/Panafirst4.jpg
STEP SIX: Open the USB folder in Disk 1 and discard the ASPIEHCI.SYS file, replacing it with USBASPI.SYS and DI1000DD.SYS as shown above.

http://img.photobucket.com/albums/v235/El_Pescador/Punysecond1.jpg
STEP SEVEN: Ensure that the AUTOEXEC.BAT file on Disk 2 exactly matches that on Disk 1.

http://img.photobucket.com/albums/v235/El_Pescador/Panasecond2.jpg
STEP EIGHT: Ensure that the GHOST folder on Disk 2 contains GHOST.EXE, but nothing else.

[glb]El Pescador[/glb]

El Pescador


Quote:

I hope someone....will pick up the gauntlet and eventually make it work.

See if this works:

I created the following bootable system floppy disk under Win98se:

[config.sys]  
 
Device=himem.sys  
Device=usbaspi.sys /e /v  
Device=di1000dd.sys
Device=oakcdrom.sys /d:mscd001
Dos=high  
Lastdrive=z  
 

[autoexec.bat]  

Path=a:\y:\;y:\ghost;y:\pqmagic  
Mouse.com
Mscdex.exe /d:mscd001 /l:x /m:16 /v  

 
 
[Files on the Bootable System Floppy Disk]  
 
Autoexec.bat  
Command.com  
Config.sys  
Di1000dd.sys  
Himem.sys  
Io.sys  
Mouse.com  
Msdos.sys  
Mscdex.exe
Usbasipi.sys

I then created a subdirectory on my C:\ drive named 'Ghost' and copied the DOS program 'Ghost.exe' to it.

I then created a subdirectory on my C:\ drive named 'Pqmagic' and copied the files from the 'C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS' subdirectory to it.

I then did the following steps to create a bootable CD:

1.  Opened Roxio Easy CD Creator 5

2.  Rt clicked the 'File' menu item

3.  Selected 'New CD Project'/'Bootable CD'

In the 'Choose Type of Bootable CD' I selected 'Floppy Disk Emulation (1.44 MB)' and selected 'Generate Image from Floppy.  Please insert a bootable floppy disk in drive A and click OK.'

Inserted the above bootable floppy and the program read the bootable floppy and added 'bootcat.bin' and 'bootimg.bin' to the lower screen where the files to be burned to the CD are listed.

4.  I then highlited the 'Pqmagic' subdirectory in the upper screen (source files), and clicked 'add' so it now showed in the lower screen of files/directories to be burned to the CD.

5.  I then highlited the 'Ghost' subdirectory in the upper screen (source files), and clicked 'add' so it now showed in the lower screen of files/directories to be burned to the CD.

6.  I then clicked 'record', and I had a bootable CD with Ghost, PartitionMagic, and the Panasonic Univeral USB Driver on it.

Notes:

1.  The 'Device=oakcdrom.sys /d:mscd001' mounts the optical drive(s), and 'Mscdex.exe' assigns the drive letters in DOS for the optical drives.  

The '/l:x' switch tells 'Mscdex.exe' to assign the first optical drive it detects with drive letter 'x', and any additional optical drives will be 'y' and 'z' if present.  You can change the '/l:x' to whatever starting letter you want.  I have two optical drives--a CD-R/RW and a DVD-Rom--so they are assigned drive letters 'x' and 'y' respectively.  On my system, if the 'path' statement points to both of the optical drives, I get a 'CDR101: Not ready reading drive x,  Abort, Retry, Fail' if the first drive in the path statement is not the boot drive.  So I only put the drive I prefer to boot from in the path statement.  I can always change to the other one if I need to.

2.  I have found that on my system, that it is important to load the Panasonic Univeral USB driver files before the 'oakcdrom.sys' program because the system will hang more often then not if the 'oakcdrom.sys' is loaded first.

3.  Might want to use a CD-RW blank at first for testing if you can.  I had to redo things several times to work out the 'bugs', and being able to erase and start over without having to waste multiple CD-R's was helpful.

I thought it might be worth mentioning how I created my bootable CD.

I use a process similar to that used by NightOwl.  Thie main difference is that I used WinImage to create an image of teh first boot disk (basically just a Win98 boot disk).  Then I used winimage to convert the format of the image from 1.44 to 2.88 MB.  At that point you have 2.88 MB of image space to play with so I actually have a number of different utilities on the root image itself.

It contains the following:
The basic DOS files (ie. command.com, io.sys, msdos.sys)
Numerous DOS utilities (ie. fdisk, format, edit, ramdisk, scandisk, ntfsdos, etc.)
The USB driver files.
The ghost.exe file.

Once you have the image how you want it, you save it as an uncompressed (IMA) file, start up Easy CD creator and follow NightOwl's instructions above (except select "2.88MB floppy disk emulation" instead of the standard 1.44, and select "Use existing image file").

I also did the same thing as nightowl, adding Partition Magic to the CD's normal (not "el torito") filesystem.

The El Torito standard also supports hard drive emulation for bootable CDs so I don't see any reason an image couldn't be created to the max size of a CD-ROM ~700MB.  I haven't yet dabled with it, but I assume that if I create a primary partition of say 680MB and format it as FAT with Win98 DOS boot files, I should be able to snag an image of it with WinImage, or 'dd' (which is available for Windows in addition to Linux/UNIX systems).  Easy CD creator gives you the option of selecting "Hard drive emulation" in addition to floppy emulation when you create a bootable CD as NightOwl outlined above.

Like I say, I haven't tested this yet, but it should work.

--Ryan

Added a link to this thread in the guide where I discuss imaging to USB drives, at the botom of this page:

http://ghost.radified.com/ghost_caveat.htm

Hi thanks very much for this information.I created the boot floppy as you instructed and it worked fine for me.I tried it on two Windows XP machines,one with usb 2.0 and one with usb 1.0 to an AKASA usb to ide hard disk enclosure with a Maxtor 120gb hard disk the hard disk is formatted fat32 .I formatted it fat 32 because I was messing about trying to get things working using the Ghost boot floppy with the Iomega drivers without success so I have not tried the dive formatted as NTFS.
I used Nero to create a couple of boot cds using the floppy as the source for the files and they work fine and the external drive was allocated drive letter D on my p.c. (I have 3 ntfs partitions) and drive C on the other p.c.
I was getting a data transfer rate of over 500mb per min usb2 and 89mb per minute on the lower spec. usb 1.o machine so overall I am very happy that things are working.
Thanks very much for your help
Keith Carlisle

Hi

Can you help me!!!

I’m making bootable USB memory stick and copy files:

[config.sys]

Device=himem.sys
Device=usbaspi.sys /e /v
Device=di1000dd.sys
Dos=high,umb
Lastdrive=z

[autoexec.bat]
 
path=a:\;c:\;c:\ghost
mouse.com
ghost

[Files on the Floppy Disk]

Autoexec.bat
Command.com
Config.sys
Di1000dd.sys
Himem.sys
Io.sys
Mouse.com
Mouse.ini
Msdos.sys
Usbasipi.sys


After boot from USB memory stick  :
"The following file is missing or corrupted: Di1000dd.sys
There is an error in your CONFIG.SYS on line 3

HELP !!!!!!!

Valts


Quote:

"The following file is missing or corrupted: Di1000dd.sys   There is an error in your CONFIG.SYS on line 3

Chicken vs Egg Problem?

I've seen reference to computer systems that can boot from USB memory cards--but I have no experience as to whether this is true or not.

Does your system have such ability?  Does it create a 'virtual A:\ drive' like the bootable CD sector on optical media?  Or, how exactly do you set it up so it's supposed to work?

The problem is--you are trying to load a USB driver that mounts a USB card reader (Device=usbaspi.sys /e /v ), and then a driver that assigns a drive letter to that mounted USB card reader (Device=di1000dd.sys ).  But you need those drivers loaded before you can access the memory card.

If your system is designed to boot from a USB memory card reader, then you must have built-in native access to the memory card--in which case, you would be trying to install drivers that do the same thing--which could cause conflicts between the competing drivers!

I have booted with the 'Panasonic USB 2.0' drivers from a floppy, and then run Ghost from my memory card reader that has Ghost.exe on it.  But I have no access to the memory card until the drivers are first loaded from floppy or bootable CD.

But, if you do have built-in native access to the USB card reader for booting--what drive letter is it assigned?  You probably have to change the CONFIG.SYS file lines to point to that drive letter with a full path indicated.

For example, if you USB card reader with the memory stick is assigned drive letter M:\, then you would possible need:  'Device=M:\di1000dd.sys'.

Or, if the card reader is being mounted as a 'virtual A:\' drive, maybe you need this change:  'Device=A:\di1000dd.sys'

Are the other drivers called in CONFIG.SYS and AUTOEXEC.BAT being loaded okay--'himem.sys', 'usbaspi.sys', and 'mouse.com'?

NightOwl wrote on Sep 17^th, 2004 at 1:24pm:

To all Why is this a better driver--see my reasons at the end of this post. I started working on this after I posted this question in this forum and did not receive much response: http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1089728699;start=0#0 The original resources I have used are as follows: http://www.theinquirer.net/?article=10215 http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/ http://www.freedos.org/freedos/news/technote/203.html http://www.computing.net/dos/wwwboard/forum/13447.html http://www.bootdisk.com/usb.htm I will call this the 'Panasonic Universal USB Driver'. So I have created a boot floppy as follows: [config.sys] Device=himem.sys rem :The following line loads Panasonic's universal USB-controller driver rem :those are spaces between the file name and each of the switches rem :The '/e' switch forces USB 2.0 only, remove for USB 1.x also Device=usbaspi.sys /e /v rem :The following is an aspi mass storage driver for usb-connected HDD's rem :and compactflash memory cards rem :The 'Motto Hairu USB Driver' Device=di1000dd.sys Dos=high,umb Lastdrive=z [autoexec.bat] rem :My USB HDD is drive 'l', if you wish, you will have to change this rem :in your path statement to match your USB HDD drive letter path=a:\;c:\;c:\pqmagic;l:\;l:\pqmagic mouse.com rem :Type 'rem' and a space in front of 'ghost' below rem :if you do not want ghost to automatically load on bootup ghost [Files on the Floppy Disk] Autoexec.bat Command.com Config.sys Di1000dd.sys Himem.sys Io.sys Mouse.com Mouse.ini Msdos.sys Usbasipi.sys How to create the boot disk and where to find the files: (I'm using Win98se for the following) -Put a blank floppy in the drive -Open Windows Explorer -Right-click the '3 1/2 ( A: ) -Choose 'Format...' -Select 'Full' and 'Display summary when finished'   and 'Copy system files' -Make sure you have full capacity and no bad   sectors after formating, i.e. a good floppy -Check the files on the floppy, you should have:   Command.com   Drvspace.bin   Io.sys   Msdos.sys -I delete the 'drvspace.bin' as it's not needed -Now create the config.sys and autoexec.bat files   -open Wordpad and copy and paste the text lines under    [Config.sys] above into Wordpad   -then 'save as' config.sys to the floppy in drive A:\   -then open a new document for Wordpad and copy and paste    the text lines under [Autoexec.bat] above into Wordpad   -then 'save as' autoexec.bat to the floppy in drive A:\ -Copy the Himem.sys to the floppy-it can be found in the Windows    directory -Mouse.com can be found in this directory if you have installed   Norton Ghost 2003:     C:\WINDOWS\All Users\Application Data\Symantec\Ghost\Template\common   or if you have PartitionMagic v8.x, it's here:   C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS     -Put a copy of Mouse.com on the floppy disk -The first time Mouse.com runs when you boot, it will create Mouse.ini   on the floppy for you -The last two files are found on Rad's download page at the bottom where   it says 'USB-DOS files':  http://radified.com/Files/ -After you download the 'usb-dos.zip' file, you will need to extract the files -The kxlrw40an.exe is a self-extracting file you have to execute   -it contains the Panasonic Driver 'usbaspi.sys' in the F2H directory   -copy the 'usbaspi.sys' file to the floppy -The mhairudo.zip has the di1000dd.sys file   -extract the file   -copy it to the floppy   -Warning:  There is a 'usbaspi.sys' file here too--it's the wrong    one!  Use the one above from the kxlrw40an.exe file. So what have I done here: Ghost will not fit on the boot floppy with the other drivers and files.  So I have copied the Ghost.exe to the root directory of the C:\ drive.   PartitionMagic v8.x has a sub-directory labeled 'DOS' (C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS) which has the necessary dos files to run PartitionMagic under dos.  So I created a sub-directory on the C:\ drive and I labeled it 'pqmagic' and copied the files from PartitionMagic's DOS sub-directory to my 'pqmagic' directory.  I chose 'pqmagic' because that's the program name that loads PartitionMagic when using dos and it reminds me what to type to start PartitionMagic. My USB 2.0 hard drive always gets the drive letter 'L' assigned to it when booting, so I have put drive letter 'L' in the autoexec.bat path statement (you will have to change your path statement to match your USB HDD letter, if you wish this functionality), and also copied Ghost.exe and the 'pqmagic' sub-directory to the USB 2.0 hard drive's root directory.  So if the C:\ drive has been trashed, then the files are available on the USB 2.0 hard drive too. In the autoexec.bat path statement, I have told the dos session to look for Ghost.exe and Pqmagic.exe in A:\, C:\, C:\pqmagic, L:\, and L:\pqmagic, and once it finds the program file, it will load and open the program.  I have set the command in the autoexec.bat file to run Ghost automatically when I boot.  If you do not want this to happen, delete the 'Ghost' line, or put 'rem + a space' in front of the 'Ghost' line so the line is ignored when read during bootup. So why is this a better USB 2.0 DOS driver?: 1.  When booting it loads much faster and mounts and assigns drive letters more quickly. 2.  The Panasonic Universal USB driver may be a more 'universal' USB 2.0 driver that is compatible with more USB 2.0 components.  (Symantec clearly states that it's Iomega driver has limited compatibility:  http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999062808022225? 3.  The Panasonic Universal USB driver was able to mount my Adaptec USB 2.0 powered hub and access the HDD through the hub, so I do not have to unplug my USB 2.0 HDD from the hub, and route the wiring directly to the PCI USB 2.0 adapter card port. 4.  The USB 2.0 transfer rate for Ghost was noticeably faster.  Using the Norton's Iomega USB 2.0 driver, I got a image creation speed of 295 MB/min and an image integrity check speed of 374 MB/min.   With the Panasonic Universal USB driver, I got an image creation speed of 551 MB/min, and an image integrity check speed of 1024 MB/min! 5.  Using the Panasonic Univeral USB driver I was able to use the DOS version of PartitionMagic to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to. 6.   Using the Panasonic Univeral USB driver I was able to use Fdisk under DOS to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to. 7.  Using the Panasonic Univeral USB driver, if a memory card was loaded in my Lexar USB 2.0 Multi-Card Reader, I was able to mount the card reader, and the driver assigned a drive letter to the memory card, and I had access to the files on the memory card under DOS. I put Ghost.exe on the memory card while in Windows, and then used the memory card to load Ghost after booting to DOS!  And the memory card showed up in Ghost as a drive that could be imaged.  I Ghosted (is that a word? :) ) it and the integrity check was successful! (Note:--I went back and tested Norton's Iomega USB driver and discovered that it too will mount the Lexar Multi-Card Reader if a memory card is in the reader before booting.) 8.  This driver is the same one mentioned in this thread:  http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1075994733   and is referenced in the Ghost Guide here at the bottom of the page:  http://ghost.radified.com/ghost_caveat.htm So based on the information in this thread, the Panasonic driver appears to work fine with a NOTEBOOK & PCMIA CARD USB hardware. MY PRINTER IS HP 1010 LASER JET i WANT DOS PRINT HOW IT'S POSSIBLE JUST SUGEST ME. PL. AS EARLY AS POSSIBLE Remember, your mileage may vary--this is what worked on my system. I'm hoping El_Pescador is willing and able to try this out on his two USB 2.0 external enclosure kits to let us know if this works for those, and if the performance changes any.  See here: http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1094192056

A made 2 floppys to boot to DOS by following the previous posts.  I am having trouble with the usbaspi.sys driver.  When it loads it says "target USB device not found.  Everything else loads fine.  I have a PCI USB 2.0 card conntected to a WD 120 GB external hard drive. I bought this as a single unit and not a hard drive and mounted into an enclosure.  The hard drive is formatted in NTFS.  It worked fine with Ghost 9.0.  I uninstalled 9.0 and went back to 2003.  Does anyone have any ideas?

dgroover

I have a similar setup, PCI USB 2.0 controller card and a Iomega USB 2.0 HDD, and it finds the HDD without a problem.

Things you might try:

1.  make sure the HDD is plugged in and running before booting

2.  try different USB plug-in ports on the PCI card if you have more than one to see if that helps

3.  do you have a USB memory card reader?  Put a memory card in the card reader and connect it to the PCI controller--now boot to DOS--does the memory card get assigned a drive letter and do you have access to the memory card in DOS?

4.  is that the only error message?  If you press F8 during boot, you can select a step-by-step boot of each line of config.sys and autoexec.bat and it pauses after each line executes to see what load or error messages occur.

Post back with your results.

NightOwl,

1. Yes the hard drive is powered on and up to speed.
2. Different ports did not make a difference.  I did plug the
   HD cable into the USB port attached to the MOBO and it
   did find it.
3.  No memory card reader.
4. I get "Target USB device not found".  After is tries to load
  di1000dd.sys is says ASPI driver not loaded.

I played with the software switches on the usbaspi.sys driver.
It will tell me bad parameter when I use /e.  I hope I (we) can solve this problem.

dgroover -

The two tables below illustrate USB 2.0 host controller and USB 2.0 device controller specifications I have gleaned while trying to ensure compatibility of USB 2.0 external HDD enclosure kits with DOS-based Norton Ghost 2003:

http://img.photobucket.com/albums/v235/El_Pescador/HostHdws.jpg

http://img.photobucket.com/albums/v235/El_Pescador/HDDHdws.jpg

Where I am severely lacking is for information about "purpose-built" external HDDs such as yours.  So far, only piikea has demonstrated access to Western Digital HDDs hereabouts (plus chuckychez contributed later on with details on his Seagate 160GB USB 2.0 external HDD) in Norton Ghost 2003, and at that it took NightOwl's Panasonic Universal USB Driver routine to pull it off.  His 80GB Western Digital "purpose-built" external HDD could not access Ghost 2003 via the conventional Norton/Iomega drivers embedded in Ghost 2003.  This in turn indicates that the USB 2.0 bridge chipset and concomitiant device controller software provided by Western Digital are not capable of "Windows-to-DOS-to-Windows" operations such as Ghost 2003 or maybe even certain phases of Norton Partition Magic 8.0.

Since you have switched back from Norton Ghost 9.0 to Ghost 2003, any information you can provide about your Western Digital 120GB "purpose-built" external HDD and USB 2.0 host controller can really prove helpful - both to you right now and then to others downstream with similar problems.

From what I can tell up to now, USB 2.0 host controllers have eventually shaken out to either VID=8086h or VID=1033h - and no other thusfar.  So, what I am now able to do with a fair degree of certainty is counsel someone as to: (1) whether or not they will need a PCI-to-USB Host Adapter Card despite having USB 2.0 ports on their systemboard - and which model cards are compliant with Ghost 2003 operations; and (2) whether or not adopting NightOwl's Panasonic Universal USB Drivers routine will render their hitherto incompatible external enclosure kit Ghost 2003-compatible.  With help from you, chuckychez, and piikea, we can continue to expand from enclosure kits to "purpose-built" HDDs right off the shelf.

In your situation, there is only a single configuration to deal with, i.e., USB 2.0.  In clarification, let me say that it is not your hardware I am really focusing on - it is the fact of whether or not those software drivers you are employing with it could permit DOS-based Norton Ghost 2003 operations.  Nonetheless, knowing the make and model of your PCI-to-USB card will help in cross-referencing later on.

On the host end of the "bridge", the useful items are in properties of only those terminal "branch(es)" on the Universal Serial Bus controllers "tree" containing the word 'Enhanced'.  On the destination end of the "bridge", the useful items are in properties of only those terminal "branch(es)" on the Universal Serial Bus controllers "tree" containing the phrase 'Mass Storage Device'.

To take a shot at revealing the particulars of both your USB 2.0 host controller(s) and your USB 2.0 device controller(s), follow the procedure below:

(1) go to Desktop and right click on My Computer;

(2) drop down to left click on Manage;

(3) in left pane, expand System Tools;

(4) in left pane, drop down to left click on Device Manager;

(5) for both USB controllers and mass storage devices in right pane, expand Universal Serial Bus controllers;

(6) for USB Mass Storage Devices, skip down to (7) - else for USB 2.0 controllers, focus on those lines containing either the abbreviation 'USB2' or the word 'Enhanced', then go to (7);

(7) right click on any such lines that drop down, then left click on Properties;

(8) left click on the Details tab;

(9) left click on the dropdown menu containing Device Instance Id; and

(10) left click on Hardware Ids and carefully transcribe the last two lines in the window. To be overly generous, drop down two more lines and repeat for Matching Device Id.

The image below reveals the functional USB 2.0 controller on the Macally PHR-100A enclosure (note that on my Dell Dimension 8300, I have three 'Enhanced' USb controllers listed - including the poisonous Intel 80281EB):

http://img.photobucket.com/albums/v235/El_Pescador/PHR100AAs.jpg

BTW, this very morning I received an Iomega 80GB USB 2.0 "purpose-built" external HDD from Outpost.com with a net cost of $40 after MIR (not counting shipping).  As I am currently battening down for a direct hit by (what so far is near-) Hurricane Cindy a little after midnight, I will unpack it in a few days.

[glb]El Pescador[/glb]

El_Pescador,

Wow, where do I start.  My hard drive is a WD found here:
http://www.wdc.com/en/products/Products.asp?DriveID=108
I am not sure of the make of my USB card.  It has an ALi chipset M5273.  That is all I know about it.  The reason I bought it was my current computer only has USB 1.1.  Ghost 9.0 took 5 hours to back up my hard drive at USB 1.1 speeds and 30 minutes at USB 2.0 speeds.  Off to device manager.
USB mass storage device HW ID:
USB\Vid_1058&Pid_0401&Rev_0412&Mi_00
USB\Vid_1058&Pid_0401&Mi_00

Matching device ID:
usb\class_08&subclass_06&prot_50

I hope that is all you wanted.  Let me know if there is anything else.  Stay safe.

dgroover -

You have the destination end of the bridge - the device controller - covered very well.  Now, we even know the chipset of the PCI-to-USB host adapter - but I am still curious about the detailed properties of any and all lines that contain the word 'Enhanced' or 'USB2'.

"...On the host end of the "bridge", the useful items are in properties of only those terminal "branch(es)" on the Universal Serial Bus controllers "tree" containing the word 'Enhanced'..."

(6) for USB Mass Storage Devices, skip down to (7) - else for USB 2.0 controllers, focus on those lines containing either the abbreviation 'USB2' or the word 'Enhanced', then go to (7);

(7) right click on any such lines that drop down, then left click on Properties;...

The Hardware Ids will start with the characters 'PCI\'.  In the image below, look on the line right above the red arrow for the word 'Enhanced'...

http://img.photobucket.com/albums/v235/El_Pescador/PHR100AAs.jpg

I am marveling at the fact that I still have electric power and DSL service.  I suspect that when dawn breaks, Cindy will have changed all that unless she veers radically to the east during the night.  Right now, the highest winds will strike us from the NORTH if she holds to the current track.

[glb]El Pescador[/glb]

El_Pescador

Hope you are surviving the weather issues okay!

If this helps your data base information:

I have an Adaptec PCI USB 2.0 adaptor card.  From Device Mgr:

'Adaptec AUA-3121 PCI to USB Enhanced Host Contoller'

Hardware Ids--last two lines:

PCI\VEN_1033&DEV_00E0&CC_0C0320
PCI\VEN_1033&DEV_00E0&CC_0C03

Matching Device Id:

pci\ven_1033&dev_00e0&subsys_02e09004

*****************************************

And I have an Iomega USB 2.0 'purpose built' 40 GB HDD:

Hardware Ids:

USB\Vid_059b&Pid_0075&Rev_1100
USB\Vid_059b&Pid_0075

Matching Device Id:

usb\class_08&subclass_06&prot_50

Both the Norton Ghost USB driver and the Panasonic USB driver work fine with this combination.

dgroover

As you may have gathered from El_Pescador, not every USB controller chipset is compatible with every DOS USB driver.

1.  Have you tried the Norton Ghost USB DOS driver using the Ghost Boot Wizard?

2.  I assume you are loading the Panasonic USB driver v2.06.  There has been two additional versions released that you could try:

v2.15, size=39,093, dated 10/26/2003

v2.20, size=39,179, dated 11/07/2004

These are self-extracting files.  You will find USBASPI.SYS in the F2H subdirectory.

Let us know if the newer versions offer compatibility with your PCI USB add-in controller card.

NightOwl wrote on Jul 6^th, 2005 at 1:54pm:

"... And I have an Iomega USB 2.0 'purpose built' 40 GB HDD: Hardware Ids: USB\Vid_059b&Pid_0075&Rev_1100 USB\Vid_059b&Pid_0075 Matching Device Id: usb\class_08&subclass_06&prot_50 Both the Norton Ghost USB driver and the Panasonic USB driver work fine with this combination..."

My new 80GB USB 2.0 'purpose built' Iomega HDD has the following characteristics -

Hardware Ids:

USB\Vid_059b&Pid_0177&Rev_0001
USB\Vid_059b&Pid_0177

Matching Device Id:

usb\class_08&subclass_06&prot_50

Despite widespread power outages and fallen trees from winds stronger than expected for Tropical Storm Cindy, the anticipated street flooding from rainfall did not occur although there was some very brief tidal flooding along shorelines as the storm center passed to the east of us.  We are watching Hurricane Dennis with a terrible sense of dread, however.

[glb]El Pescador[/glb]

Success!

I used USBASPI.SYS version 2.20 and it found my USB hard drive with no problems and I was able to Ghost both of my internal drives.  Thanks alot guys.

dgroover wrote on Jul 8^th, 2005 at 8:44pm:

"... I used USBASPI.SYS version 2.20 and it found my USB hard drive with no problems and I was able to Ghost both of my internal drives..."

Thanks for reporting back with the good news.  However, for the common good, please consider filling us in on the details posed in the inquiry below:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1095438251;start=32#32

[glb]El Pescador[/glb]

dgroover


Quote:

I used USBASPI.SYS version 2.20 and it found my USB hard drive with no problems and I was able to Ghost both of my internal drives.  Thanks alot guys.

Thanks for reporting back with what worked for you  ;) !

NightOwl wrote on Sep 17^th, 2004 at 1:24pm:

To all Why is this a better driver--see my reasons at the end of this post. I started working on this after I posted this question in this forum and did not receive much response: http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1089728699;start=0#0 The original resources I have used are as follows: http://www.theinquirer.net/?article=10215 http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/ http://www.freedos.org/freedos/news/technote/203.html http://www.computing.net/dos/wwwboard/forum/13447.html http://www.bootdisk.com/usb.htm I will call this the 'Panasonic Universal USB Driver'. So I have created a boot floppy as follows: [config.sys] Device=himem.sys rem :The following line loads Panasonic's universal USB-controller driver rem :those are spaces between the file name and each of the switches rem :The '/e' switch forces USB 2.0 only, remove for USB 1.x also Device=usbaspi.sys /e /v rem :The following is an aspi mass storage driver for usb-connected HDD's rem :and compactflash memory cards rem :The 'Motto Hairu USB Driver' Device=di1000dd.sys Dos=high,umb Lastdrive=z [autoexec.bat] rem :My USB HDD is drive 'l', if you wish, you will have to change this rem :in your path statement to match your USB HDD drive letter path=a:\;c:\;c:\pqmagic;l:\;l:\pqmagic mouse.com rem :Type 'rem' and a space in front of 'ghost' below rem :if you do not want ghost to automatically load on bootup ghost [Files on the Floppy Disk] Autoexec.bat Command.com Config.sys Di1000dd.sys Himem.sys Io.sys Mouse.com Mouse.ini Msdos.sys Usbasipi.sys How to create the boot disk and where to find the files: (I'm using Win98se for the following) -Put a blank floppy in the drive -Open Windows Explorer -Right-click the '3 1/2 ( A: ) -Choose 'Format...' -Select 'Full' and 'Display summary when finished'   and 'Copy system files' -Make sure you have full capacity and no bad   sectors after formating, i.e. a good floppy -Check the files on the floppy, you should have:   Command.com   Drvspace.bin   Io.sys   Msdos.sys -I delete the 'drvspace.bin' as it's not needed -Now create the config.sys and autoexec.bat files   -open Wordpad and copy and paste the text lines under    [Config.sys] above into Wordpad   -then 'save as' config.sys to the floppy in drive A:\   -then open a new document for Wordpad and copy and paste    the text lines under [Autoexec.bat] above into Wordpad   -then 'save as' autoexec.bat to the floppy in drive A:\ -Copy the Himem.sys to the floppy-it can be found in the Windows    directory -Mouse.com can be found in this directory if you have installed   Norton Ghost 2003:     C:\WINDOWS\All Users\Application Data\Symantec\Ghost\Template\common   or if you have PartitionMagic v8.x, it's here:   C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS     -Put a copy of Mouse.com on the floppy disk -The first time Mouse.com runs when you boot, it will create Mouse.ini   on the floppy for you -The last two files are found on Rad's download page at the bottom where   it says 'USB-DOS files':  http://radified.com/Files/ -After you download the 'usb-dos.zip' file, you will need to extract the files -The kxlrw40an.exe is a self-extracting file you have to execute   -it contains the Panasonic Driver 'usbaspi.sys' in the F2H directory   -copy the 'usbaspi.sys' file to the floppy -The mhairudo.zip has the di1000dd.sys file   -extract the file   -copy it to the floppy   -Warning:  There is a 'usbaspi.sys' file here too--it's the wrong    one!  Use the one above from the kxlrw40an.exe file. So what have I done here: Ghost will not fit on the boot floppy with the other drivers and files.  So I have copied the Ghost.exe to the root directory of the C:\ drive.   PartitionMagic v8.x has a sub-directory labeled 'DOS' (C:\Program Files\PowerQuest\PartitionMagic 8.0\DOS) which has the necessary dos files to run PartitionMagic under dos.  So I created a sub-directory on the C:\ drive and I labeled it 'pqmagic' and copied the files from PartitionMagic's DOS sub-directory to my 'pqmagic' directory.  I chose 'pqmagic' because that's the program name that loads PartitionMagic when using dos and it reminds me what to type to start PartitionMagic. My USB 2.0 hard drive always gets the drive letter 'L' assigned to it when booting, so I have put drive letter 'L' in the autoexec.bat path statement (you will have to change your path statement to match your USB HDD letter, if you wish this functionality), and also copied Ghost.exe and the 'pqmagic' sub-directory to the USB 2.0 hard drive's root directory.  So if the C:\ drive has been trashed, then the files are available on the USB 2.0 hard drive too. In the autoexec.bat path statement, I have told the dos session to look for Ghost.exe and Pqmagic.exe in A:\, C:\, C:\pqmagic, L:\, and L:\pqmagic, and once it finds the program file, it will load and open the program.  I have set the command in the autoexec.bat file to run Ghost automatically when I boot.  If you do not want this to happen, delete the 'Ghost' line, or put 'rem + a space' in front of the 'Ghost' line so the line is ignored when read during bootup. So why is this a better USB 2.0 DOS driver?: 1.  When booting it loads much faster and mounts and assigns drive letters more quickly. 2.  The Panasonic Universal USB driver may be a more 'universal' USB 2.0 driver that is compatible with more USB 2.0 components.  (Symantec clearly states that it's Iomega driver has limited compatibility:  http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999062808022225? 3.  The Panasonic Universal USB driver was able to mount my Adaptec USB 2.0 powered hub and access the HDD through the hub, so I do not have to unplug my USB 2.0 HDD from the hub, and route the wiring directly to the PCI USB 2.0 adapter card port. 4.  The USB 2.0 transfer rate for Ghost was noticeably faster.  Using the Norton's Iomega USB 2.0 driver, I got a image creation speed of 295 MB/min and an image integrity check speed of 374 MB/min.   With the Panasonic Universal USB driver, I got an image creation speed of 551 MB/min, and an image integrity check speed of 1024 MB/min! 5.  Using the Panasonic Univeral USB driver I was able to use the DOS version of PartitionMagic to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to. 6.   Using the Panasonic Univeral USB driver I was able to use Fdisk under DOS to access and perform all partitioning activities on the USB 2.0 HDD, again through the powered hub if I wanted to. 7.  Using the Panasonic Univeral USB driver, if a memory card was loaded in my Lexar USB 2.0 Multi-Card Reader, I was able to mount the card reader, and the driver assigned a drive letter to the memory card, and I had access to the files on the memory card under DOS. I put Ghost.exe on the memory card while in Windows, and then used the memory card to load Ghost after booting to DOS!  And the memory card showed up in Ghost as a drive that could be imaged.  I Ghosted (is that a word? :) ) it and the integrity check was successful! (Note:--I went back and tested Norton's Iomega USB driver and discovered that it too will mount the Lexar Multi-Card Reader if a memory card is in the reader before booting.) 8.  This driver is the same one mentioned in this thread:  http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1075994733   and is referenced in the Ghost Guide here at the bottom of the page:  http://ghost.radified.com/ghost_caveat.htm So based on the information in this thread, the Panasonic driver appears to work fine with a NOTEBOOK & PCMIA CARD USB hardware. Remember, your mileage may vary--this is what worked on my system. I'm hoping El_Pescador is willing and able to try this out on his two USB 2.0 external enclosure kits to let us know if this works for those, and if the performance changes any.  See here: http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1094192056

Thanks again for your help, guys.  Here is the information about my USB PCI card:

USB 2.0 Root Hub HW ID:
{4B571702-E6C6-4db1-A2C6-FD1D53A70FC3}\EHCI_ROOT_HUB
Matching device ID is same except no caps on any letters.

ALi PCI to USB Enhanced Host Controller HW ID:
PCI\VEN_10B9&DEV_5239&SUBSYS_523910B9&REV_01
PCI\VEN_10B9&DEV_5239&SUBSYS_523910B9
PCI\VEN_10B9&DEV_5239&CC_0C0320
PCI\VEN_10B9&DEV_5239&CC_0C03

Matching Device ID:
pci\ven_10b9&dev_5239&cc_0c03

Mass Storage Device HW ID:
USB\Vid_1058&Pid_0401&Rev_0412&Mi_00
USB\Vid_1058&Pid_0401&Mi_00

Matching Device ID:
usb\class_08&subclass_06&prot_50

If there is anything else, let me know.

[quote author=dgroover  link=1095438251/30#40 date=1121372265]"... Here is the information about my USB PCI card -

ALi PCI to USB Enhanced Host Controller HW ID:
PCI\VEN_10B9&DEV_5239&SUBSYS_523910B9&REV_01
PCI\VEN_10B9&DEV_5239&SUBSYS_523910B9
PCI\VEN_10B9&DEV_5239&CC_0C0320
PCI\VEN_10B9&DEV_5239&CC_0C03

Matching Device ID:
pci\ven_10b9&dev_5239&cc_0c03

Mass Storage Device HW ID:
USB\Vid_1058&Pid_0401&Rev_0412&Mi_00
USB\Vid_1058&Pid_0401&Mi_00

Matching Device ID:
usb\class_08&subclass_06&prot_50..."[/quote]dgroover -

The two tables below illustrate USB 2.0 host controller and USB 2.0 device controller specifications I have gleaned while trying to ensure compatibility of USB 2.0 external HDD enclosure kits with DOS-based Norton Ghost 2003:

http://img.photobucket.com/albums/v235/El_Pescador/HostHdws.jpg

http://img.photobucket.com/albums/v235/El_Pescador/HDDHdws.jpg
From what I could tell up until now, USB 2.0 host controllers have eventually shaken out to either VID=8086h or VID=1033h - and no other thusfar.  Thanks to your cooperative efforts, we now know of a third USB 2.0 host controller category - tentatively VID=10B9h !!!

Take note on the CONTROLLER line in the image below where VID=8086h and VID=1033h appear, and whenever possible transcribe the counterpart for your PCMIA controller when you are initiating a DOS-based Ghost 2003 procedure.  Altering your config.sys to reflect the following: Device=usbaspi.sys /e /w /v will facilitate matters.  It may very well to turn out to be VID=10B9h, but we won't know for sure until you report back.

Actually, the bottom line here is that the string values found in the VID= statement are very useful in choosing between file system formats - FAT32 or NTFS - in USB 2.0 external devices.

http://img.photobucket.com/albums/v235/El_Pescador/ByteccIVs.jpg

[glb]El Pescador[/glb]

Hmmm,

I am goin'crazy. Barts PE did not quite work for me. Creating boot disks the way you guys did (i followed the thread using MagicIso) did not lead to the desired result.
I have just spent two whole weeks reinstalling my machine and I really need to have a bootable CD for XP home with Ghost on it so that I can restore my backup.

I created a bootable CD with Ghost on it but when starting I get an error saying that I need to eject the disc and to press a key. Do these bootable CD's work for XP?
Pls help I am in deep trouble as I have to process some wedding pictures, snik.....

wrote on Jul 21^st, 2005 at 4:00pm:

"... I am goin'crazy ... Barts PE did not quite work for me ... I am in deep trouble as I have to process some wedding pictures, snik..."

Are 3.5-inch floppies completely outside your setup ?

[glb]El Pescador[/glb]

Wow, quick response!
Actually floppy is in the setup it is just that I prefer a bootable CD. Is it possible to use a Win98 startup disk for XP Home?

Bjorn


Quote:

Is it possible to use a Win98 startup disk for XP Home?

No--WinXP Home does not work with Win98 DOS  ;) !  But the Win98 startup disk may boot your system to DOS okay.

If you have a floppy drive and boot floppy disk to your liking, most CD burning programs will create a bootable CD by reading the boot floppy and burning it to the CD.

Here's another resource--works with floppy drives as well:

Creating Bootable CD/DVD's Without A:\Floppy Drive

Okay, It took a while but i managed using nero. I burned a cd with ghost and pq magic on it plus the panasonic usb 2.0 driver.
But, on starting it uses the Caldera Dos (as expected). I pressed F8 to go through it step by step and after saying something like the detection of my usb controllers it stops with HIDEVICE A:\ somethin'.
So, I tried to let it run through the routine all by itself and it seemed that it detected the external HDD drives. Although i could barely see that as i could not stop it via the BREAK button. and then again the system stops.
Any idea on how to walk through the start up routine or what i might do wrong?

Okay some more data:

USB external WD Media center (250GB) with 2 card reader slots. 3 partitions with 1 FAT32 (h:\), NTFS (i:\ and j:\).

CD-Rom on Z:\
Standaard enhanced pci to usb-hostcontroller:PCI\VEN_8086&DEV_24DD&SUBSYS_80A61043&REV_02\3&267A616A&0&EF

compatible id's are:
PCI\VEN_8086&DEV_24DD&REV_02
PCI\VEN_8086&DEV_24DD
PCI\VEN_8086&CC_0C0320
PCI\VEN_8086&CC_0C03
PCI\VEN_8086
PCI\CC_0C0320
PCI\CC_0C03

twice USB mass storage:
1st id: USB\VID_1058&PID_0400&MI_00\7&2EF3404E&0&0000
1st compatible id:
USB\Class_08&SubClass_06&Prot_50
USB\Class_08&SubClass_06
USB\Class_08

2nd id: USB\VID_1058&PID_0600\050115503B4F
2nd compatible id:
USB\Class_08&SubClass_06&Prot_50
USB\Class_08&SubClass_06
USB\Class_08


hope that helps you and me to find the solution to my dilemma.
cheers,
Bjorn

wrote on Jul 21^st, 2005 at 7:46pm:

"... USB external WD Media center (250GB) with 2 card reader slots. 3 partitions with 1 FAT32 (h:\), NTFS (i:\ and j:\) ... PCI\VEN_8086&DEV_24DD&REV_02 ... USB\VID_1058&PID_0400&MI_00 ... USB\VID_1058&PID_0600..."

Based on the case of Piikea's Western Digital external HDD troubles, this looks like another perfect candidate for NightOwl's Panasonic Universal USB Drive routine - and I would strongly suggest using the v2.20 version (CLICK HERE) of Usbaspi.sys.

It looks like the USB 2.0 ports are emanating from the systemboard with the VID=8086h USB host controller hardware - and this alone frequently necessitates using the Panasonic drivers with USB external devices whenever the FAT32 file system format is in play - but the VID=1058h is not familiar USB device controller hardware.

[glb]El Pescador[/glb]

Aye, I used the panasonic 2.20 version but PC simply gets stuck as I described.

Bjorn


Quote:

Okay, It took a while but i managed using nero. I burned a cd with ghost and pq magic on it plus the panasonic usb 2.0 driver.

You will have to be more step-by-step detailed in the 'how I did it' in order to see what may be wrong.  It's the little details that usually trip us up.

And, you have to take the time to write down the error messages and report them 'exactly' if you hope we might have a chance at figuring out what's wrong without sitting next to you watching your computer!

I don't know what to do with:


Quote:

it stops with HIDEVICE A:\ somethin'

Maybe, .... try 'somethin'  ;) !

Are you trying to create a bootable CD from a floppy boot disk that works successfully when booting from the floppy drive?

Hello again,

Okay, sorry about that I guess it all frustrates me so much that I could simply not bear to write details at 2 am....:)

What I did was following the manual you referred to earlier. I also put on that disk the Panasonic USB driver 2.20 as described. Below you will find all details on that matter.
I have created the bootable CD using Nero (worked fine).

When I put in the CD I press F8 after I started from CD I get into the step by step routine. When I keep pressing one of the options per step (n,y,r) it goes fine to some point.
Then it ends mostly after the DPMS stuff with:
[Dr-Dos] A:\> and a blinking cursor. I cannot type anything with my cordless keyboard. Neither can I press the break button in order to see whether or not the usb driver recognized my external HDD.
2 questions:
1.) Could it be the keyboard by any chance?
2.) Why do I need the IBMDOS and IBMBIO stuff?Is the command.com not enough?

So, sorry I cannot really give you a specified error message as it at one point simply stops and the next time I restart it stops somewhere else. Unfortunately I do not have a wired keyboard. However, it should work I guess as in the XP recovery console, which also uses DOS stuff the keyboard works. I hope you can help again.

Below you will find some more details on my bootable CD and PC±
1.) Here is my configuration with drives etc.:
Floppy on a:\
internal HDD with XP Home on c:\
and two more partitions on d:\ and e:\ (all are NTFS)
CD-Rom Drive on z:\
Emulated CD on y:\

external WD 250GB with 3 partitions:
h:\ (Fat32 but I want to make it NTFS)
i:\ and j:\ (both are NTFS)
This is my USB external WD Media center (250GB) with 2 card reader slots and I would like to store my ghost image of my internal HDD.

Here are my USB controller details:
Standaard enhanced pci to usb-hostcontroller:PCI\VEN_8086&DEV_24DD&SUBSYS_80A61043&REV_02\3&267A616A&0&EF

compatible id's are:
PCI\VEN_8086&DEV_24DD&REV_02
PCI\VEN_8086&DEV_24DD
PCI\VEN_8086&CC_0C0320
PCI\VEN_8086&CC_0C03
PCI\VEN_8086
PCI\CC_0C0320
PCI\CC_0C03

twice USB mass storage:
1st id: USB\VID_1058&PID_0400&MI_00\7&2EF3404E&0&0000
1st compatible id:
USB\Class_08&SubClass_06&Prot_50
USB\Class_08&SubClass_06
USB\Class_08

2nd id: USB\VID_1058&PID_0600\050115503B4F
2nd compatible id:
USB\Class_08&SubClass_06&Prot_50
USB\Class_08&SubClass_06
USB\Class_08
----------------------------------------------------------
2.) Now, my autoexec and config. They look like this:
[Autoexec]
@echo off
SET TZ=GHO-01:00
path=z:\;z:\ghost;z:\pqmagic
MOUSE.COM
LH \Mscdex.exe /d:mscd001 /l:x /m:16 /v
echo Loading...
CD \GHOST
GHOST.EXE
goto END

[config.sys] / leave behind all the remarks please.
rem :The following line loads WD's universal USB-controller driver
rem :The spaces between the filenames and the parameters are
rem :'/e' forces USB 2.0 only, remove for USB 1.x also

[menu]
menuitem = FROMCD, This computer was started from a GHOST bootable CD

[FROMCD]
[COMMON]
DEVICE = usb\usbaspi.sys /e /v /w
rem :DEVICE = usb\aspiohci.sys /int /all
rem :DEVICE = usb\aspiuhci.sys /int /all
rem :The following is an aspi mass storage driver for usb-connected HDD's
rem :and compactflash memory cards
DEVICE = usb\di1000dd.sys
DEVICE = oakcdrom.sys /d:mscd001
LASTDRIVE = Z
----------------------------------------------------------
3.) These are the files I have on my bootable cd
a.) All of these reside in the bootable image I created with the manual you gave me
of course autoexec.bat and config.sys
help.bat
command.com
edit.com
format.com
aspi2dos.sys
aspi4dos.sys
aspi8dos.sys
aspi8u2.sys
aspicd.sys
aspiohci.sys
aspiuhci.sys
btcdrom.sys
btdosm.sys
flashpt.sys
di1000dd.sys
io.sys
oakcdrom.sys
usbaspi.sys
mscdex.exe
mscdexnt.exe
attrib.exe
chkdsk.exe
debug.exe
ext.exe
guest.exe
scandisk.exe
format.com
restart.com
sys.com
edit.com
IBMBIO.com
IBMDOS.com
MOUSE.com
Mouse.ini
scandisk.ini
----------------------------------------------------------
4.) I have added two directories to the disk:
\pqmagic (all partition magic dos files)
\ghost (here is the ghost.exe)
----------------------------------------------------------

wrote on Jul 22^nd, 2005 at 4:16pm:

"... and a blinking cursor. I cannot type anything with my cordless keyboard. Neither can I press the break button in order to see whether or not the usb driver recognized my external HDD. 2 questions: 1.) Could it be the keyboard by any chance? 2.) Why do I need the IBMDOS and IBMBIO stuff?Is the command.com not enough? So, sorry I cannot really give you a specified error message as it at one point simply stops and the next time I restart it stops somewhere else. Unfortunately I do not have a wired keyboard. However, it should work I guess as in the XP recovery console, which also uses DOS stuff the keyboard works. I hope you can help again..."

I would be very suspicious of the keyboard, and would certainly try to borrow a conventional model from a friend. Yet, then again, try one more time with this modified line:

DEVICE = usb\usbaspi.sys /e /v /w /norst

Also, you might consider working from within Windows as illustrated below (the advantage being that, no matter what, you will have a detailed log when you return to Windows):

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1104185611;start=0#0

http://img.photobucket.com/albums/v235/El_Pescador/Pana.jpg

[glb]El Pescador[/glb]

Bjorn


Quote:

What I did was following the manual you referred to earlier. I also put on that disk the Panasonic USB driver 2.20 as described. Below you will find all details on that matter. I have created the bootable CD using Nero (worked fine).

1.  Looking at the information you posted futher down after this quote from your last post regarding the *config.sys* and *autoexec.bat* files, I'm not sure I know what *manual* outline you are following--could you be specific, because I don't recognize the source of the batch files?

2.  Did you create a bootable floppy with PC-DOS OS on it first, and then modify it with the files that you list later in your post--and did you then use that floppy in Nero to create the bootable data CD?

I'm going to use your posting details to try and re-create what you have done to see if I can find any problems and duplicate your issues.  Will post the results later when I'm done.

Bjorn

I did not create a boot CD from your information--just a boot floppy disk--and used it for testing--here's the problems I found and the suggested changes that should help:

[config.sys]

rem :The following line loads WD's universal USB-controller driver
rem :The spaces between the filenames and the parameters are
rem :'/e' forces USB 2.0 only, remove for USB 1.x also

[menu]
menuitem = FROMCD, This computer was started from a GHOST bootable CD

[FROMCD]
[COMMON]
REM  by NightOwl  DEVICE = usb\usbaspi.sys /e /v /w
DEVICE=usbaspi.sys /e /v
rem EVICE = usb\aspiohci.sys /int /all
rem EVICE = usb\aspiuhci.sys /int /all
rem :The following is an aspi mass storage driver for usb-connected HDD's
rem :and compactflash memory cards
REM by NightOwl  DEVICE = usb\di1000dd.sys
DEVICE=di1000dd.sys
DEVICE = oakcdrom.sys /d:mscd001
LASTDRIVE = Z

In the first problem line above, the *usb\usbaspi.sys* is telling config.sys to look for *usbaspi.sys* in the subdirectory *usb*, but you have put *usbaspi.sys* in the 'root directory', and not in a subdirectory.

Also, unless you are booting from a USB floppy drive, and need to unplug it and plug-in a USB CD-ROM drive, the is no need for the */w* switch--which is a 'wait until I plug in the USb CD-ROM drive' switch before continuing to process the rest of the batch file.

The second problem line is the same issue of telling config.sys to look for the driver in a subdirectory.

[autoexec.bat]
@echo off
SET TZ=GHO-01:00
path=z:\;z:\ghost;z:\pqmagic
MOUSE.COM
REM by NightOwl LH \Mscdex.exe /d:mscd001 /l:x /m:16 /v
Mscdex.exe /d:mscd001 /l:z /m:16 /v
echo Loading...
Z:
CD \GHOST
GHOST.EXE  
goto END

In your previous post, you said your optical drive is assigned drive letter Z: in WinXP.  You also mention an 'emulated CD-drive' using Y:.  Now, I assume the emulated CD-drive is not loaded when booting to DOS, so the only CD drive in DOS will be the one optical drive.

Based on the 'path=' statement in your autoexec.bat, I'm assuming you wish the drive letter to be Z: in DOS also.  So you have to change the drive letter assignment switch in the 'mscdex.exe' line from 'l:x' to 'l:z'.

A minor point, because DOS will ignor it, but the 'LH' (load high) command in front of the 'mscdex.exe' file has no effect unless you load a 'high memory manager' such as *himem.sys* first in config.sys.

And, because the Ghost program is going to be on the data portion of the CD which is accessed in DOS from the Z: drive, you need to change to that drive by using the 'Z:' command before using the 'CD \Ghost' (change directory) command line.

Report back with your progress in resolving your problems.

Okay, back from germany from the weekend.
Installed my external HDD on another win98 PC also with the Panasonic driver. Worked great although it cost a lot effort to get there.

And that also gave me a fresh view on my own issues. But first things first:
- I changed the files as you suggested. I saw the flaws with the directories (\usb) also. However, I did not try this CD on my home PC yet as I first wanted to see whether things were caused by my wireless keyboard.

- I tried the CD on a laptop in the weekend and guess what: It recognized my USB drive and even gave the indication on the transfer speed. And all typed commands after the DOS prompt worked out. So I figured out that if you burn a bootable CD with NERO it will use the CALDERA DOS which does obviously not recognize wireless keyboards.
However, although the laptop recognized my external HDD there was no drive letter assignment. I thought that it might be due to the fact that the CD was customized for my own home PC and that's why the drive letters would not match. So I decided to first try again that same disc on my home PC (I did before but then the directories were set wrongly).

- But I was still wondering why the caldera DOS would always be used. I took a look in the NERO directory with the DOSBootimage file
(Nightowl, you suggested to replace the DosBootimage file -
[glb]" placed a copy of my boot image file (bootcdp1.ima ) in the 'Nero' subdirectory along with Nero's re-named 'DOSBootimage.old.ima' file.  I then renamed my boot image file (bootcdp1.ima) to 'DosBootimage.ima' .   So, it looks like this now--screen shot." [/glb]
- that's not I would put it). When you replace it Nero justs grants you (in the 'Select Boot Image' screen) to select from floppy. So, what I did is copying the contents of my Image - the one I will also put as an image to the bootable CD (without the \ghost and \pqmagic folder) to a floppy and just let Nero read it when creating the bootable disc. I am not able to send screen prints so I suggest that you include it in your description at http://nightowl.radified.com/bootcd/neroexpress6.html.

(Edited above link by NightOwl so it works!)

- After that I let it burn the CD and I put in the CD in my home PC and guess what it recognized the external HDD. [glb]SO< I FINALLY MANAGED!!!!![/glb]

- Strange on that matter was, that the drive letters are not set right. my external HDD has drive letter C:\ and I have the Z:\ for my CD drive. So, I still have to figure that out. I also have the issue with the codepage as I need to have the dutch codepage but I have an idea on how to do that.

- So, what remains is the drive letter assignment. If you have any suggestions I would appreciate your help again.

Thanks already for all the help you provided until now. I really appreciate that.

Regards,
Bjorn

Just a short update on my progress.....
....well progress regarding gathering of information as I did not quite manage to mount my NTFS drives.

Right now I am using a floppy with the necessary dos files (except the folders pqmagic and ghost). This is just for testing purpose and when that will work I am going to burn my bootable cd.

I used ntfsdos which should very well be able to mount all ntfs drives in read mode. That should do as I want to just read them and back them up to my external FAT32 drive.

So, at the command prompt I type ntfsdos and then it starts mounting. However, after the last drive is mounted I get and error message saying that there is no access to command.com system halted.
This is strange as the command.com just resides on my floppy.

Any ideas??
Greets,
Bjorn

Okay, not really done any visible progress.

My main problem now is:
Basically the only drive that is recognized is the FAT32 partition of my external HDD. All other drives are NTFS and do not have any drive letters.
When I try to use NTFSDOS I get a memory allocation error saying '....could not allocate memory...'. Then it says '...could not find command.com...system halted'. Strange, as the command.com is present and not hidden on the bootable floppy.
Any ideas on that one?

Furthermore, I tried to install the dutch codepage with the syntax:
country=031,850,country.sys
install=mode.com con cp prepare=((850) ega.cpi)
install=mode.com con cp select=850
install=keyb.com nl,,keyboard.sys

With the necessary files keyboard.sys and ega.cpi present on the floppy it should be no problem. But I get an error. rebooting with the other PC now and see what error it is again.

-----------------------------------------------------------------------
1.) [autoexec]
@echo off  
SET TZ=GHO-01:00  
path=z:\;z:\ghost;z:\pqmagic  
DRFAT32.exe /m:120 >NUL
MOUSE.COM  
Mscdex.exe /d:mscd001 /l:z /m:16 /v
echo Loading...  
Z:
CD \GHOST  
GHOST.EXE  
goto END

-----------------------------------------------------------------------
2.) [config.sys]

rem :The following line loads WD's universal USB-controller driver  
rem :The spaces between the filenames and the parameters are  
rem :'/e' forces USB 2.0 only, remove for USB 1.x also  
 
[menu]  
menuitem = FROMCD, This computer was started from a GHOST bootable CD  
 
[FROMCD]  
[COMMON]  
DEVICE=drfat32.sys /x
DEVICE=usbaspi.sys /e /v /norst
rem :The following is an aspi mass storage driver for usb-connected HDD's
rem :and compactflash memory cards  
country=031,850,country.sys
install=mode.com con cp prepare=((850) ega.cpi)
install=mode.com con cp select=850
install=keyb.com nl,,keyboard.sys
DEVICE=di1000dd.sys
DEVICE=oakcdrom.sys /d:mscd001  
LASTDRIVE=Z  

Bjorn

Sounds like you have made some progress--that's good!

Any of your NTFS partitions will not be seen by the DOS OS--only FAT partitions will be seen and given a drive letter when you boot to DOS.

So if your external drive is the only FAT partition on your system, it will be C:

Ghost has the ability to *see* NTFS partitions in the Ghost DOS interface--but, not by drive letter.  They will be identified as *1:1* for drive 1, partition 1, and *1:2* for drive 1, partition 2, etc., and *2:1* for drive 2, partition 1, etc.  And Ghost can store a Ghost image to a NTFS partition.  But once you exit Ghost back to DOS, you will still not see any NTFS partitions in DOS.



Quote:

So, at the command prompt I type ntfsdos and then it starts mounting. However, after the last drive is mounted I get and error message saying that there is no access to command.com system halted. This is strange as the command.com just resides on my floppy.

I've not played around with NTFSDOS, so I can't say much from experience with it...but, it is supposed to allow you to boot to DOS and read files on NTFS partitions and copy files from a NTFS partition to a FAT partition.  But you will not be able to write any files to a NTFS partition.

If you want full access to NTFS partitions from a bootable CD, you should consider Bart's PE:  Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD

Based on what you've reported, I'm hoping that the problem you're reporting is due to a conflict of drive letter assignments--because your external HDD is C: in DOS, and your WinXP main partition is C: in NTFS--NTFSDOS may be  *seeing* two C: drives when it trys to mount the partitions.

To see if that's true:

1.  disconnect your USB HDD before booting and trying to run NTFSDOS--does that allow NTFSDOS to work okay?

2.  Change the *motto hairu* driver line in config.sys from:

DEVICE=di1000dd.sys      , to

DEVICE=di1000dd.sys /dh

The */dh* is a command line switch that tells the *motto hairu* driver to use as it's first drive letter, the letter *h*.  But your two other NTFS partitions on the external USB HDD will still not be seen in DOS and assigned drive letters by DOS.

Does that allow NTFSDOS to run okay with the HDD hooked up?


Quote:

- But I was still wondering why the caldera DOS would always be used. I took a look in the NERO directory with the DOSBootimage file (Nightowl, you suggested to replace the DosBootimage file -

I continue to be confused by your questions--you seem to be using several different outlines as to how to set up a bootable CD/DVD--and you are mixing and matching the instructions, but you are not changing the information to match the changed combination of DOS boot file command lines.

For instance, you refer to my Guide's instructions  (Nero's OEM NeroExpress6)
to 'replace the DosBootimage file in NeroExpress v6.xx ... with bootcdp1.ima...' by first re-naming DosBootimage.ima to DosBootimage.old.ima, and then re-naming bootcdp1.ima to DosBootimage.ima.  But you state you only get caldera DOS (aka PC-Dos) each time you try to create a bootable CD.

Did you follow my Guide and create the *bootcdp1.ima* file?  If you did, it does not have *caldera DOS*, but only MS-DOS!

NeroExpress v6.xx's *DosBootimage.ima* uses the *caldera DOS* as it's DOS OS.  So, you must be using NeroExpress's default boot image file.

So, I have to believe you are not actually following any one *guide* or outline from beginning to end--and you are ending up with a final result that fails because it does not have a consistent structure.

Another example--in your latest *autoexe.bat* and *config.sys* that you posted--you now have a new program listed:


Quote:

DRFAT32.exe /m:120 >NUL DEVICE=drfat32.sys /x

What's the purpose of that program?  Is that interferring with NTFSDOS and *command.com*?

Hello again,

1.) Regarding the codepage everything works fine now.
2.) I saw some directory entries for emm and himem that prevented the right start up. Fixed it and emm works.
3.) Already had the *motto hairu* driver set with parameter /di.
4.) I downloaded ntfspro and that worked fine. However, still got the memory allocation error. However it should be solved with emm working okay now. Just testing on my other machine.
5.) Regarding the Nero issue. I followed again your step by step course at http://nightowl.radified.com/bootcd/neroexpress6.html.

At some stage I come to this section:
---------------------------------------------------------------------
You are now at the 'Select Boot Image' dialog screen. This is where you find out you do not have the option of selecting any boot image file of your choosing. You only have the option of:

- read a floppy boot disk, or
- use the built-in 'Nero's bootable floppy image.'

The built-in 'Nero's bootable floppy image' will now be our custom boot image file that we created with WinImage and have re-named to 'DOSBootimage.ima' at the beginning of this outline. So:

- Select 'Use standard boot image'
- Select 'English (United State)' for 'Boot Locale'.
---------------------------------------------------------------------
Nero 6.6 only grants me the choice from 1 (!) and that is the option for Read boot disc in drive. But it does not matter really. I have all the files on my floppy as well so I can just let it read the floppy and build the bootable cd from that.
I guess that it has something to do with an internal check for the bootsector for Dr Dos  7 (which is Caldera). I cannot explain otherwise.

Be back in a minute....

Hmmm, I encountered the following issues:

1.) EMM works fine
2.) When starting PQMagic it says "EMM is running. Available memory is limited to 32 MB."
Any idea on how to set emm in config.sys so that the full memory can be used (I installed emm in order to prevent memory allocation error from ntfspro)?
3.) In order to free some memory I deleted the /m:16 value in the autoexec.bat (for the cd-driver)
4.) There is still no mouse support with my logitech wireless mouse. I am curious why this does not work as I have enabled also the on USB 1.1 controllers who should detect the mouse (that would be the /o /u commands right??)
5.) I located the Drfat32 in the Dr Dos directories at Nero and thought that it might help with drive letters etc. but of course then I did not know that Fat32 partitions are recognized by dos. So I deleted the entry.
6.) Okay, now the ntfsdos or pro issue. I said that ntfsdos gave an error. It does not anymore.
However, drive letters are not set right (all partitions are NTFS right now):

internal drive partition C| I:\ ----> this should become C:\
internal drive partition D| J:\ ----> this should become D:\
internal drive partition E| K:\ ----> this should become E:\

external drive partition 1: L:\ ---> this should become I:\.
external drive partition 2: M:\ ---> this should become J:\
external drive partition 3: N:\ ---> this should become K:\

And here I am stuck. Any ideas on how to change that? And you are also very welcome on the other questions marked yellow.

Well, I need to get some sleep now....this is nagging at me!

wrote on Jul 26^th, 2005 at 7:00pm:

"... drive letters are not set right (all partitions are NTFS right now): internal drive partition C| I:\ ----> this should become C:\ internal drive partition D| J:\ ----> this should become D:\ internal drive partition E| K:\ ----> this should become E:\ external drive partition 1: L:\ ---> this should become I:\. external drive partition 2: M:\ ---> this should become J:\ external drive partition 3: N:\ ---> this should become K:\ And here I am stuck..."

Though it may not prove helpful in your predicament, be advised of the trick of giving every HDD partition/logical drive a unique name that reflects both the drive letter in Windows and the file system format, i.e., C: on the Master HDD would be named "C_NTFS", I: on the Slave HDD would be named "I_FAT32".

Then, when running an Integrity Check in Ghost to match the assignments to the respective drives, one would see "C_NTFS" (C:) is assigned "1:1 [C_NTFS] NTFS drive" and "I_FAT32" (I:) is assigned "D: [I_FAT32] Local drive".

In reality, my assignments are shown in the illustration below:

http://img.photobucket.com/albums/v235/El_Pescador/KomboDM.jpg

A real-life Integrity Check in Ghost on my Dell Dimension 8300 reveals the following assignments to the respective drives on the Master HDD: "Boot8300" (C:) is assigned "1:2 [Boot8300] NTFS drive"; "F_Drive" (F:) is assigned "1:3 [F_Drive] NTFS drive"; and "G_DRIVE" (G:) is assigned "C: [G_DRIVE] Local drive".  The missing "1:1" assignment is hidden because it is a Dell Diagnostic partition that has no drive letter assignment in Windows (the Dell Dimension 8100 has no such partition).  On the Slave HDD, one finds: "H_Drive" (H:) is assigned "2:1 [H_Drive] NTFS drive"; and "I_DRIVE" (I:) is assigned "D: [I_DRIVE] Local drive".  Both Windows drive letters D: and E: are assigned to optical drives (CD/DVD).  Take note that names for NTFS drives can be in both upper and lower case, but FAT32 drive names are restricted to upper case.

[glb]El Pescador[/glb]

Hello El Pescador,

That would be exactly what I need! But how do I set these drive letters? To me it is not that obvious how to do that.

Anyway, I was wondering about the following:
When I do the backup, I set everything from windows, so the drive letter assignment should not be a problem. However, in the situation that I need to restart in DOS due to a crash in order to set the backup back the drive letters are missing.

Will this pose a problem for Ghost when restoring the image? With other words do the drive letter assignments used in the backup (e.g. windows directory is on the C:\ drive) indicate where to put the files and will the drive letters be automatically restored?

If so, then there is no problem right?

On the DPMI thing, I found out that I need to install a DPMI driver. So I downloaded it and will do so. Report later!

Oh well, me dumbhead! Now I know what you mean.

About my question before:
The reason I ask is that pqmagic only indicates the various partitions of my disks as *.* or like extended etc. Of course I know due to the names of the partitions what drive letter I usually had (the way you did it might be a bit more obvious though).
Anyway, when I restore the backup (I havn't made yet) there are still no drive letters present. When using NTFSPRO e.g. these newly assigned drive letters do not match the original ones. Files that originally resided on e.g. c:\windows need to be restored on c:\windows and as these drive letters are not present how does Ghost know where to restore the files to? It might then as well restore them on my original I:\ drive as this one now has the c:\drive letter assigned. Do you what I mean? Is this an issue?


Now in ghost I get the error:
"Your program caused a divide overflow error...if the problem persists contact ..."
Any clue on this one?

Bjorn

Based on the drive letter assignment that you are getting with NTFSDOS--it looks like the */di* switch for the *motto hairu* driver forces DOS to start the drive letter assignments at the drive letter I:\--if you remove that switch do you get the correct drive letters?

Are your drive letters F: and G: assigned to your card reader slots in WinXP?  If you put memory cards in the reader before booting to DOS, they would probably also be assigned drive letters by NTFSDOS also.  If the memory card reader and the external HDD partitions are seen in the same order as the drive letters were assigned in WinXP, then they should be in the same order as seen in DOS.

Drive letters in WinXP are assigned and stored in WinXP's registry--so as long as the partition identifiers are kept the same, then WinXP will continue to report those partitions with the same drive letter.

Ghost keeps track of the partitions differently than WinXP--it's based on drive number (as determined by the order seen on the system) and then by partition number on that particular drive.  As long as you do not switch drives to different locations on your HDD controllers, or add HDD's and then restore partitions that were located at a different location when saved, then the drive letters assigned in DOS will have no effect on the restored partition if it's going back to the same place you originally saved it from.

It's if you try to restore partitions to new HDD in new positions on your HDD controllers, that drive letter assignments may not match--this is especially true of your OS partition.


Quote:

2.) When starting PQMagic it says "EMM is running. Available memory is limited to 32 MB." Any idea on how to set emm in config.sys so that the full memory can be used (I installed emm in order to prevent memory allocation error from ntfspro)?

I use a separate boot disc for PQMagic that does not load EMM--not all DOS programs can be run from a single DOS environment--so, if certain programs need certain memory configurations that are not compatible with other programs, you have to use separate boot discs.


Quote:

4.) There is still no mouse support with my logitech wireless mouse. I am curious why this does not work as I have enabled also the on USB 1.1 controllers who should detect the mouse (that would be the /o /u commands right??)

Actually, the *motto hairu* and Pansonic USB drivers are for *mass storage* USB devices--so it may not mount USB support for a mouse driver!  Does your BIOS have an option to enable *legacey USB support*--that may load USB DOS support for a USB mouse.  But, you might have to consider using a serial mouse for your DOS programs.


Quote:

3.) In order to free some memory I deleted the /m:16 value in the autoexec.bat (for the cd-driver)

I doubt that's an issue--more likely it's other memory conflicts of programs that are not getting along with each other .


Quote:

5.) Regarding the Nero issue. I followed again your step by step course at http://nightowl.radified.com/bootcd/neroexpress6.html Nero 6.6 only grants me the choice from 1 (!) and that is the option for Read boot disc in drive.

Did you follow the rest of the guide to create the *bootcdp1.ima* file?

Nero 6.6 may not be the same as NeroExpress6!  In the full Nero program, you may have to enable *expert* settings to use boot image files.


Quote:

That would be exactly what I need! But how do I set these drive letters?

You can change the partition labels in *Disk Management* in WinXP, and PQMagic will allow you to change the partition labels as well.

Another suggestion, make each partition a unique size that's different from the others--record those size numbers and keep them handy when using Ghost!


Quote:

Will this pose a problem for Ghost when restoring the image? With other words do the drive letter assignments used in the backup (e.g. windows directory is on the C:\ drive) indicate where to put the files and will the drive letters be automatically restored?

If you are restoring individual partitions, you have to make sure you are selecting the correct partition on that image for a source, and the correct partition on the correct HDD in order for it to come out right.  If you choose incorrectly, you will over-write the wrong partition--or restore the wrong partition!  That's why labeling the partitions with unique labels can be helpful.

Ghost will not offer you the option of restoring drive letter C: to the *correct* location for you!--you have to tell Ghost where to put things!

Okay, it beats me! I give up....

1.) Due to the dpmi error. I downloaded a driver but it simply won't load, always get a restart. Trying the next driver now.

2.) No success on drive letters yet. It is right I indicated that moto hairu should start with I:\ hoping that this would leave space for C, D, E on my internal drive. but it simply does not work that way.
Based on the drive letter assignment that you are getting with NTFSDOS--it looks like the */di* switch for the *motto hairu* driver forces DOS to start the drive letter assignments at the drive letter I:\--if you remove that switch do you get the correct drive letters?
The answer is NO. The first partition on my external drive is seen as the first drive thus C:\.
The rest is:
internal drive partition C| I:\ ----> this should become C:\
internal drive partition D| J:\ ----> this should become D:\
internal drive partition E| K:\ ----> this should become E:\

external drive partition 1: L:\ ---> this should become I:\.
external drive partition 2: M:\ ---> this should become J:\
external drive partition 3: N:\ ---> this should become K:\

This is really complicated to me. I might as well try to get an elefant in a shoe box....pfft. Any possibility there that you send me your working image by mail or something. I really cannot spend anymore effort on this thing?

Cheers,
Bjorn

Guess what!
I didn't even dare to hope for it but the inthinkable happened. I changed the Nero Image with the usbaspi.sys and the mottu  hairu driver with the DrDos bootsector and restarted.
HDD was detected (I have been here before). Drive letters are still not right although yesterday night I managed for some reason that is the original drive letters were assigned.
I started ghost and created an image of roughly 600 MB of one drive successfully. No issue here.
Next, I tried to create an image of my C: drive (~17GB) and here when trying to create the image to my external drive it stops responding. Ghost says in the status part on the lower left half of the screen that it is "Adding MFT Table File to image".
Right now I am imaging my C: to another partition of my internal drive with fast compression. That seems to work and if everything went well I will just copy that image to my external drive. In case I need to restore it I guess access will work (I hope).

Data transfer is ~740 MB/min (and still going up)

But there are still a couple of issues:
1.) Why does it stop responding when imaging 17GB to my external drive whereas with 600 MB everything goes well?
2.) Why is it not possible to create two images lets say first d: and then C: drive. I get the earlier reported memory allocation error?
3.) Do I need himem or emm in order to get ghost to work error free? Right now, I disabled EMM as i got this strange error before. However, Now DPMS says that I should load EMM as memory manager.
(Ghost error 0004 double page fault - Symantec was obviously not able to solve that:
------------------------------------------------------------------------
http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00176.html
------------------------------------------------------------------------
Cheers,
Bjorn

Okay, max speed is 997 MB/min. Not too bad is it?
created my third image with it. works great.

wrote on Jul 29^th, 2005 at 7:31pm:

"... Next, I tried to create an image of my C: drive (~17GB) and here when trying to create the image to my external drive it stops responding. Ghost says in the status part on the lower left half of the screen that it is "Adding MFT Table File to image"... 1.) Why does it stop responding when imaging 17GB to my external drive whereas with 600 MB everything goes well?.."

How many spanned images are created on the external drive when response stops, and compare the volume of the latest spanned image to the initial image and the image preceding it.

[glb]El Pescador[/glb]

no image files then.
I have redone everything and simply imaged the big c:\ drive last just after a fresh restart. That worked well. However, in the end it stopped again after completing 100% and saying that the image was created successfully.

Additionally to the other 3 questions there is a 4th one:
But there are still a couple of issues:
1.) Why does it stop responding when imaging 17GB to my external drive whereas with 600 MB everything goes well?
2.) Why is it not possible to create two images lets say first d: and then C: drive. I get the earlier reported memory allocation error?
3.) Do I need himem or emm in order to get ghost to work error free? Right now, I disabled EMM as i got this strange error before. However, Now DPMS says that I should load EMM as memory manager.
(Ghost error 0004 double page fault - Symantec was obviously not able to solve that:
------------------------------------------------------------------------  
http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00176.html
------------------------------------------------------------------------ 4.) Image size of a spanned image varies slightly:
initial C is 2097121 kB
span1 is   2097130 kB
span2 is   2097137 kB
span3 is   2097147 kB
span4 is   2097147 kB
span5 is   1457601 kB (for the last one i get the reason but why do the first ones vary in size??)

cheers,
B.

wrote on Jul 30^th, 2005 at 6:31pm:

"... 4.) Image size of a spanned image varies slightly: initial C is 2097121 kB span1 is   2097130 kB span2 is   2097137 kB span3 is   2097147 kB span4 is   2097147 kB span5 is   1457601 kB (for the last one i get the reason but why do the first ones vary in size??)..."

Your sequence here looks perfectly healthy from my viewpoint, and I find the slight variances quite typical.  Verify that the date/time values all make sense, i.e., all on the same day and cover a contiguous span of hours.

[glb]El Pescador[/glb]

Bjorn

To answer a couple of the most recent questions:


Quote:

3.) Do I need himem or emm in order to get ghost to work error free?

As far as I know--No!  I do not load either of those for booting DOS for Ghosting.


Quote:

2.) Why is it not possible to create two images lets say first d: and then C: drive. I get the earlier reported memory allocation error?

What specific autoexe.bat and config.sys are you using when you get this error?


Quote:

Now DPMS says that I should load EMM as memory manager.

Why are you loading DPMS?  What purpose does that program perform?


Quote:

1.) Why does it stop responding when imaging 17GB to my external drive whereas with 600 MB everything goes well?

What specific autoexec.bat and config.sys files are you using when this happens?

Okay, as I have changed the Nero DosBootImage (which is the Caldera Dos) my config.sys and autoexec.bat look different than yours:
------------------------------------------------------------------------
REM DEVICE=A:\DRDOS\EMM386.EXE /OFF
DEVICE=A:\DRDOS\DPMS.EXE
HIDEVICE=A:\OAK\VIDE-CDD.SYS /D:MSCD001
SHELL=A:\COMMAND.COM A:\ /E:512 /P:AUTODOS7.BAT
BREAK=OFF
BUFFERS=15
FILES=20
FCBS=4,4
LASTDRIVE=Z
HISTORY=ON,256,ON
HIDEVICE=A:\DRDOS\DISPLAY.SYS CON=(EGA,,1)

GOTO o_alldrv

CLS
TIMEOUT 30
ECHO   1. Enable maximum memory
ECHO   2. Load USB/FW ODD driver
ECHO   3. Load all drivers
ECHO
ECHO Press 1 - 3
SWITCH o_maxmem,o_maxusb,o_alldrv

:o_alldrv
SET BOOT_OPT=o_std
HIDEVICE=A:\DRDOS\USBASPI.SYS /e /o /u /v /norst
HIDEVICE=A:\DRDOS\di1000dd.SYS
HIDEVICE=A:\DRDOS\SETVER.EXE
GOTO o_std

:o_maxusb
HIDEVICE=A:\DRDOS\USBASPI.SYS /e /o /u /v /norst
HIDEVICE=A:\DRDOS\di1000dd.SYS

:o_maxmem
SET BOOT_OPT=o_maxmem

:o_std
COUNTRY=001,,A:\DRDOS\COUNTRY.SYS
SET CODE_PAGE=437
SET KEYB_LO=US+

DOS=HIGH,UMB
------------------------------------------------------------------------

What does DPMS do? What it exactly does I do not know but it has obviously to do with handling and assigning memory resources. It is like DPMI which Ghosts asked for earlier when no memory handler was assigned and obviously you need it for NWCache.
Actually, I did not put the entry there but I am happy that Ghost at least works.
------------------------------------------------------------------------
My autoexec.bat:
@ECHO Off
PATH A:\DRDOS;A:\NR;A:\

GOTO %BOOT_OPT%

:o_std
REM LH FAT32
REM LH NTFSREAD

:o_maxmem
LH A:\DRDOS\nwcdex /D:MSCD001 /l:z /v
MODE CON CP PREP=((%CODE_PAGE%) A:\DRDOS\EGA.CPI)
MODE CON CP SELECT=%CODE_PAGE%

KEYB %KEYB_LO%
VERIFY OFF
PROMPT [DR-DOS] $P$G
SET DRDOSCFG=A:\DRDOS
NLSFUNC A:\DRDOS\COUNTRY.SYS
CHCP %CODE_PAGE%
NWCACHE 7670 1024 /LEND=ON /DELAY=OFF
VER /R
------------------------------------------------------------------------

Bjorn


Quote:

The DPMS standard (Display Power Management Signaling) was developed to extend the useful life of PC monitors as well as to conserve the relatively high amount of energy used by monitors when not required.

Quote:

DOS Protected Mode Interface (DPMI) Created for Windows version 3.0, DPMI is an industry standard for an interface that allows DOS applications to access extended memory of the 80286-, 80386-, and 80486-based PC architecture while maintaining system protection.

Why would you want those programs using up DOS memory to run a DOS utility program such as Ghost?

Looking at your config.sys and autoexec.bat, you're loading so much **** (junk ?!  ;) ), you are no longer dealing with a Ghost problem--you are troubleshooting DOS memory management problems and conflicts.

I wish you well  ;) .

Hah,

Finally I have managed....not with Nero though but with Roxio.
All issues I dealt with were obviously caused by the Caldera-Dos.
Now, that I have created a MS-DOS bootable CD everything works just fine!!

Thanks guys!

Hello everyone -
I found this thread and website  by googling "ghost usb 2" and have found it very helpful!  Thank you all for the wonderful tutorial.   :D

Using the steps in the very first post of this thread (but with v2.20 of Panasonic Universal USB Driver) I am cloning to my external at a pretty good clip, but I'm still not as fast as some of the other users.  I'm maxing out at about 478 MB/min while imaging to USB HD, but USB 2 (and my enclosure) should still be alot faster.  The spec for USB 2 (and my enclosure) is 480MB/sec (per second!!)  

Can anyone think of a way to get this any faster?  If I could get into the 1000 or 1500 MB/min or faster that would be awesome!

For the record, here is my gear:

PC:  Dell Dimension 3000, P4, 3.0 GHz CPU, 800 MB FSB, 512 MB RAM, 80 GB HD

USB Enclosure:  An Ultra ULT-31310 Combo (USB 2 / IEEE1394) to IDE, with enclosed Maxtor DiamondMax 250 GB EIDE HD, 7200/16MB/ATA-133  

Regards,
Jim

wrote on Aug 11^th, 2005 at 4:54pm:

"... but I'm still not as fast as some of the other users.  I'm maxing out at about 478 MB/min while imaging to USB HD, but USB 2 (and my enclosure) should still be alot faster.  The spec for USB 2 (and my enclosure) is 480MB/sec (per second!!)   Can anyone think of a way to get this any faster?  If I could get into the 1000 or 1500 MB/min or faster that would be awesome!...

The surname 'Flournoy' is evocative of Caddo Parish, Louisiana - but, nevermind, let's get down to business:

USB 2.0 = 480 Mbps (megaBITS per second) = 60 MB/s (megaBYTES per second) ::)

I don't know what you mean by 'maxing-out', but I do know that on my Dell Dimension 8300 I can use Fast Compression in a Norton Ghost 2003 "disk-to-image" Backup procedure to generate seven 2GB spanned images in less than 15 minutes with my SATA-150 external HDD; my best USB 2.0 rig will take 25-to-28 minutes to do the same job.


El_Pescador wrote on May 21^st, 2005 at 4:16pm:

"... The Intel USB host controller drivers typically found on motherboards can cause greater expense to rectify than employing a communications tactic using tomorrow's technology rather than that from yesterday; the SATA hardware of the future will be backwards compatible just like USB 2.0 hardware is with USB 1.1: USB 2.0 = 480 Mbps (megaBITS per second) = 60 MB/s (megaBYTES per second) FireWire 400 = 400 Mbps (megaBITS per second) FireWire 800 = 800 Mbps (megaBITS per second) SATA = 1,500 Mbps (megaBITS per second) SATA II = 3,000 Mbps (megaBITS per second) SATA III = 6,000 Mbps (megaBITS per second) SATA has no host controller/device controller baggage like either USB 2.0 or FireWire, i.e., a PC system categorizes both USB and FireWire devices as external whereas an external SATA device - despite its own power supply and its own cooling fan - is regarded as internal. BTW, you can readily boot from an internal SATA HDD mounted in an external enclosure kit as referred to below - try to do that without major USB issues or minor FireWire issues.  So, consider 'thinking outside the box'..."

[glb]El Pescador[/glb]

El-
By "maxing out at 478 MB/min" I just meant this is the speed at which I ghost the USB image.

I see your point about the difference between MB/s and Mbps, but still 60 MB/s is much faster than 478 MB/minute

60 MB/s = 3600 MB/min

therefore, I'm still getting only 478/3600 or 13% of the USB 2 standard.  Thats the number I'd like to improve on.  

How much RAM are you running in your 8300 to get those speeds?  Do you think RAM is a factor in this?  

BTW - TX, OK, and MO, but I don't know any in LA...
Jim

Jim Flournoy


Quote:

therefore, I'm still getting only 478/3600 or 13% of the USB 2 standard.

USB is a Windows *standard*--not a DOS standard--based on most peoples' posts and own experience--you are getting about what most folks report for speed with USB 2.0.

I suspect that it is more likely *CPU cycles* rather than RAM that is the critical factor in DOS UBS performance--but I'm guessing on that one.

wrote on Aug 12^th, 2005 at 5:15am:

"... 'maxing out at 478 MB/min' I just meant this is the speed at which I ghost the USB image... BTW - TX, OK, and MO, but I don't know any in LA..."

I don't understand exactly how you are deriving '478 MB/min', i.e., with my best USB device I usually start off around 1,500-to-1,700 and taper off to 550-to-650 nearing completion.  So, is '478 MB/min' a snapshot value or a result of some sort of calculation - please explain.

I have two 512MB sticks of primo OCZ for RAM in the 8300, but I agree with NightOwl about the CPU cycles.  I have three Dell Dimension desktops on my LAN - 8300, 8100, L400c - and, despite being maxed out at 512MB RAM, the L400c Celeron just positively oozes along in Ghost 2003.

To see how I have managed to improve performance with FAT32 partitions in Ghost 2003, CLICK HERE. This refers to both internal SLAVE HDDs and to external HDDs connected via USB, FireWire and SATA.

BTW - Caddo Parish (Shreveport), LA adjoins TX and AR with OK nearby to the northwest and MO on far side of AR to the north.  J. Howell Flournoy was the High Sheriff for decades when I was a youngster, and Flournoy was a well-respected family name throughout the parish back then.  I moved away almost 40 years ago, but the community is still close to my heart.

[glb]El Pescador[/glb]

wrote on Aug 11^th, 2005 at 4:54pm:

"... Using the steps in the very first post of this thread (but with v2.20 of Panasonic Universal USB Driver) I am cloning to my external at a pretty good clip, but I'm still not as fast as some of the other users... For the record, here is my gear: PC:  Dell Dimension 3000, P4, 3.0 GHz CPU, 800 MB FSB, 512 MB RAM, 80 GB HD USB Enclosure:  An Ultra ULT-31310 Combo (USB 2 / IEEE1394) to IDE, with enclosed Maxtor DiamondMax 250 GB EIDE HD, 7200/16MB/ATA-133..."

I am assuming your highly-rated external enclosure kit would not function in Ghost 2003 with the stock Norton/Iomega drivers extracted from Guest.exe, and that is a puzzle.  Do consider that all three of my Macally USB 2.0 PHR-series work just fine with all brands of IDE HDDs up 120GB, but my 160GB Seagate requires NightOwl's Panasonic Universal USB Driver routine (CLICK HERE to view using same inside Windows) to function whereas my 160GB Maxtor does not.

Therefore: (1) I wonder if the 250GB volume of your DiamondMax is an issue; and (2) have you ever used FireWire during your Ghosting sessions?

[glb]El Pescador[/glb]

EL - Thanks again for the tips.  I guess I can live with the speeds I'm getting.  You're right about the speed starting off around much faster, about 1500 MB/min and taper off to around 500 at the end.  It seems that I always want to push it faster when I can!  

As far as the talk about CPU cycles, that is not changeable in my dell, right?  I didn't see anyway in Bios to change it. I saw somewhere that the memory speed is 333, even though I run PC3200

As far as your question about the Guest.exe drivers, I never tried those.  The only thing I've taken from Ghost 2003 is the ghost.exe, and that is how I'm ghosting (of course with the panasonic drivers.)  

Anyway, thanks again.  

Jim

[quote author=jf38081  link=1095438251/75#81 date=1124407361]"... about CPU cycles, that is not changeable in my dell..."[/quote]
You could do what David_L6 does... buy Dell parts and components off eBay and swap out your CPU ... LOL !!! I'm serious - he really does.

[quote author=jf38081  link=1095438251/75#81 date=1124407361]"... As far as your question about the Guest.exe drivers, I never tried those.  The only thing I've taken from Ghost 2003 is the ghost.exe, and that is how I'm ghosting (of course with the panasonic drivers.)..."[/quote]
The first table below illustrates USB 2.0 host controller specifications while the second does likewise for USB 2.0 device controllers.  If you are up to taking a shot at it, how about performing some trials for us and reporting back so I can flesh out these tables with specifications from your rig?

http://img.photobucket.com/albums/v235/El_Pescador/HostHdws.jpg

http://img.photobucket.com/albums/v235/El_Pescador/HDDHdws.jpg

From what I can tell up to now, USB 2.0 host controllers for desktop PCs have eventually shaken out to either VID=8086h or VID=1033h - and no other thusfar.  So, what I am now able to do with a fair degree of certainty is counsel someone as to: (1) whether or not they will need a PCI-to-USB Host Adapter Card despite having USB 2.0 ports on their systemboard - and which model cards are compliant with Ghost 2003 operations; and (2) whether or not adopting NightOwl's Panasonic Universal USB Drivers routine will render their hitherto incompatible external enclosure kit Ghost 2003-compatible.

On the host end of the "bridge", the useful items are in properties of only those terminal "branch(es)" on the Universal Serial Bus controllers "tree" containing either the word 'Enhanced' or the abbreviation 'USB2'.  Knowing the particulars of your USB 2.0 host controller is critical, so by following the procedure below such will become evident:

(1) go to Desktop and right click on My Computer;

(2) drop down to left click on Manage;

(3) in left pane, expand System Tools;

(4) in left pane, drop down to left click on Device Manager;

(5) for both USB controllers and mass storage Devices in right pane, expand Universal Serial Bus controllers;

(6) for USB Mass Storage Devices, skip down to (7) - else for USB 2.0 controllers, focus on those lines containing either the abbreviation 'USB2' or the word 'Enhanced' then go to (7);

(7) right click on any such lines that drop down, then left click on Properties;

(8) left click on the Details tab;

(9) left click on the dropdown menu containing Device Instance Id; and

(10) left click on Hardware Ids and carefully transcribe the last two lines in the window. To be overly generous, drop down two more lines and repeat for Matching Device Id.

While the image below is set to reveal the functional USB 2.0 controller on the Macally PHR-100A external HDD enclosure kit, take note that right above the red arrow is one of my Dell Dimension 8300's three 'Enhanced' USB controllers - the Intel 80281EB is integrated into the motherboard while the other two are on PCI-to-USB host adapter cards:

http://img.photobucket.com/albums/v235/El_Pescador/PHR100AAs.jpg

If we are aware of what is both on the host end and on the device end of your USB 2.0 "bridge", then our knowledge base certainly increases.  For "grins and giggles", how about using the stock Norton/Iomega drivers that automatically come with the PC-DOS option when generating a Standard Ghost Boot Disk in the Norton Ghost Boot Wizard; then, use the stock boot disk to perform an Image Integrity Check on an existing Backup image and document any stoppages that occur - IF ANY !!!  If there are NONE, that is even more important as either way we will know the degree of compatibility your USB 2.0 host/device controller bridge enjoys with Ghost 2003 and can counsel others in the future.  

[glb]El Pescador[/glb]

Thanks a lot for the help!!!!!. ;D ;D
PS: I am braziliam and I dont speek english. :-[ :-[

People, look this.....

I'm try a boot for HD in NTFS. My files:





[config.sys]

[config.sys]

rem :The following line loads WD's universal USB-controller driver  
rem :The spaces between the filenames and the parameters are  
rem :'/e' forces USB 2.0 only, remove for USB 1.x also  
 
[menu]  
menuitem = FROMLIMPO1, Boot clean - USB1.1
menuitem = FROMLIMPO2, Boot clean - USB2.0  
menuitem = FROMGHOST1, GHOST - USB1.1
menuitem = FROMGHOST2, GHOST - USB2.0  
menuitem = FROMNTFS1, Boot clean with NTFS - USB1.1
menuitem = FROMNTFS2, Boot clean with NTFS - USB2.0  
menuitem = FROMGHOSTOKO, Boot GHOST with Guest - USB1.1  
menuitem = FROMGHOSTOK, Boot GHOST with Guest  - USB2.0  
menuitem = FROMCD, Boot CD Externo - USB1.1
menuitem = FROMCDT, Boot CD Externo - USB2.0

[FROMLIMPO1]  
DEVICE=oakcdrom.sys /d:mscd001  
DEVICE=usbaspi.sys /v
DEVICE=di1000dd.sys

[FROMLIMPO2]  
DEVICE=oakcdrom.sys /d:mscd001  
DEVICE=usbaspi.sys /e /v
DEVICE=di1000dd.sys

[FROMGHOST1]  
DEVICE=usbaspi.sys /v
DEVICE=di1000dd.sys
DEVICE=oakcdrom.sys /d:mscd001  

[FROMGHOST2]  
DEVICE=usbaspi.sys /e /v
DEVICE=di1000dd.sys  
DEVICE=oakcdrom.sys /d:mscd001  

[FROMNTFS1]  
DEVICE=usbaspi.sys /v
DEVICE=di1000dd.sys  
DEVICE=oakcdrom.sys /d:mscd001  

[FROMNTFS2]  
DEVICE=usbaspi.sys /e /v
DEVICE=di1000dd.sys  
DEVICE=oakcdrom.sys /d:mscd001  

[FROMGHOSTOKO]  
DEVICE=aspiohci.sys /int /all
DEVICE=aspiuhci.sys /int /all
DEVICE=oakcdrom.sys /d:mscd001  

[FROMGHOSTOK]  
DEVICE=ASPIEHCI.sys /int /all
DEVICE=oakcdrom.sys /d:mscd001  

[FROMCD]  
devicehigh=USBASPI.SYS /v /w
devicehigh=DI1000DD.SYS
devicehigh=USBCD.SYS /d:USBCD001

[FROMCDT]  
devicehigh=USBASPI.SYS /v /w /e
devicehigh=DI1000DD.SYS
devicehigh=USBCD.SYS /d:USBCD001

[COMMON]  
DEVICE=himem.sys
DOS=HIGH,UMB
LASTDRIVE=Z  



autoexec.bat

@echo off  
SET TZ=GHO-03:00  
path=z:\;z:\ghost;z:\pqmagic;z:\ntfs  
MOUSE.COM  
Mscdex.exe /d:mscd001 /l:z /m:16 /v
echo Loading...  

if %config% == FROMLIMPO1 goto LIMPOBOOT
if %config% == FROMLIMPO2 goto LIMPOBOOT
if %config% == FROMGHOST1 goto GHTBOOT
if %config% == FROMGHOST2 goto GHTBOOT
if %config% == FROMNTFS1 goto LIMPONT
if %config% == FROMNTFS2 goto LIMPONT
if %config% == FROMGHOSTOK goto GHTBOOTOK
if %config% == FROMGHOSTOKO goto GHTBOOTOK
if %config% == FROMCD goto BOOTCD
if %config% == FROMCDT goto BOOTCD

goto FAILED

:LIMPOBOOT
C:
goto END

:GHTBOOT
if exist z:\ghost\ghost.exe goto GHOSTOKLU

:LIMPONT
if exist z:\ntfs\ntfsdos.exe goto LIMPONTF

:GHTBOOTOK
if exist z:\ghost\ghost.exe goto GHOSTOK

:GHOSTOKLU
cd\ghost
GHOST.EXE
goto END


:LIMPONTF
cd\ntfs
NTFSDOS /L:ge /C:1024
goto END


:GHOSTOK
GUEST.EXE
cd\ghost
GHOST.EXE
goto END


:BOOTCD
MSCDEX /d:USBCD001
goto END


:FAILED
echo Unknown boot menu selection
goto END

:END



The option 3 (FROMGHOST2, GHOST - USB2.0 ) stops in the screen of the Ghost with HDs external in NTFS. Why???? Help me......

weblur  

The batch file coding looks okay--but, I'm not clear on what you are actually trying to do:


Quote:

I'm try a boot for HD in NTFS.

I don't understand what you are trying to say above.


Quote:

stops in the screen of the Ghost with HDs external in NTFS.

And, not sure what this means either.

If you could offer more detail, maybe I could understand the problem.

NightOwl, sorry sorry...... I am braziliam and i don't speak english.


When I execute the GHOST using a HD with the system of archives in NTFS, the GHOST stop and congeals, or either, it does not function.

weblur

To load Ghost, it has to be on a partition that supports DOS--floppy disk FAT, FAT16, or FAT32, or the boot sector of a  bootable CD/DVD.  But Ghost will not be *seen* on a NTFS partition.

Once Ghost is loaded in DOS, Ghost can read data from a NTFS partition and save images to a NTFS partition.

hello guys, i really need some guidance here

i am new to this usb in DOS thingy

by objective is to ghost my internal 2gb HD to a USB 2.0 external 10gb HD which i bought recently
i use Norton Ghost 2002
now i understand that i need to perform the ghosting in Dos mode
as expected, i cannot detect my usb 10gb HD since i read in NightOwl's topic that USB drivers should be loaded in DOS
therefore, i followed NightOwl's instructions (beginning of this topic).

i run in step-by-step confirmation mode in Dos to see where the problem is, the following is what shows in my screen:
------------------------------------------------------------------------
ASPI Manager for USB Mass Storage Version 2.06
(C) Copyright Panasonic Communication Co., Ltd. 2000-2003

Controller : 00-01-2 VID=8086h PID=7112h(0000h-0000h) UHCI
                 I/O=FCEOh-FCFFh

USB Device: Host [00-01-2 VID=8086h PID=7112h(0000h-0000h) UHCI]
               :    |-- VID=04CFh PID=8818h FS
               :    ^ -- 1 Device (s)

ASPI Device: ID:0  LUN:0= IC25N010 ATDA04-0  DACO

DI1000 ASPI Disk Driver Ver. 2.00
Copyright (C) 2001 Novac Co., Ltd.

AVailable ID=0
ID 0 = HD . . IC25N010ATDA04-0
#1 :  ? ? ?  Read error in Partition read.
Read error in Boot Record read.
#2 :  ? ? ?
Your program caused a divide overflow error.
If the problem persists, contact your program vendor.
------------------------------------------------------------------------
then at this point, nothing happens, it like its stopped from there
i had to reboot

what could possibly be the problem ?

uwebow

1.  Have you followed the outline *exactly*, or are you modifying the config.sys and autoexe.bat files with additional command lines--i.e. are you trying to load other DOS support programs?

2.  For trouble shooting, disconnect all other USB devices except the HDD and see if that helps.

3.  Is your USB 1.0 or 1.1 for your controller and HDD?

4.  Is the USB HDD a USB only unit--or is it an *enclosure kit* unit that the HDD can be inserted and removed?

5.  What is the details of the hardware that you are using?

NightOwl wrote on Sep 1^st, 2005 at 10:43am:

uwebow 1.  Have you followed the outline *exactly*, or are you modifying the config.sys and autoexe.bat files with additional command lines--i.e. are you trying to load other DOS support programs? 2.  For trouble shooting, disconnect all other USB devices except the HDD and see if that helps. 3.  Is your USB 1.0 or 1.1 for your controller and HDD? 4.  Is the USB HDD a USB only unit--or is it an *enclosure kit* unit that the HDD can be inserted and removed? 5.  What is the details of the hardware that you are using?

nightowl, thanks for the reply,
here are the answers to your questions:
1.  i modified the config.sys and autoexec.bat as you instructed
[contents on my floppy]
autoexec.bat
bootlog.prv
bootlog.txt
command.com
config.sys
di1000dd.sys
drvspace.bin
himem.sys
Io.sys
mouse.com
mouse.ini
msdos.sys
usbaspi.sys

[config.sys]
Device=himem.sys
Device=usbaspi.sys /v
Device=di1000dd.sys
Dos=high,umb
Lastdrive=z

[autoexec.bat]
mouse.com

2. i already tried that, did not work

3. i have no idea, i do not know how to check if my usb is 1.0 or 1.1
however, my laptop is a Compaq Presario 1680 and i bought it 1997, so i guess i have a usb 1.0?

4.  it is an enclosure kit where HDD is inserted

5.  well, i use a Compaq Presario 1680 laptop Pentium MMX, with 96mb RAM, with Win98SE installed
in my Device Manager/Universal Serial Bus Controllers it contains the ff:
-Intel 82371AB/EB PCI to USB Universal Host Controller
-USB Root Hub
what other hardware details u need to know?

i am not sure if the problem is in the partition of my external HDD, however, i can access this external hdd when im in Windows in Windows Explorer and i can transfer files in it with no problem, also when i access MS Dos prompt in Windows, i can also detect the external HDD

hope you can help. thanks

uwebowe

wrote on Sep 2^nd, 2005 at 11:39am:

nightowl, thanks for the reply, here are the answers to your questions: 1.  i modified the config.sys and autoexec.bat as you instructed [contents on my floppy] autoexec.bat bootlog.prv bootlog.txt command.com config.sys di1000dd.sys drvspace.bin himem.sys Io.sys mouse.com mouse.ini msdos.sys usbaspi.sys [config.sys] Device=himem.sys Device=usbaspi.sys /v Device=di1000dd.sys Dos=high,umb Lastdrive=z [autoexec.bat] mouse.com 2. i already tried that, did not work 3. i have no idea, i do not know how to check if my usb is 1.0 or 1.1 however, my laptop is a Compaq Presario 1680 and i bought it 1997, so i guess i have a usb 1.0? 4.  it is an enclosure kit where HDD is inserted 5.  well, i use a Compaq Presario 1680 laptop Pentium MMX, with 96mb RAM, with Win98SE installed in my Device Manager/Universal Serial Bus Controllers it contains the ff: -Intel 82371AB/EB PCI to USB Universal Host Controller -USB Root Hub what other hardware details u need to know? i am not sure if the problem is in the partition of my external HDD, however, i can access this external hdd when im in Windows in Windows Explorer and i can transfer files in it with no problem, also when i access MS Dos prompt in Windows, i can also detect the external HDD hope you can help. thanks uwebowe

sorry nightowl, i forgot to mention in #3
my enclosure kit is a USB 2.0 High Speed type
at least it says so in the casing

also, the external 10gb HDD i have is an IBM Travelstar
Model: IC25N010ATDA04-0 4200 rpm, 10GB, ATA/IDE

uwebowe

There are two newer versions of the Panasonic DOS USB drivers available that might help:

v2.15, size=39,093, dated 10/26/2003

v2.20, size=39,179, dated 11/07/2004

But, some USB enclosure type setups just don't seem to be compatible with DOS.

Try the newer drivers listed above--report back with your progress.

NightOwl wrote on Sep 5^th, 2005 at 11:48am:

uwebowe There are two newer versions of the Panasonic DOS USB drivers available that might help: v2.15, size=39,093, dated 10/26/2003 v2.20, size=39,179, dated 11/07/2004 But, some USB enclosure type setups just don't seem to be compatible with DOS. Try the newer drivers listed above--report back with your progress.

nightowl
thanks for the help

i tried both newer versions, but no luck, still having the same error messages as i described in my previous messages

i do not know if this information will help
i tried re-partitioning my external HDD and formatted it before trying out the above 2 newer Panasonic DOS USB drivers

the difference this time is, when it comes to loading the DI1000 driver, it goes all the way to #4.  The message shown are as follows:
-----------------------------------------------------------------------
DI1000 ASPI Disk Driver Ver. 2.00
Copyright (C) 2001 NOVAC Co., Ltd.

Available ID=0
ID 0=HD..IC25N010ATDA04-0
#1:  ???  Read error in partition read.
Read error in Boot record read.
#2:  ???  Read error in partition read.
Read error in Boot record read.
#3:  ???  Read error in partition read.
Read error in Boot record read.
#4:  ???  Read error in partition read.
Read error in Boot record read.
-----------------------------------------------------------------------
unlike before, after the above is shown, i goes on to load the mouse driver, lastdrive, etc.

it does not show the message: "your program caused a divide overflow error.  If the problem persists, contact your program vendor"

do you think this has something to do with my enclosure or HDD or the partitioning?

or is it the di1000dd.sys driver?  is there a newer version or other kind

uwebowe


Quote:

my enclosure kit is a USB 2.0 High Speed type

For the benefit of the forum--can you identify the brand name and model number of the USB enclosure kit--so others can be forewarned of possible compatibility issues.


Quote:

do you think this has something to do with my enclosure or HDD or the partitioning? or is it the di1000dd.sys driver?

My suspicion is that there is a compatibility issue with the controller chip set of the USB enclosure kit vs the DOS USB drivers.

If you can get access to a friend's USB HDD just long enough to boot to DOS with the Panasonic USB drivers and determine if a different USB HDD can be successfully mounted--that would tend to confirm the issue.

NightOwl wrote on Sep 7^th, 2005 at 10:37am:

uwebowe For the benefit of the forum--can you identify the brand name and model number of the USB enclosure kit--so others can be forewarned of possible compatibility issues. My suspicion is that there is a compatibility issue with the controller chip set of the USB enclosure kit vs the DOS USB drivers. If you can get access to a friend's USB HDD just long enough to boot to DOS with the Panasonic USB drivers and determine if a different USB HDD can be successfully mounted--that would tend to confirm the issue.

The brand name is That's Enclosure and the model number is USB-HD25.

did you mean a different USB enclosure?  
yeah, maybe i can try that

I am close to having my new 10gb HDD formatted and just start from scratch and install Win98SE and all other softwares which i currently have in my 2gb HDD.
I've been trying to figure out how to ghost my 2gb HDD for almost a month now.
If i just installed everthing in my new 10gb HDD, i would have been long done...hehehe....

thanks once again and i shall let you know my progress

by the way NightOwl
what would be a recommended enclosure that surely works with the Panasonic USB Dos driver?

can you advice me a brand and model
i might just opt to buy another one over the weekend

i am from manila
i've seen some brands like Billinton(?)
will this work?

uwebowe

USB ADVENTURES: 'It ain't necessarily so...'

El_Pescador talks about several different enclosure kits in many of his threads like the above--but, has never mentioned *Billinton*--so, I don't know--I personally do not have or have ever used an *enclosure kit*--only an Iomega 40 GB purpose built USB HDD.

So, my recommendation--try to find a friend's unit and test it out--if it works--buy that brand/model!  Or, buy a unit with the understanding from whom you purchase, that you can return it for refund if it is not compatible with your system and software!


Quote:

I've been trying to figure out how to ghost my 2gb HDD for almost a month now.   If i just installed everthing in my new 10gb HDD, i would have been long done...hehehe....

Yup--computers are sure *fun*--and they boost our productivity greatly!(?)

NightOwl wrote on Sep 7^th, 2005 at 10:37am:

uwebowe For the benefit of the forum--can you identify the brand name and model number of the USB enclosure kit--so others can be forewarned of possible compatibility issues. My suspicion is that there is a compatibility issue with the controller chip set of the USB enclosure kit vs the DOS USB drivers. If you can get access to a friend's USB HDD just long enough to boot to DOS with the Panasonic USB drivers and determine if a different USB HDD can be successfully mounted--that would tend to confirm the issue.

hi nightowl
NO LUCK!  it didnt work too
i borrowed a different enclosure from a friend and tried it
intalled my 10gb HDD into my friends enclosure, tried 3 versions of the panasonic dos usb drivers
it hangs in the portion where DI1000 driver is being loaded

my friends enclosure is a generic type and i have no idea of its brand and model.  although it says in the housing that it is USB 2.0. (different from mine which is High Speed USB2.0 - btw, is there a diff?)

i guess we eliminated the compatibility issue on the enclosure, unless im really just unlucky

do you think it has something to do with the USB version
i mean, my laptop hardware must be a USB 1 or 1.1 and my enclosures are USB 2.0
do you think connecting it thru a USB 2.0 root hub will make a diff?

also, what does the DI1000.sys driver suppose to be?  loading the hard drive? (sorry for my ignorance)

im am 2 steps away from reinstalling windows to my new 10gb
i will just try 2 more other options:
1.  use a USB 2.0 root hub (i will need it anyway, guess this is the time to buy it)
2.  use another enclosure (will probably look or buy a diff one)

Unless you have some more ideas in mind that can solve this
thanks a  lot for your help and effort
appreciate it!

uwebowe


Quote:

do you think it has something to do with the USB version

In my original posting, I used this line in *config.sys*:

Device=usbaspi.sys /e /v

The */e* switch forces USB 2.0.  But in your *config.sys*, you have removed it, which is the correct thing to do because your system board is USB 1.x and not 2.0.


Quote:

also, what does the DI1000.sys driver suppose to be?  loading the hard drive?

As I understand it--*usbaspi.sys* mounts the USB HDD in DOS so DOS *sees* it, and then *di1000.sys* assigns the drive letter to the HDD.


Quote:

although it says in the housing that it is USB 2.0. (different from mine which is High Speed USB2.0 - btw, is there a diff?)

I think it's mostly a marketing thing--*High Speed* is a term added when USB 2.0 came out to distingish it from USB 1.x.


Quote:

i guess we eliminated the compatibility issue on the enclosure, unless im really just unlucky

Well, hard to say--the compatibility could be your controller chip on you laptop's motherboard, rather than the one in the enclosure kits--or you may in fact just be *unlucky* so far!

What you would need to do, is try the Panasonic DOS drivers on another computer with each of the enclosure kits to see if the drivers work on that system--if the enclosures work on that other system, then the problem is pointing at the USB controller on your laptop!

Basically, until you can demonstrate that the components work on one system, and then show that it doesn't on another--you can't be sure if it's *unlucky* or truely *incompatible* and will never work!


Quote:

do you think connecting it thru a USB 2.0 root hub will make a diff?

A hub is not likely to solve the problem you are currently having!

thanks nightowl

why havent i tried testing the enclosures on other systems, how stupid of me
i guess i was so concentrated in wanting to ghost my hdd that i didnt consider that

okay then, let me try that

but let me point out that my enclosures+HDD works fine when im in Windows, meaning when i access it from Windows explorer, it works fine
also when i access it thru MS Dos prompt
i dont know if this matters, but just wanted to let you know

i read somewhere that there is a switch that you can put in the di1000dd.sys driver, it goes something like this:

Device=di1000dd.sys /Hx /Hx

i think its about accessing the Master sector and Boot sector of the HDD, something like that

are you familiar with this?

i shall let you know results when i test my enclosure+HDD on another system

thanks

Hello,

I have the same probleme as Bjorn. I can read image from ghost without any problems but when I want to create an image of C: 4GB it stop responding at 70%.

PLease help me. THanks. Luxembourg.

[config.sys]
device=usbaspi.sys /e /v
device=di1000dd.sys
device=oakcdrom.sys /d:nightowl
lastdrive=z

[autoexec.bat]
path=a:\;x:\
mouse.com
mscdex.exe /d:nightowl /l:x /m:16 /v
ghost.exe

****Files****
AUTOEXEC.BAT
COMMAND.COM
CONFIG.SYS
di1000dd.sys
GHOST.EXE
IO.SYS
mouse.com
MSCDEX.EXE
MSDOS.SYS
OAKCDROM.SYS
Usbaspi.sys

PS.  I created the boot cd with Roxio using the 2.88 emulation.

Hello guys,

I finally manages the problem with a little modification.

[config.sys]
device=himem.sys  :-* :-*
device=usbaspi.sys /e /v
device=di1000dd.sys
device=oakcdrom.sys /d:nightowl
dos=high,umb :-* :-*
lastdrive=z

[autoexec.bat]
path=a:\;x:\
mouse.com
mscdex.exe /d:nightowl /l:x /m:16 /v
ghost.exe

****Files****
AUTOEXEC.BAT
COMMAND.COM
CONFIG.SYS
di1000dd.sys
GHOST.EXE
HIMEM.SYS :-* :-*            
IO.SYS
mouse.com
MSCDEX.EXE
MSDOS.SYS
OAKCDROM.SYS
Usbaspi.sys

Created with Roxio Creator Classic ( 2.88 emulation) Thanks for this guide.

uwebowe


Quote:

i read somewhere that there is a switch that you can put in the di1000dd.sys driver, it goes something like this: Device=di1000dd.sys /Hx /Hx i think its about accessing the Master sector and Boot sector of the HDD, something like that are you familiar with this?

Actually, no--I've not seen anything like the above.  Here is a resource I've used:

Subject: USB driver for DOS = USBASPI.SYS



Quote:

DI1000DD.SYS ASPI Disk Driver v2.00 from Novac Co., Ltd device=[{path}]DI1000DD.SYS [/hN] [/dL] If USBASPI.SYS detects multiple mass storage devices on multiple host adapters, use /hN Host, to specify which host adapter to map drive letter(s), where N would be the 3rd number set reported for the USB controller in USBASPI.SYS with the /v switch. To specify the starting drive letter for detected mass storage devices, use /dL Drive_letter, where L is the first assigned letter for this host adapter Example of use: If you want specify the "L" drive letter for a storage device, try: device[high]=[{path}]di1000dd.sys /dL

The above resource also outlines other drivers that are similar--you might try those.

Also, zoro's post is informative--some *systems* do not work well without the use of *himem.sys* for memory management--wouldn't hurt to try that in your *config.sys* file as he outlines.

zoro

Thanks for the post and the additional feedback.

I've seen reference to needing to use *himem.sys* on *certain* systems for proper memory management--but I always thought it would cause boot failure, and not failure  at 70 % into the Ghosting process.

Because I've never had that memory problem, I've never had the chance to *trouble shoot* it.  Your solution is very informative.  I will incorporate the information into my Guide, and based on other posts in the past, it is likely the answer to some others' problems that we have tried to trouble shoot previously--some unsuccessfully--so, your contribution is very helpful.

More than 15,000 pageviews, and over 100 replies. Wow.

NightOwl wrote on Sep 11^th, 2005 at 11:23am:

uwebowe Actually, no--I've not seen anything like the above.  Here is a resource I've used: Subject: USB driver for DOS = USBASPI.SYS The above resource also outlines other drivers that are similar--you might try those. Also, zoro's post is informative--some *systems* do not work well without the use of *himem.sys* for memory management--wouldn't hurt to try that in your *config.sys* file as he outlines.

nightowl,
here is a link of where i read about switches on DI1000dd.sys
http://www.computing.net/dos/wwwboard/forum/15085.html

about zoro's suggestion, did you mean that i try not loading the himem.sys?

uwebowe


Quote:

about zoro's suggestion, did you mean that i try not loading the himem.sys?

My *bad*--I thought you were not loading it, and was suggesting that you try it!

Many thanks for such a great post.  It has taken me days (on and off) to get through all the discussions and links.

I am running a generic 2.0 USB enclosure on a WD 250Gb harddrive.  The system is a Asus P4GE-MX running a 2.4 GHz Celeron.  I tried to figure out the manufacture of the USB control on the MB and was not able to do so.  I also have a Ali 2.0 card in the system.  

I have seen some discussion about transfer rates and I still feel that the rates are unacceptable.  

The system didn't really need any special drivers to be able to boot from and/or talk to the USB External drive.  However, when I first tested Ghost under this configuration, Ghost indicated that it was averaging 60 MB/min or 1MB/sec.  When directly connected to the IDE bus, 1000 MB/Min transfer rates were seen, so I at least assume that is the best I would ever do due to some sort of limitation of the bus.

After reading this post, I was confident I had to be able to do better.  I tried the Ghost Iomega boot disk configurations with IBMDOS and MSDOS and could never get the system to see the External USB hardrive.  I also tried DUSE and had the same issues.

Tonight, I tried the Panasonic driver with the *motto haru* driver.  All the drives were recognized and assigned new drive letters.  The "normal" system recognization of the External USB Harddrive was also still seen and assigned a drive letter, by these drives were not usable.

In testing Ghost 2003 with this new configuration, I was able to get a sustained transfer rate of up to 170 MB/min.  This is still substantially slower than the maximum transfer rate possible with USB 2.0 of 3600 MB/min and I still remain confused as to what I can do to speed things up.  Obviously, the Panasonic driver is better than the built-in BIOS recognization of the USB device.

It would be appreciated if any recommendations could be made as to how to speed up the transfer rate to the External USB device.  Also, forgot to mention... whether connected to the USB bus on the MB or the Ali card, the results are the same.

I am currently reviewing this thread in hopes to use it for a USB 2.0 Maxtor One Touch II 300 Gig...  

Thank you greatly to those who have contributed; it does not go without much gratitude.

wrote on Sep 9^th, 2005 at 12:40pm:

thanks nightowl why havent i tried testing the enclosures on other systems, how stupid of me i guess i was so concentrated in wanting to ghost my hdd that i didnt consider that okay then, let me try that but let me point out that my enclosures+HDD works fine when im in Windows, meaning when i access it from Windows explorer, it works fine also when i access it thru MS Dos prompt i dont know if this matters, but just wanted to let you know i read somewhere that there is a switch that you can put in the di1000dd.sys driver, it goes something like this: Device=di1000dd.sys /Hx /Hx i think its about accessing the Master sector and Boot sector of the HDD, something like that are you familiar with this? i shall let you know results when i test my enclosure+HDD on another system thanks

hi nightowl
i have tested the enclosures with the Panasonic USB drivers on a different system/desktop, and guess what......

it didnt work too!

oh well....

uwebowe

I'm thinking that you have tried two *enclosure* type USB HDD setups that are not compatible with the DOS drivers.

Next step is to try either a purpose built USB HDD and/or other enclosure USB kit that is known to work successfully on a system (any system!) to see if it works on your laptop.  

You need to try a known compatible USB HDD setup to confirm where the problem lies at this point.

It's really frustrating when components don't seem to have the compatibility that you would expect!

The results are in but before I share a success story let me say to all the Moderators here.  Among my searching this is the only forum that has provided such acurrate, compiled, and well-illustrated information regarding this topic.  This should be made into a PDF and posted for D/L ...

I successfully identified in dos TWIN (2 identical) Maxtor One Touch II 300GB External USB 2.0 HDDs  using the USBASPI.SYS  v2.20 controller and the DI1000DD.SYS driver.  

Both HDDs are partitioned in half as NTFS.  (286,188MB total or 143,000something each partition)

Note: these drives have ONLY 1 USB port each.  No Firewire or Cat 5 or 6 link

This worked on two different setups:

# 1. Compaq Presario Notebook, P4 2.0Ghz, 752meg RAM, 2 USB ports out the back.

(this next one will make you cry; I do...)

# 2. HP Pavilion Desktop, P3 900Mhz ("overclocked" to 1.0 Ghz), 256meg RAM, using a BELKIN PCI USB card.

IN GHOST

setup 1
Using the # 1. setup I created an image of Disk 1, partion 2 ( 1:2 ) onto Disk 2, partition 2 ( 2:2 ).  I used FAST compression...

The total time was 5hrs 20mins.  The average speed was 400 MB/minute or 6.66 MB/second...  I read previously someone got around 550MB/minute and liked the prospects but I shouldn't complain.  The ability to even identify these drives with dos is amazing...

setup 2
Using # 2 setup I am currently checking the image integrity at 600 MB/minute or 10 MB/second.  I wanted to use the Desktop just to test the PCI card.

I am still curious, would the drivers that come with drives on cd work under dos?  Doubtfully, but still asking...

This is the end of a 25-hour road of reading forum after forum.  Thankyou to all who have contributed and will contribute.

A few more questions:

Having two external HDDs of such capactity (4 partitions all roughly 143 GB) there is a lot freedom for me explore more efficeint storage practices.  I use HDD 1 as a regular/everyday HDD connected to my Desktop in which I keep my music, photos, and the such.  I use HDD 2 as a backup of HDD 1, my desktop, and my laptop.

1. Is it "better" to have HDD 1 formatted as NTFS vs. others?

2. Can I gain any performance during a ghost backup or file integrity if I format HDD 2 as something other than NTFS?

3. In accessing HDD 1 daily, is it possible to keep these files encrypted without a lot of time consuming processing?

presbuteros

Good to hear of your successes!


Quote:

I am still curious, would the drivers that come with drives on cd work under dos?  Doubtfully, but still asking...

Usually, you have to find out by trying!

1.  Again, doing time trials will answer this question--I found the NTFS was very slightly faster than FAT32 on my USB HDD.

2.  Same as #1  ;) !

3.  Someone else will have to help you on that one--I don't use encryption.

Thanks NightOwl...

I do not know much about drivers and did not know if they were sometimes restricted to a specific os environment (ie: a driver only usable with a particular version of windows)

I will give that a go too.  Again if there is success I will share...

Presbuteros, concerning your question “Is it possible to keep these files encrypted without a lot of time consuming processing?”, the answer is:  it depends upon the encryption tool being used (and there are many options available).  Based upon my own experience using SecretAgent (http://www.infoseccorp.com/products/secretagent/sa57win.htm), the time required to encrypt/decrypt most files (< 10MB) is negligible.

Hi all,

First time posting, just wanted to thank all the moderators for the great work & info.

I have recently used nightOwl's Panasonic drivers on my wife's Dell WinXP SP2 laptop to do a Disk Image. I was able to create the image, and successfully verified the image (for specs and transfer speed, see below). However, when I booted it up, my wife noticed that the wireless network settings that were previously saved, are now gone. I verified this, as I had to re-enter my wifi network's WEP key to reconnect to my home network.

In addition, she also noticed that when she mouses over the wifi mgr icon in the system tray, it says "Windows is managing this device" and the icon is white instead of the usual green.

Today (3 days after the disk image) she called me from school and said she got a blue screen. Rebooted and it looked to be ok. I'll have to wait til she gets home to check it.

When I created the Disk Image, I saw that there was a Dell partition that I did not know existed. I wonder if this is where they store the config data and somehow this was not copied over entirely?

I realize that this would be strange for a computer to be modified b/c of CREATING an image, not RESTORING an image, but I thought I would check in case. It's important for the laptop to stay up as we're in the thick of 1st year law school (which is why I created the ghost image in the first place! :-) ) so I didn't want to try anything else without doing some research first.

I tried searching for answers to the above, but got nowhere, so was wondering if any of the moderators/posters with their wealth of knowledge might have heard something like this. Thanks for any assistance!

Specs:

Dell Inspiron 600m Laptop w/ WinXP SP2
40 GB HD, ~10 GB used

External USB HD: USB 2.0 80GB Maxtor Personal Storage 3100
Transfer speed: ~333 MB/min

how would you go about making that boot disk on xp pro.

ghost 8.0 wont see my usb dvd burner and i think this will work but i cant get a boot disk working? pls help
??? ??? ??? ??? ???

pbnj,

did you retore an image or simply create one? creating an image shouldn't affect anything with system configuration.

http://www.goodells.net/dellutility/

pbnj130


Quote:

However, when I booted it up, my wife noticed that the wireless network settings that were previously saved, are now gone.

I have to second *Raul's* comment--creating an image should not have had any effect on any settings.  

What is actually saved to an image by Ghost may not be an *exact* copy of what's on the HDD--Ghost leaves out certain files such as the actual *pagefile*--just has a *placeholder* in the directory tree.  You can, in Ghost 2003, use a switch to create an exact copy called a *sector-by-sector* image--but that image will then be the size of the HDD you are imaging--and not just an image of the data portion on the HDD.

But, I've never seen any reference to the settings of the system being altered by an image creation process.


Quote:

When I created the Disk Image, I saw that there was a Dell partition that I did not know existed. I wonder if this is where they store the config data and somehow this was not copied over entirely?

The *hidden* partition on the Dell is usually the *restore* partition that allows you to run a restore utility and the *original* factory fresh OS--all the programs and settings--that came from the factory can be restored--but, you loose all the data that you have created since you started using the system.

I have heard that Dell systems often have two hidden partition--one is the restore partition, and the other is a *utility* partition.  But, I do not believe any system settings for the current *in use* OS are saved to those partitions.

lost soul

Your question lacks details--what have you tried so far and where are you having a problem?

You might want to consider starting a new thread topic if it involves issues not directly related to this thread about the Panasonic DOS USB drivers.

You can find reference to using a USB optical drive in one of the original references in this thread:

Yes, there are USB drivers for DOS...

One way to avoid USB issues in DOS is to avoid the use of DOS.  Some readers of this thread may benefit by considering the use of the Windows-based version of Ghost 2003 (GHOST32.EXE) operating either from within Windows or from within BartPE.

See the thread “Ghost 10.0:  Restore Ghost 2003 Images” (http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1127153647) for additional details.

Raul and NightOwl,

I created a disk image, and did not do a restore. I also thought it was weird that the image creation process would modify something. I have since called Dell Support and used the Dell System Restore utility to roll back 1 week. I'm hoping that will stop the Blue Screens. I will definitely read the info you have provided though, as it is good to know exactly what Dell puts into these things. Thank you for the info.

I've decided it's probably best not to try anything else on the laptop until I can get a WinXP machine of my own to play with. That way I can have a staging machine where I can try stuff out.

BTW, I made a correction to my previous post. It said "Windows is managing this device", not "This device is not installed".

Thanks

Pleonasm

Minor clarification--*Ghost32.exe* is the Corporate version of Ghost--Ghost 8.x--cousin to Ghost 2003.  One will only have that option if they have the Corporate version of Ghost.

*RESTOREGHOST.EXE* comes with Ghost 9.x (and presumably Ghost 10.x when released)--but you have to have Ghost 9.x or 10.x if you want to use that option--it is found on the Ghost 9.x *Recovery Disc*.  It is a *crippled* version of Ghost 8.x that can only be used to restore an image, but not create a backup image.

NightOwl wrote on Sep 16^th, 2005 at 10:44am:

uwebowe I'm thinking that you have tried two *enclosure* type USB HDD setups that are not compatible with the DOS drivers. Next step is to try either a purpose built USB HDD and/or other enclosure USB kit that is known to work successfully on a system (any system!) to see if it works on your laptop.   You need to try a known compatible USB HDD setup to confirm where the problem lies at this point. It's really frustrating when components don't seem to have the compatibility that you would expect!

yes NightOwl, im still at this....
well, i havent really made some efforts to solve my problem since my last post.....a bit preoccupied

anyway, i just thought of an idea and please help if it is advisable

now, from what i read, it is not advisable to ghost your internal hard drive to an external hd while you are at windows, right?

then, what if i pull out my internal hard drive (which i want to ghost), load it to another PC thru my USB enclosure
then run ghost while at Windows and ghost this external HD to the internal HD of the PC (probably the ghosted HD will be located on a separate directory?)
then, afterwhich, i disconnect the ghosted external USB HD, connect a new HD, then ghost back the previously ghosted HD to the new HD...

did you get what I mean?

NightOwl, concerning your Reply #123, you are correct:  it is necessary to have a "corporate Ghost 2003" (i.e., "Symantec Ghost Solution Suite") license to obtain GHOST32.EXE and thereby run "Ghost 2003" in Windows.  It may be purchased from the "Enterprise Store" on the Symantec website for US$39.20/license - but, unfortunately, Symantec does not appear to sell these licenses in quantities smaller than 10.

I also noticed that Symantec no longer even displays "corporate Ghost 2003" as a product option - see:
http://enterprisesecurity.symantec.com/content/productlink.cfm.  Looks like "corporate Ghost 2003" is disappearing fast, so those who are interested may want to buy soon . . . .

Pleonasm

Terminology is *everything* when it comes to computers  ;) -- and I think you are mixing *apples and oranges*!

I do not believe there is a *corporate Ghost 2003*.  Corporate Ghost is Ghost 8.xx, and is a close *cousin* of Ghost 2003.

The interface of the two versions appear very similar, but the capabilities vary.

So you have to have Corporate Ghost 8.xx in order to get *Ghost32.exe* that will run Ghost 8.xx in Windows.  Ghost 8.xx can create and restore Ghost images while booted to Windows--but probably can only do that to non-OS partitions--but, I'm guessing on that one.

Ghost 2003 has a Windows interface that can be installed and run in Windows--but it can not perform any Ghost image creation or restoration unless it shuts down Windows and re-boots to DOS.

NightOwl, my intent was to keep the verbiage user-friendly  :) and to help ‘translate’ between the retail and corporate environments, but perhaps I did not succeed and inadvertently created confusion.  By "corporate Ghost 2003" (the use of quotes was intentional) I do indeed mean Ghost 8 which is sold under the label Symantec Ghost Solution Suite.  I understand that Ghost 8 is not identical to Ghost 2003, but for all practical purposes the two can be considered “essentially equivalent” in terms of major functionality.  (As you noted, the former does contain the GHOST32.EXE executable that runs in Windows - thereby yielding a Windows-based version of Ghost 2003, roughly speaking.)

In contrast, the Windows interface to Ghost 2003 is just that – a Windows-based mechanism to ease the burden of “dropping to DOS” to run Ghost 2003.  Whether launched via Windows or directly from DOS, the identical product - Ghost 2003 – runs in DOS.  Strictly speaking, the Windows interface to Ghost 2003 is not an interactive Windows front-end to Ghost 2003 per se – it is, rather, a Windows interface to a mechanism to launch Ghost 2003 in DOS.  That’s a big difference, but one that should be commonly understood.

The Hidden Partition on your dell is used to restore a Factory Install Image in case we ever had to put the Computer back to defaults during repair.

The program us dell techs used was called ZZTOP.exe you will find it in the CDENAB Boot Disk download off of Dells FTP server in the Utilities Directory at ftp://ftp.dell.com


Will Someone post a download link to their created Boot Cd or Floppy...thnx

Ex Dell Tech

Now Area 51 I.T. Admin/Staff

http://support.studio505.net
http://area51portal.com

wrote on Sep 27^th, 2005 at 2:55pm:

Hi all, First time posting, just wanted to thank all the moderators for the great work & info. I have recently used nightOwl's Panasonic drivers on my wife's Dell WinXP SP2 laptop to do a Disk Image. I was able to create the image, and successfully verified the image (for specs and transfer speed, see below). However, when I booted it up, my wife noticed that the wireless network settings that were previously saved, are now gone. I verified this, as I had to re-enter my wifi network's WEP key to reconnect to my home network. In addition, she also noticed that when she mouses over the wifi mgr icon in the system tray, it says "Windows is managing this device" and the icon is white instead of the usual green. Today (3 days after the disk image) she called me from school and said she got a blue screen. Rebooted and it looked to be ok. I'll have to wait til she gets home to check it. When I created the Disk Image, I saw that there was a Dell partition that I did not know existed. I wonder if this is where they store the config data and somehow this was not copied over entirely? I realize that this would be strange for a computer to be modified b/c of CREATING an image, not RESTORING an image, but I thought I would check in case. It's important for the laptop to stay up as we're in the thick of 1st year law school (which is why I created the ghost image in the first place! :-) ) so I didn't want to try anything else without doing some research first. I tried searching for answers to the above, but got nowhere, so was wondering if any of the moderators/posters with their wealth of knowledge might have heard something like this. Thanks for any assistance! Specs: Dell Inspiron 600m Laptop w/ WinXP SP2 40 GB HD, ~10 GB used External USB HD: USB 2.0 80GB Maxtor Personal Storage 3100 Transfer speed: ~333 MB/min

Do any USB 2.0 drivers for DOS & Ghost 2003 allow you to access more than one partition ( multiple partitions ) on the USB 2.0 external hard disk Drive?  If yes, could you please post the sections of CONFIG.SYS and AUTOEXEC.BAT that apply.

GhostFan

The DOS USB drivers should allow you to access all DOS based partitions on a USB HDD--FAT16, FAT32--but DOS can not *see* NTFS partitions on any HDD.

There are DOS *tools* for reading NTFS partitions--but those are not the USB drivers.  I have not used these, but I assume they must also *see* those NTFS partitions--and would *see* them on a USB HDD that is accessed using the DOS USB HDD drivers.

I tried the Iomega driver for USB 2.0 that comes with Ghost 2003 and I was only able to see the first of my two fat32 partitions on the USB 2.0 external hard disk drive.  I may not have implemented it correctly in config.sys and autoexec.bat for 2 partitions.  I just used the standard format that is written when you create the floppies for USB 2.0 support.  aspiehci.sys /int /all in config.sys and guest.exe in autoexec.bat

In a strange twist, when I changed partition number one to be ntfs, Ghost 2003 could see the first NTFS partition with no drive letter and assigned a drive letter to the second partition which was fat32.

Am I missing something in config.sys and autoexec.bat or should I just abandon the Iomega driver and try the Panasonic driver that is talked about in this thread?

GhostFan


Quote:

I tried the Iomega driver for USB 2.0 that comes with Ghost 2003 and I was only able to see the first of my two fat32 partitions on the USB 2.0 external hard disk drive.

I have to suspect there is an issue with how the USB HDD was partitioned--or a compatibilty issue--that is causing a problem with DOS *seeing* the second partition.

I've not had problems *seeing* all the USB HDD partitions using Ghost's USB DOS drivers with my USB HDD, but I suspect there are compatibility issues with some hardware--especially enclosure kit type USB units.  I do remember using another DOS USB driver called *Duse* where only the first partition would be assigned a drive letter in DOS.  That's why I moved on to the *Panasonic DOS USB drivers*.


Quote:

when I changed partition number one to be ntfs, Ghost 2003 could see the first NTFS partition with no drive letter and assigned a drive letter to the second partition which was fat32

Ghost 2003 will *see* and can access NTFS partitions from within Ghost's interface, but NTFS partitions will be assigned a *drive # : partition #*--so something like 2:1, 2:2 or 3:1, 3:2, etc., depending on how many HDD's are present on the system.

Again, the fact that the 2nd partition now got a drive letter in DOS, suggests that DOS is not really *seeing* the HDD partition structure correctly--an incompatibility issue most likely between software and hardware.


Quote:

Am I missing something in config.sys and autoexec.bat or should I just abandon the Iomega driver and try the Panasonic driver that is talked about in this thread?

I doubt you are missing anything--try something else!

Thank you for your replies NightOwl.  I appreciate having someone out there in the cyberworld to help me.

My USB 2.0 External Drive is a Western Digital 40GB 8MB Cache 7200 RPM drive in an enclosure that uses the Cypress AT2 bridge circuit.

The formatting was done by Windows 2000 SP4 Disk Management.  2 nearly equal size partitions were created.

The NTFS partition was assigned 2:1 as you suspected.

Guest.exe does seem to assign a single letter to the drive despite there being two fat32 partitions.

I guess I'll try the Panasonic driver talked about in this thread.

Lest anyone think I'm making problems for myself, I will say that having more than one partition saved me from losing important data when I accidently clobbered one of the partitions by choosing the wrong drive.  My data was on the other partition and was still safe after my goof.  Never put all the eggs in one basket, unless you like em scrambled. :-)

Thank you.

GhostFan


Quote:

I will say that having more than one partition saved me from losing important data

That's how most of us have *learned* that backing up is a good thing!!!!

My 40 GB USB HDD has three partitions.


Quote:

Never put all the eggs in one basket, unless you like em scrambled.

I like that one  ;) !

Have you guys noticed that the forum software somehow "lost" 10 or 15 thousand page-views from this thread?

Back on reply #105, I remarked that the thread had over 15,000 page-views:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1095438251;start=105#105

.. yet now, it says "only" 4700.

I have seen this happen on other threads, too.

But this thread, over on the "Lethal" Rad board, says ~43K .. so I'm not sure what the problem is.

Long as we don't lose actually posts, I guess it's not a major problem. But I *am* curious to know exactly how many page-views this thread has had.

So I made a boot CD with the guide and substituting these usb drivers.  But when I boot into my machine with USB keyboard and mouse, I can't do anything (because they don't work).  Any ideas?
It works fine from a computer with PS/2 keyboard and mouse.

Sorry if this is covered in the norton ghost guide or somewhere else.

Hi,

I am having trouble getting the Boot disk to work properly.  Let me explain the situation and hardware/software.

Hardware:  Dell laptop, USB floppy,  USB Western Digital      Passport HD.  Note: Laptop C: is NTFS, and WD is FAT32.

Software :  Ghost 2003, Dos Boot disk from Ghost 2003, Dos Boot disk by Nightowl

Objective :  Boot from floppy,  and Ghost Laptop HD                  partition to USB HD.

Yes, I am aware that I can run Ghost from Win - however, the current laptop partition setup (i.e.,  1- Dell Utility, 2-C:, 3: Dell estore) results in "No space in MBR" for Virtual partition.  At this time, don't wish to delete the Dell partitions.  Also, I know you won't be able to see the NTFS partitions in DOS unless you are using the NTFSDOS driver - however, the NTFS partitions should be visible in Ghost.

I will list what I have attempted and the resulting problems:

a.)  Generate Boot disk with USB support from Ghost.  USB HD found, but when I run Ghost, the laptop HD is not visible,  i.e., not found.  I don't know the reason.
b.)  Modify boot disk to not load usb drivers.  As expected, USB  HD not found,  BUT now laptop HD seen in Ghost.  Perhaps USB driver is causing a conflict.  And according to posts on  this site, the Ghost USB driver has limitations.
c.)  Tried the Boot disk (i.e., USBaspi.sys, DI1000dd.sys) procedure given by Nightowl.  The driver is loaded but the WD is not found and the process never proceeds any further.  Note, I used an MS-DOS disk generated by Win98 for the system files.
d.)   Based on further posts on the site, thought that I might be  using an old USBaspi.sys that does not recognized the WD USB HD.  So I changed it for ver 2.2 - the driver loads up - initializes controllers, and the begins scanning for USB devices and again hangs.
     
I am somewhat at a loss on how to solve the problem.  Does anyone have any ideas/suggestions.  I would appreciate it if someone could point me in the right direction.

Thanks.

Hi,

Just wanted to let you know that I got the DOS boot disk to work.    I used the same Dos boot disk setup suggested by Nightowl but edited the config.sys and stopped the usb driver from loading up.  After this, I was able to see both HDs (Laptop & USB HD) in Ghost.  

I don't know why this is so or what caused the problems I experienced (see post above).  If you have any questions or need any further info., just let me know.

Thanks

mpcp.

Will_Rickards wrote on Nov 29^th, 2005 at 12:36pm:

So I made a boot CD with the guide and substituting these usb drivers.  But when I boot into my machine with USB keyboard and mouse, I can't do anything (because they don't work).  Any ideas? It works fine from a computer with PS/2 keyboard and mouse. Sorry if this is covered in the norton ghost guide or somewhere else.

Upgraded my bios and found that now the usb keyboard and mouse options had legacy next to them.  They were enabled anyway so scratch the bios as the problem.
Then I booted with the CD and pushed F8 to do step by step.
If I don't load the panasonic usb drivers, the keyboard and mouse work.
If I do, they don't. So it is definitely the driver. It might be an option like only use OHCI or EHCI or something.  

Also another interesting thing.
While I was able to format this 160GB drive as FAT32 in an external enclosure with mkdosfs for windows, and was able to write to it with ghost, and verified the images with ghost. A day later all I got was gibberish when doing a dir command and it said the FAT table was corrupt. All with no writing to the drive being done?!? So my backups are well gone. Not sure whether it is the greater than 137GB thing or the enclosure chipset or what.

It works fine formatted NTFS over firewire connected to my main machine so back it goes. Which means now I don't need the panasonic drivers, I need the firewire device drivers. Anybody want to create a ghost 2003 boot floppy disk with those and tell me what files/commands are needed in config .sys/autoexec.bat?

I'm out of CD-Rs so I won't be able to test a new boot cd.
I'm thinking about trying to make my USB flash drive bootable and trying that as it is rewritable.

Other Forum Post

mpcp27


Quote:

Just wanted to let you know that I got the DOS boot disk to work.    I used the same Dos boot disk setup suggested by Nightowl but edited the config.sys and stopped the usb driver from loading up.  After this, I was able to see both HDs (Laptop & USB HD) in Ghost.

This behavior makes me think that your laptop may have *built-in* or *native* support for USB--and loading the additional USB DOS drivers was creating a driver conflict of the two drivers.

You say you have a USB floppy drive--are you able to boot to DOS with other DOS floppys without first loading USB drivers--then the laptop BIOS supports USB in DOS without additional drivers--probably can control that (enable or disable) in the BIOS settings if you wanted to use other USB DOS drivers instead.

Will_Rickards

This may solve your USB keyboard/mouse problem:

USB driver for DOS = USBASPI.SYS

Quoting regarding various switches for the Panasonic driver:


Quote:

/norst NO ReSeT, to prevent the driver from resetting USB peripherals which have been initialized by BIOS (USB legacy support) such as keyboards and mice.

If your system did not support your keyboard and mouse in DOS (legacy support), Norton's Ghost Boot Wizard for the *Std Ghost Boot Disk*, on the first option screen lets one select *Peer-to-Peer>>USB Support*--others have reported that this driver will allow access to USB mouse and keyboard in DOS.

The driver names are *ohci.exe* and *uhci.exe* and are found in the *C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common* sub-directory on my system.

In the *Boot Wizard*, you can choose to load both, or just one or the other, by using the *Advanced...* button.

If using these drivers outside of the boot wizard, you load them in *config.sys* with the following syntax:

device=ohci.exe
device=uhci.exe

and the files would have to be added to the root directory of your boot disk.

But, selecting this option in the Boot Wizard *greys out the option of using *External Storage Options* where you get your USB support for the external HDD--so apparently the Ghost USB DOS driver for external HDD will not function.

But, you can load the Panasonic USB DOS driver or *mass storage devices--which is different from USB mouse or keyboard functions--after the above USB driver using the */norst* switch and you may now have both USB mouse/keyboard support plus the USB external HDD support.  (I say *may*--because I don't have USB mice or keyboards to test this out--and various systems may respond differently!)


Quote:

I need the firewire device drivers. Anybody want to create a ghost 2003 boot floppy disk with those and tell me what files/commands are needed in config .sys/autoexec.bat?

See here (reply # 8 ):

Adding USB to Ghost Boot CD

Report back with the results of your efforts--it would be informative if you tried the Ghost *Peer-to-Peer* driver and the Panasonic driver with the */norst* switch--if this combination allows for USB mouse and keyboard functionally plus external USB HDD access! (You would have to *disable* legacey USB support in the BIOS to try this.)

But, knowing if the */norst* switch works if the BIOS is giving legacy USB support to the USB mouse and keyboard would also be of interest.

Many, many thx NightOwl.  I work at a NFP that still uses some Win 98s.  Had used Ghost 2K3 successfully on WinXPs, not on 98s.  Had a major fit with it until I found this thread.  Here's my blog post.

I have Ghost app on disk by itself but Ghost doesn't start automatically & when type "ghost" at A: prompt get "bad file name or command". I have the panasonic drivers floppies (I think correctly setup) but they used to automatically check for drives & assign letters, etc & DID recognize my WD ext. HDD but now it just gets me to A: prompt & "duh" - I don't know where to go from there.....

I'm not terribly knowledgable on Ghost or DOS so are there other commands to run Ghost & to utilize the drivers?

I used these floppies a few times months ago & they worked(that is, automatically checked for drives & assigned letters, etc & DID recognize my WD ext. HDD) so not sure if I messed them up somehow or what & forgot in what order to use them.....Win98 boot, then get Ghost going, THEN put drivers disk in??

(BTW they were generously supplied to me by El_Pescador.)

piikea wrote on Jan 18^th, 2006 at 12:00am:

I have Ghost app on disk by itself but Ghost doesn't start automatically & when type "ghost" at A: prompt get "bad file name or command".

Here's a muy basic question, but you did say you were unfamiliar with DOS. ;)

Using Windows Explorer, see if Ghost.exe is on the root or if it's in some subdirectory on your floppy.  Next, use notepad to open the autoexec.bat file to check the path, i.e. a:\ghostfolder\ghost.exe it's using to crank it up.  If you make any changes to it, be sure notepad saves the autoexec to .bat, not .txt extension.

Compute in Peace!!!

tbb

Thanks........I took ghost.exe out of the folder called ghost & it seems to be starting ghost ok now (though originally had no mouse functioning --- added mouse.com, etc. & I think THAT floppy is working correctly.

As to problem #2 - w/o the Panasonic USB Drivers disk working, ghost doesn't recognize the ext. HDD where images would be/are saved to or recovered from.

I HAVE used it successfully before, it "did it's thing" automatically....said "scanning for usb drives" (or drivers?), etc & then ghost would show the ext HDD as the last drive. Can't figure out how or what command is missing or needed for it to load/scan usb devices as it should.....
Any ideas???

What's bugging me is that you said you took the ghost.exe out of the ghost folder, (and put it on the floppy root ?!?) rather than changing the autoexec.bat to point to it in the ghost folder.  I would suggest putting the ghost.exe back into the ghost folder.  Leave your mouse.com where it is. Then, open the autoexec.bat file with notepad and make sure the path to the ghost.exe is right (per previous example.)

Once we get the ghost disk working properly, the Panasonic drivers problem might be fixed as well. ;D

BTW, here's a link on DOS commands and another on batch files:

Didn't mean to bug you.  ;)    It seemed easier & less likely I might mess it up more.
Long story short, I now have a working 2 disk Ghost created set of floppies.

My 2 disk set of Panasonic Usb Drivers however does not work as it had previously, i.e. - insert it, it loads/looks for USB drives, etc. & then Ghost recognizes the WD ext. HDD.

Tried to use it as I had previously w/ no luck. I may have altered it subsequently per instructions on pg. 1 of this post to get it to work but I've done so much it is all a blur to me at this point.....NOT sure WHY it worked automatically before & does not now....

- on the Ghost created disk the MSDOS.SYS is 0 bytes.
- on the Panasonic Usb Driver disk MSDOS.SYS is 6 bytes.
is this as it should be? obviously i am clueless

Dude, if you don't do what I ask you to do, I'm am not going to waste any more time on your problem! >:(
1.  If you haven't already, move the freakin' ghost.exe file back into the ghost folder on the floppy.
2.  Using notepad, open the freakin' autoexec.bat and copy and paste the contents into your reply to this post.

DO NOTHING ELSE

<<grrrrrrrr>>

wrote on Jan 19^th, 2006 at 3:36pm:

"... Dude, if you don't do what I ask you to do, I'm am not going to waste any more time on your problem!..."

While the expression of such sentiments is commonplace throughout the rest of the cyberworld, these boards are indeed a world apart - and I, for one, find them out of place.


piikea wrote on Jan 18^th, 2006 at 12:00am:

"... (BTW they were generously supplied to me by El_Pescador.)..."

Last summer, I dispatched a highly-modified set of Norton Ghost 2003 boot diskettes bearing NightOwl's Panasonic Universal USB Driver routine to assist piikea with a cranky Western Digital "purpose-built" external HDD.

Regrettably, Hurricane Katrina's floodwaters destroyed virtually everything I once owned in the way of removable magnetic, optical, and print media.  So, I have no ready way to recreate said item as I am living in a FEMA trailer while engaged in torturously renovating my home.  I do recall that the 'autoexec.bat' and 'config.sys' were rather unconventional as were those sub-directories included.

EP :'(

Quote:

tbbrick: Dude, if you don't do what I ask you to do

Essentially I did....& the disk WILL get Ghost.exe up & running.
But FYI - the Ghost created 2 DISK SET - DISK 1 contains:
GHOST folder - empty
USB folder - containing aspiehcs.sys
AUTOEXEC(.bat)
COMMAND
CONFIG.SYS
guest (app)
IO.SYS
MOUSE (app)
MOUSE (config settings)
MSDOS.SYS (size: 0 bytes)

DISK 2 contains:
GHOST folder - containing ghost.exe
AUTOEXEC(.bat) - contents below:

@echo off
SET TZ=GHO+05:00
GUEST.EXE
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

:END
____________________________________
AUTOEXEC(.bat) on Disk 1 looks identical (could post if nec.)


Quote:

tbbrick: Once we get the ghost disk working properly, the Panasonic drivers problem might be fixed as well.

So....the Ghost disks work now but W/O working Panasonic Universal USB Driver floppy(s) Ghost is of no use because IT STILL does not recognize the ext. Western Digital HD where my Ghost images are & updated ones would go.

El_Pescador's disks PREVIOUSLY worked as that is how I got the Ghost images ONTO the ext. HD initially. WHY they do not work as they had b4 I don't know. I reluctantly tried to figure out what was wrong w/ them by reading directions of their creation at beg. of this post & thus they may have been altered but they weren't functioning as needed anyway & I had no other option.

Unfortunately Pesky was flooded out so he has WAY more problems than I at this point so I wish him good luck!!!  

piikea

Post the contents of the *config.sys* file for the above Ghost created two floppy disk boot set.

And in a separate post:

1.  Post the files that are on the floppy disk provided by El_Pescador--is it a one disk or two disk set?

2.  Post the contents of the *config.sys* on the El_Pescador boot disk.

3.  Post the contents of the *autoexec.bat* on the El_Pescador boot disk.

El_Pescador wrote on Jan 19^th, 2006 at 10:06pm:

While the expression of such sentiments is commonplace throughout the rest of the cyberworld, these boards are indeed a world apart - and I, for one, find them out of place. EP :'(

Fair enough.  I suspect you will find this next question sarcastic, but it is not.  What is this board's protocol for telling someone you can't help them if they don't follow directions?   If you read my second post again, I did tell him less pointedly what I needed him to do and if he did so, it might solve both of his problems.  It wasn't until the last post that he finally got it thru his head to give me the autoexec.bat contents I asked for.  

Look, I'm all for helping people.  The Good Lord only knows how much help I've gotten online.  But, I'm not going to waste people's time by ignoring what they advise me to do and I don't want my time wasted as well.

Interesting that NightOwl asked him for more of the same type of information.  I didn't ask for as much as he's an admitted NOOB and wanted to take it one step at a time.



Quote:

Regrettably, Hurricane Katrina's floodwaters destroyed virtually everything I once owned in the way of removable magnetic, optical, and print media.  So, I have no ready way to recreate said item as I am living in a FEMA trailer while engaged in torturously renovating my home.  I do recall that the 'autoexec.bat' and 'config.sys' were rather unconventional as were those sub-directories included. EP

Big time bummer EP.  Hope you aren't in one of those areas that may or may not be torn down if enough neighbors don't return.

tbb

NightOwl wrote on Jan 20^th, 2006 at 2:11am:

Post the contents of the *config.sys* file for the above Ghost created two floppy disk boot set.

Ok --- *config.sys* file from Ghost created Disk 1:

[menu]
menuitem=FROMFLPY, This computer was started from a Ghost boot disk
menuitem=FROMCD, This computer was started from a Ghost bootable CD

[FROMFLPY]

[FROMCD]

[COMMON]
DEVICE = usb\aspiehci.sys /int /all
LASTDRIVE = Z

wrote on Jan 20^th, 2006 at 3:44pm:

It wasn't until the last post that he finally got it thru his head to give me the autoexec.bat contents I asked for.

You didn't ask me to post autoexec.bat contents in your 1st 2 replies. When you asked for it in your 3rd reply I POSTED IT.
I'm not looking to argue w/ anyone....I appreciate your replies/help....I am NOT easily offended.

piikea wrote on Jan 19^th, 2006 at 11:34pm:

Essentially I did....& the disk WILL get Ghost.exe up & running.

Wrong piikea, just because you got Ghost to work, doesn't mean it's working the way EP set it up to work.  

Look at this set of commands in the autoexec.bat file:
{
:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END
}

See how it says "cd \ghost"?  That's DOS telling the computer to change to the subdirectory \ghost.
Then "echo Loading..." is telling it to print "Loading..." on the screen.
Then the "GHOST.EXE " command fires off.  When it does, the "Loading..." on the screen disappears.

In short, the autoexec.bat tells the computer the right folder to get into, then the right command to execute .  

But you said, Ghost won't run unless it's on the root of the floppy, not in the ghost subdirectory.   And that Jedi Warrior is probably why it's not seeing your ext. hard drive.

That's why I (and NightOwl) needed to see the contents of the autoexec.bat.  And since you've posted the config.sys, lets look at the some it's contents:
{
[COMMON]
DEVICE = usb\aspiehci.sys /int /all
LASTDRIVE = Z
}
The "[COMMON]" tells the computer that it doesn't matter if the the user is using a CD or a floppy disk, use the following configurations.  

"DEVICE = usb\aspiehci.sys /int /all" tells it to look into the usb folder to find the right driver that will let you run your ext. hard drive in a DOS environment.

So, if the computer can't find the ghost.exe command in the ghost subdir, it makes sense that it can't find the ext. HDD driver in it's subdir as well.  

Oh, the "LASTDRIVE = Z " says the computer can assign any open letter to your ext. HDD up to the letter Z.  Esp. helpful when you have a boocoo of various drives.  

Sooo, now that I'm sure where the autoexec.bat and config.sys are looking for ghost.exe command and the aspiehci.sys driver, I suspect the boot floppy itself is messed up.

Here's my next question.  (And Dude, just be honest, OK?)  Do you know how to create a boot floopy disk?  If you do, type Yes in reply and create one, but don't do anything to it yet.

If not, type No, tell me what operating system you are using, and I'll give you the drill.


Quote:

Unfortunately Pesky was flooded out so he has WAY more problems than I at this point so I wish him good luck!!!

Roger that Piikea!!!

tbb

NightOwl wrote on Jan 20^th, 2006 at 2:11am:

And in a separate post: 1.  Post the files that are on the floppy disk provided by El_Pescador--is it a one disk or two disk set?

Disk 1 of 2 labeled:
PANASONICDRV1 / MS-DOS / Panasonic USB Drivers contains:
USB folder(containing aspiehcs.sys, Di1000DD.sys, Usbaspi.sys)
AUTOEXEC(.bat)
COMMAND
guest
HIMEM.SYS
IBMBIO
IBMDOS
IO.SYS
MOUSE (app)
MOUSE (config settings)
MSDOS.SYS

Disk 2 of 2 labeled:
PANASONICDRV1 / MS-DOS / Panasonic USB Drivers contains:
GHOST folder containing ghost (app)
USB folder - empty
AUTOEXEC
CONFIG.SYS


Quote:

2.  Post the contents of the *config.sys* on the El_Pescador boot disk.

*config.sys* from disk 2 -

[menu]
menuitem=FROMFLPY, This computer was started from a Ghost boot disk
menuitem=FROMCD, This computer was started from a Ghost bootable CD

[FROMFLPY]

[FROMCD]

[COMMON]
DEVICE = himem.sys
DEVICE = usb\usbaspi.sys /v /w /e
DEVICE = usb\di1000dd.sys
DOS = high,umb
LASTDRIVE = Z


Quote:

3.  Post the contents of the *autoexec.bat* on the El_Pescador boot disk.

*autoexec.bat* from disk 2 -

@echo off
SET TZ=GHO+06:00
PATH=A:\;A:\GHOST;A:\USB
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

:END

There is an *autoexec.bat* file on disk 1 too but can ONLY open with notepad & it is a jumble of letters (probably because it's a wordpad doc) OR edit which opens a DOS window to A: prompt & "bad file or cammand".

***As I said I may have altered them reluctantly trying to "recreate" them per instructions on post pg. 1. I likely messed them up.

Thanks all for the assistance!

piikea wrote on Jan 20^th, 2006 at 4:02pm:

You didn't ask me to post autoexec.bat contents in your 1st 2 replies. When you asked for it in your 3rd reply I POSTED IT. I'm not looking to argue w/ anyone....I appreciate your replies/help....I am NOT easily offended.

Correct, I did not ask you to post the contents of your autoexec.bat, I asked you to tell me which subdir it was pointing to to find the Ghost.exe.  I asked for the autoexec.bat contents in post three because I thot you were too whatever to admit you didn't know what I was asking for.

Snip of post 1:
Using Windows Explorer, see if Ghost.exe is on the root or if it's in some subdirectory on your floppy.  Next, use notepad to open the autoexec.bat file to check the path, i.e. a:\ghostfolder\ghost.exe it's using to crank it up.  If you make any changes to it, be sure notepad saves the autoexec to .bat, not .txt extension.
End Snip

Snip of post 2:
What's bugging me is that you said you took the ghost.exe out of the ghost folder, (and put it on the floppy root Huh) rather than changing the autoexec.bat to point to it in the ghost folder.  I would suggest putting the ghost.exe back into the ghost folder.  Leave your mouse.com where it is. Then, open the autoexec.bat file with notepad and make sure the path to the ghost.exe is right (per previous example.)
End Snip

tbb

piikea wrote on Jan 20^th, 2006 at 4:36pm:

There is an *autoexec.bat* file on disk 1 too but can ONLY open with notepad & it is a jumble of letters (probably because it's a wordpad doc) OR edit which opens a DOS window to A: prompt & "bad file or cammand". ***As I said I may have altered them reluctantly trying to "recreate" them per instructions on post pg. 1. I likely messed them up.

Ahhh piikea, the plot doth indeed thicken.  If you opened Disk 1's autoexec.bat with WordPad and saved, you need to come out and admit it.  Which is why I said to use Notepad in the first two posts.  When you save files in Notepad, it doesn't insert a buncha formatting crap in the files like WordPad or any other late model word processing program does.  It just saves what you wrote.

Still, let me know if you can create a boot disk or not.  And while you are at it, using Windows Explorer, make two folders on your computer's C drive called Ghost Disk 1 and Ghost Disk 2.  Copy and paste the contents of each Ghost disk in the respective C drive folder so nothing else get's messed up.  A trick I learned from a few agonies of computing defeat of my own.  ;)

YES - I can & have:

A working Windows Me created Windows Me boot disk as well as a Windows 98SE boot disk (supplied as part of El_Pescador's set of floppies).

Ghost asks for Windows 95/98 formatted floppies when it creates it's 2 disk set(?).

Also put copies of Ghost disks on C:\

Very good piikea!!!  Now, as much as I'm not fond of Windoze Massive Excrement, let's use it to start with.  If you get a  warning that you are going to overwrite any files in the following directions, click ok to replace the floppy files.

1. Open up Windows Explorer.
2. Insert the newly made ME boot disk in the A drive.
3. Make a folder called USB on the ME boot floppy.
4. From the C Drive Ghost Disk 1 folder, copy the contents of the USB folder (which you ID as aspiehcs.sys, Di1000DD.sys, Usbaspi.sys) into the ME boot USB folder.
5. Still in the Ghost Disk 1 folder, copy the Guest.exe, MOUSE (app) and MOUSE (config settings) to the ME boot disk.
6. Go to the Ghost Disk 2 folder and copy the good Autoexec.bat and config.sys files to the ME boot disk.
7. Shut down the computer completely.
8. While the PC is still off, plug in your ext. HDD, connect the USB cable, and power it up.  
9. Now, turn on your PC and boot from the ME boot disk.  
10. After it boots, it should ask for the disk 2, put in the original disk 2 and hit enter.
11.  Hopefully, at this point, it should automatically start Ghost and should see your ext. HDD.

Let us know how it goes.  I've got to go and won't be online tomorrow.  But I'll try to check my email Sunday and see what happened.

tbb

wrote on Jan 20^th, 2006 at 3:44pm:

"... Big time bummer EP.  Hope you aren't in one of those areas that may or may not be torn down if enough neighbors don't return..."

Fortunately, I live on the northern shore of Lake Pontchartrain and not down in Mayor Wonka's 'Chocolate City' where only yesterday did his Director of Homeland Security - City of New Orleans discover that the Big Easy had only received 1,700 FEMA travel trailers while neighboring counties in Mississippi were enjoying 31,000.  The Crescent City really should import experts skilled in misgovernance from Haiti and Somalia so as to "jump-start" the recovery effort at the local level.

Not long ago, I had the pleasure of briefly visiting with the Number Three executive of one of the most respected disaster-recovery contractors extant in the USA.  He sadly related that the rate-of-installation for the now ubiquitous FEMA travel trailers his firm is placing could be increased twenty-fold if only all levels of government would respectively release their strangulating "red-tape".

EP :'(

piikea


Quote:

There is an *autoexec.bat* file on disk 1 too but can ONLY open with notepad & it is a jumble of letters (probably because it's a wordpad doc) OR edit which opens a DOS window to A: prompt & "bad file or cammand".

This is the problem most likely--you have to have a *functional* *autoexec.bat* file on that first disk for booting.

Here's a simple fix--if everything else is *okay*--just delete the *autoexec.bat* that's on the first disk.  The *autoexec.bat* on the second disk should be identical to the one that was on the first disk--so just *copy* (leave the original on that second disk) the *autoexec.bat* from the second disk to the first disk.

Try booting--how did it go?

NightOwl wrote on Jan 21^st, 2006 at 12:19am:

piikea This is the problem most likely--you have to have a *functional* *autoexec.bat* file on that first disk for booting. Here's a simple fix--if everything else is *okay*--just delete the *autoexec.bat* that's on the first disk.  The *autoexec.bat* on the second disk should be identical to the one that was on the first disk--so just *copy* (leave the original on that second disk) the *autoexec.bat* from the second disk to the first disk. Try booting--how did it go?

Tried this 1st as it was simpler/faster but unfortunately it didn't get it working. Just got to a: prompt.

Maybe *autoexec.bat* on both not set up properly(?)...dunno. Seems to me whatever necessary command in whatever file that tells computer to "run/load" the drivers is not there or wrong. Only my guess based on fact that b4 I put disk in & maybe press enter & it went thru sequence - "finding drivers, etc." or something to that effect.

piikea

When you boot with the boot floppy, after the initial computer's POST, when the floppy is first accessed--pressing *F8* should bring up a boot screen menu with several choices--one being *step-by-step* confirmation of loading the device drivers from *config.sys* and *autoexec.bat*.

Go through each step, answering *Y* for *yes*--and see what is reported  by each step.  Does everything load, any error messages, any steps *skipped*, are the USB DOS drivers loading (usbaspi.sys* and *di1000dd.sys*), are drive letters being assigned, etc....report the results.

wrote on Jan 20^th, 2006 at 6:00pm:

Very good piikea!!!  Now, as much as I'm not fond of Windoze Massive Excrement..............Let us know how it goes. tbb

Agreed, Me is a mess & exactly WHY I began trying to have/create back ups!!!

I did as you instructed & momentarily thought it was successful.  It DID function as you said would, however Ghost still did not recognize the ext. HDD.  It did "scanning" thing but said "no devices found" then asked for disk 2 as I recall.

Just to clarify too -
1. I have the 2 disk Ghost created disk set.
2. A seperate 2 disk "Universal Panasonic driver" set originally created by NightOwl/El_Pescador (designed to get Ghost to "see" ext. HDD's in DOS mode; not specifically designed for Western Digital ext. HDD's though IT HAD worked previously w/ this same pc & ext. HDD).
and,
3. the WMe boot floppy you had me create (to which I made the changes as you instructed).


Quote:

If you opened Disk 1's autoexec.bat with WordPad and saved, you need to come out and admit it.

Missed that earlier....I generally woulda used notepad. However, as I was trying to follow NightOwl's directions (originally) on page 1 of this post on the Driver set's creation - it says use Wordpad. I was not sure WHICH to use.

NightOwl wrote on Jan 21^st, 2006 at 5:51pm:

report the results.

Forgive my ignorance, I assume you mean boot w/ the panasonic driver disk 1 (as the W98SE disk El_P sent wouldn't/doesn't have those drivers on it; they are now on the newly created WMe boot disk augmented as tbbrick instructed) but you must mean your set.

Uh....yes....errors....
step 5. DEVICE=USBASPI.SYS
"the following file is missing or corrupted: USBASPI.SYS. There is an error in your CONFIG.SYS file on line 2"
step 6. DEVICE=ASPIEHCI.SYS
same error message except line 3
step 7. DEVICE=Di1000DD.SYS
same error message except line 4
step 11. GUEST.EXE
"Iomega Guest Driver version 8.5, no drive letter added"
step 12. MOUSE.COM
"mouse driver installed"
step 15. if == FROMFLPY goto FLPYBOOT
"syntax error"
step 16. if == FROMCD goto CDBOOT
"syntax error"
step 17. goto FAILED
step 18. Unknown boot menu selection
step 19. Unknown boot menu selection goto END
and lastly........
A:\>  prompt.

Clearly it is corrupted OR I messed things up trying to "fix" it. The drivers may be corrupt but they ARE there in a folder called USB. If needed I can post contents of:
*config.sys* and *autoexec.bat*.

Sorry this has become such a pain....

piikea

Now I'm confused--it looks like you have now posted the results from three different boot disk sets--I thought you were trying to get the boot disks sent by El_Pescador working...

So, you decide which boot set you wish to work on..., but the information that you report has to be from only one set--you choose--but report the information from the one set.

Yes--need the contents of *config.sys* and *autoexec.bat*, the list of files and directories on the disk(s), and the error messages that occur for that particular set of boot files seen by using F8 during boot.

Quote:

Now I'm confused--it looks like you have now posted the results from three different boot disk sets--I thought you were trying to get the boot disks sent by El_Pescador working...

Yes, the boot disks sent by El_Pescador are the problem. The info above are the error messages that occur(ed) for those disks using step by step confirmation during F8 boot.

The contents of *config.sys* and *autoexec.bat* & the list of files and directories on the disk(s) are below:

Disk 1 (of 2) labeled:
PANASONICDRV1 / MS-DOS / Panasonic USB Drivers contains:

USB folder w/ aspiehcs.sys, Di1000DD.sys, Usbaspi.sys
AUTOEXEC(.bat)
COMMAND
CONFIG.SYS
guest
HIMEM.SYS
IBMBIO
IBMDOS
IO.SYS
MOUSE (app)
MOUSE (config settings)
MSDOS.SYS

Disk 2 (of 2) labeled:
PANASONICDRV2 / MS-DOS / Panasonic USB Drivers contains:

GHOST folder containing ghost (app)
USB folder - empty
AUTOEXEC
CONFIG.SYS

Disk 1 AUTOEXEC(.bat) -

@echo off
SET TZ=GHO+06:00
GUEST.EXE
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

:END

Disk 1  CONFIG.SYS -

Device=himem.sys
Device=usbaspi.sys /e /v
Device=aspiehci.sys
Device=di1000dd.sys @echo off
SET TZ=GHO+06:00
PATH=A:\;A:\GHOST;A:\USB
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END
Dos=high,umb
Lastdrive=z

Disk 2 AUTOEXEC(.bat) -

@echo off
SET TZ=GHO+06:00
PATH=A:\;A:\GHOST;A:\USB
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

Disk 2 config.sys -

[menu]
menuitem=FROMFLPY, This computer was started from a Ghost boot disk
menuitem=FROMCD, This computer was started from a Ghost bootable CD

[FROMFLPY]

[FROMCD]

[COMMON]
DEVICE = himem.sys
DEVICE = usb\usbaspi.sys /v /w /e
DEVICE = usb\di1000dd.sys
DOS = high,umb
LASTDRIVE = Z

piikea

Okay--it looks like the *config.sys* and *autoexec.bat* on disk 1 are not correct.  Delete both of those files from disk 1.

The *config.sys* and *autoexec.bat* on disk 2 appear to be correct!  Copy those from disk 2 to disk 1!

Now try those boot disks using the *F8* at startup and report if that works--or what errors occur!

piikea wrote on Jan 21^st, 2006 at 6:56pm:

Forgive my ignorance, I assume you mean boot w/ the panasonic driver disk 1 (as the W98SE disk El_P sent wouldn't/doesn't have those drivers on it; they are now on the newly created WMe boot disk augmented as tbbrick instructed) but you must mean your set.

piikea,
First, sorry I couldn't get back online yesterday as I'd hoped.

Since Pesky sent you the disks originally and NightOwl is having you go thru the "check it out drill," I'll lurk for the time being.  I agree with NO, that you should work with one set of disks.

I do have one question for 'it's and giggles.  In post 21 Jan 06 0/a 1700, you wrote:

Quote:

I did as you instructed & momentarily thought it was successful.  It DID function as you said would, however Ghost still did not recognize the ext. HDD.  It did "scanning" thing but said "no devices found" then asked for disk 2 as I recall.

Did you insert disk 2 as prompted, and if so, what happened?

Like I said, keep on with NO's able instruction and set aside the ME boot disk we were working with for the time being.  Unless of course, NO asks you to pull it out.

El_Pescador wrote on Jan 20^th, 2006 at 10:03pm:

Not long ago, I had the pleasure of briefly visiting with the Number Three executive of one of the most respected disaster-recovery contractors extant in the USA.  He sadly related that the rate-of-installation for the now ubiquitous FEMA travel trailers his firm is placing could be increased twenty-fold if only all levels of government would respectively release their strangulating "red-tape".EP :'(

Pesky, Pesky, now you're starting to talk logically.  As a former service member (USAF,) I found that cooperation between gov. agencies was always a trip.  In this case, you have city, state, AND Fed operators, all fighting to keep control of power/$$$.   God have mercy on the people they're supposed to be "helping." :P

piikea wrote on Jan 22^nd, 2006 at 6:57pm:

"... Yes, the boot disks sent by El_Pescador are the problem...."

It appears additional material was subsequently added to the boot disk set I sent piikea via US Mail; such items are boldly highlighted in yellow below and should be removed:

The contents of *config.sys* and *autoexec.bat* & the list of files and directories on the disk(s) are below:

Disk 1 (of 2) labeled:
PANASONICDRV1 / MS-DOS / Panasonic USB Drivers contains:

USB folder w/ aspiehci.sys, Di1000DD.sys, Usbaspi.sys
AUTOEXEC(.bat)
COMMAND
CONFIG.SYS
guest
HIMEM.SYS
IBMBIO
IBMDOS
IO.SYS
MOUSE (app)
MOUSE (config settings)
MSDOS.SYS

Disk 2 (of 2) labeled:
PANASONICDRV2 / MS-DOS / Panasonic USB Drivers contains:

GHOST folder containing ghost (app)
USB folder - empty
AUTOEXEC
CONFIG.SYS

Disk 1 AUTOEXEC(.bat) -

@echo off
SET TZ=GHO+06:00
GUEST.EXE
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

:END

Disk 1  CONFIG.SYS -

Device=himem.sys
Device=usbaspi.sys /e /v
Device=aspiehci.sys
Device=di1000dd.sys @echo off
SET TZ=GHO+06:00
PATH=A:\;A:\GHOST;A:\USB
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END
Dos=high,umb
Lastdrive=z

Disk 2 AUTOEXEC(.bat) -

@echo off
SET TZ=GHO+06:00
PATH=A:\;A:\GHOST;A:\USB
MOUSE.COM
echo Loading...
cls

if %config% == FROMFLPY goto FLPYBOOT
if %config% == FROMCD goto CDBOOT

goto FAILED

:FLPYBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if exist a:\ghost\ghost.exe goto GHOSTFND
goto FLPYBOOT

:CDBOOT
echo Insert Ghost boot disk 2 (containing Ghost.exe)
pause
if not exist b:\ghost\ghost.exe goto CDBOOT
b:
goto GHOSTFND

:GHOSTFND
cd \ghost
echo Loading...
GHOST.EXE
goto END

:FAILED
echo Unknown boot menu selection
goto END

Disk 2 config.sys -

[menu]
menuitem=FROMFLPY, This computer was started from a Ghost boot disk
menuitem=FROMCD, This computer was started from a Ghost bootable CD

[FROMFLPY]

[FROMCD]

[COMMON]
DEVICE = himem.sys
DEVICE = usb\usbaspi.sys /v /w /e
DEVICE = usb\di1000dd.sys
DOS = high,umb
LASTDRIVE = Z

As an afterthought, the very latest version of usbaspi.sys should be substituted for what was dispatched last year.

EP :'(

NightOwl wrote on Jan 22^nd, 2006 at 11:57pm:

piikea Okay--it looks like the *config.sys* and *autoexec.bat* on disk 1 are not correct.  Delete both of those files from disk 1. The *config.sys* and *autoexec.bat* on disk 2 appear to be correct!  Copy those from disk 2 to disk 1! Now try those boot disks using the *F8* at startup and report if that works--or what errors occur!

NightOwl - i did "copy those from disk 2 to disk 1" & IT WORKS! Went thru F8 step by step (not including each step's results though I can if interested) & it eventually asked for Ghost Boot disk 2 which I put in & Ghost ran & the ext. HDD WAS recognized (so I can now use Ghost w/ it!).


Quote:

tbbrick: Did you insert disk 2 as prompted, and if so, what happened?

Yes I did & Ghost ran okay BUT the ext. HDD was NOT recognized.


Quote:

El_Pescador: such items are boldly highlighted in yellow below and should be removed:

Decided to check the disks after making changes as NightOwl suggested as 1st step & as IT IS FUNCTIONING as designed now I think I should leave well enough alone & play it safe!

BTW - I did run the Panasonic Drivers disk w/o using F8 subsequently to see if it worked "automatically" & it did work properly.

Thanks to all for time & help.  Good luck EL_P!

piikea

Glad to hear you're back on track  ;) !

piikea wrote on Jan 23^rd, 2006 at 5:59pm:

"... IT IS FUNCTIONING as designed now I think I should leave well enough alone & play it safe!..."

I maintain you would be well-served - in the long run, at least - to remove the guest(.exe) command and all lines containing aspiehci.sys as you risk mixing in the incompatible Norton/Iomega USB drivers with the compatible USB Panasonic drivers.

EP :'(

El_Pescador wrote on Jan 23^rd, 2006 at 9:44pm:

I maintain you would be well-served - in the long run, at least - to remove the guest(.exe) command and all lines containing aspiehci.sys as you risk mixing in the incompatible Norton/Iomega USB drivers with the compatible USB Panasonic drivers. EP :'(

Just FYI EL_P I made a copy of the working floppy & removed items you mentioned above. It did work properly (i.e., scanned & recognized ext. HDD AND Ghost ran ok) however when it asked for Ghost disk 2 & I inserted it -- it initially said "bad command of file", then (apparently) continued "looking" or "looked" elsewhere & found Ghost.
A Ghost error log from the floppy afterwards read as follows:

Date   : Mon Jan 23 16:14:25 2006
Error Number: (19010)
Message: Arguments must be preceeded with a '-' or a '/'
Version: 2003.775 (Aug 14 2002, Build=775)
Command line arguments: goto GHOSTFND
Active Switches :
      AutoName

I now have 2 working Panasonic Drivers disks so it's not really a problem....just relaying it for all our general edification.

piikea wrote on Jan 25^th, 2006 at 2:41am:

I now have 2 working Panasonic Drivers disks so it's not really a problem....just relaying it for all our general edification.

Glad to read it's doing right for you.

tbb

wrote on Feb 3^rd, 2006 at 6:12pm:

Glad to read it's doing right for you. tbb

Yeah - thanks for your help along the way!

has anyone found a way to make the USB Mouse and Keyboard work when using the aspiehci.sys driver?  I can get it to work with I REM out the line in config.sys and my drive is still detected but I don't think it makes the controller USB2.0 but rather 1.1.  I maybe incorrect, does anyone have any suggestions?

P.S USBaspi.sys does not work for my external HDD

wrote on Feb 7^th, 2006 at 1:38pm:

"... has anyone found a way to make the USB Mouse and Keyboard work when using the aspiehci.sys driver?..."

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1095438251;start=142#142


wrote on Feb 7^th, 2006 at 1:38pm:

"... P.S. USBaspi.sys does not work for my external HDD..."

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1121910396;start=6#6

If you are having difficulty with an USB external HDD when working with Norton Ghost 2003, then you have indeed come to the right place!

EP :'(