Jump to content











Photo
- - - - -

Speed UP USB ghost image transfer in Dos


  • Please log in to reply
64 replies to this topic

#26 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 16 July 2010 - 02:10 PM

Any ideas, captain? ;)


Are you still testing in a Virtual Machine or you are now on "real" hardware? ;)

What do you mean by this :thumbup::

Changed to what I know works
ctload usbaspi.sys /v[panasonic 2.20]
ctload di1000dd.sys

Using this ALL USB STICKS I have tested load fine
but this "ctload di1000dd.sys" causes a freak out either locks up or just pipes out a load of smiley faces and heart shapes and stops the boot process.


I read the first part as a report that the whatever you are now doing with the panasonic 2.20 drivers is working and the second part as a report that they DO NOT? ;)

Did you take note of this ?:
http://johnson.tmfc....dos/usbdrv.html

** Notice:

[1] These USB Drivers only work for storage device like Flash Disk, USB hard disk or USB CD-ROM, device such as Mouse or Printer were not supported.

[2] During my research of GHOST a Serial-ATA hard disk to USB hard disk, I found a limitation of the DI1000DD.SYS (NOVAC), it only support FAT16 format! If you format your USB connected hard disk with FAT32, it shows nothing when you type DIR, when you try to FORMAT it, the PC will crash!



:cheers:
Wonko

#27 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 16 July 2010 - 02:27 PM

REAL HARDWARE: LAPTOP

I read the first part as a report that the whatever you are now doing with the panasonic 2.20 drivers is working and the second part as a report that they DO NOT? dubbio.gif

I have been using F8 to load all the parts of the boot in turn so USBAPSI ok, then the DI1000DD.SYS then fails thats what I meant dude.

** Notice:

[1] These USB Drivers only work for storage device like Flash Disk, USB hard disk or USB CD-ROM, device such as Mouse or Printer were not supported.

[2] During my research of GHOST a Serial-ATA hard disk to USB hard disk, I found a limitation of the DI1000DD.SYS (NOVAC), it only support FAT16 format! If you format your USB connected hard disk with FAT32, it shows nothing when you type DIR, when you try to FORMAT it, the PC will crash!

Uh oh! erm, maybe this is the end of the road, 4gb partition size limit is out of the question.
(sound of window breaking....AAAaaaaaaaaarrhjjjjjjjhhhhhhhh...splat. THE END)

#28 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 16 July 2010 - 06:22 PM

Why the end of the road? :ph34r:

Maybe the end of ONE road, but there is more than one way to skin a cat (though the cat won't be happy no matter which one you use :().


This:

Using this ALL USB STICKS I have tested load fine

means (at least in my foreigner English) that ALL USB STICKS (you have tested) LOAD FINE (which cannot be if di1000dd.sys crashes :thumbup:).

It is very possible that the Panasonic drivers are somehow incompatible with that particular laptop of yours, but it's unlikely that BOTH the Panasonic drivers AND the Iomega ones will be. :cheers:


Check this:
http://www.georgpotthast.de/usb/

In passing by I would like to point out:
http://www.georgpott...sb/licencen.htm
the REASONS the Author declares for it being gone Commercial:

DOSUSB licence information

DOSUSB is no longer free for personal use since too many commercial users did not order a licence.

So a demo version is free for download now. See the LICENCE.TXT file in the download package for details.

once said that the Author has all the rights in the world on his creation :cheers:, I find - to say the least - queer :( - that since Commercial users behaved dishonestly then non-professional users should be "punished". :cheers:

:thumbup:
Wonko

#29 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 16 July 2010 - 07:08 PM

:ph34r:

#30 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 12:09 AM

Had a break and came back and started again. I had a very big GOOGLE and found this post

"that's when the above USB DOS driver takes control of the USB controller and mounts the USB HDD's so they are seen in DOS. But, by taking control of the USB controller, that may also take over control so the USB floppy drive is no longer being read! And, if that's the case, then the boot process will stall there because the next step can not be taken by reading the floppy disk!
You could try adding that floppy drive RAM driver (The Panasonic USB DOS RAM Floppy Driver--RAMFD.SYS) and see it that solves the issue"

This sounded familiar as whenever I got a loaded USBASPI.SYS it always failed (couldnt find etc or said was corrupted) on DI1000DD.SYS, I'm not sure if the freedos floppy loaded it either!!



So just with my original VFD I thought I would see what happened I didn't expect ANYTHING

Config sys:
DEVICE=himem.sys /testmem:off /v
DEVICE=btdosm.sys
DEVICE=flashpt.sys
DEVICE=RAMFD.SYS
Device=usbaspi.sys /v
Device=di1000dd.sys /dC
LASTDRIVE = Z

Autoexec
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
C:
C:\32L\cddeploy

with that I get this far (futher than before) and a hang....

Posted Image

Uploaded with ImageShack.us

and with this
config.sys
DEVICE=himem.sys /testmem:off /v
DEVICE=btdosm.sys
DEVICE=flashpt.sys
DEVICE=RAMFD.SYS
Device=usbaspi.sys /v
Device=di1000dd.sys >>>>>>>>>>NO SWITCH<<<<<<<<<<<
LASTDRIVE = Z

Posted Image

Uploaded with ImageShack.us

IS there anything worth pursuing in this finding? I was definitley going to shelve this but in the thread where I found this people seemed to be doing a similar thing with HDD's (bigger than 4gb). Maybe its because its doing it in memory?

[2] During my research of GHOST a Serial-ATA hard disk to USB hard disk, I found a limitation of the DI1000DD.SYS (NOVAC), it only support FAT16 format! If you format your USB connected hard disk with FAT32, it shows nothing when you type DIR, when you try to FORMAT it, the PC will crash!

Also with regard to that I was able to navigate to the CDDEPLOY.BAT after abort retry fail and running dir but still general failure reading drive C: - ODD BECAUSE IT SHOULD TRY AND RUN SOME OF THE BAT and fail coz havent put files it needs there yet

Posted Image

Uploaded with ImageShack.us

#31 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 17 July 2010 - 12:22 AM

WHICH thread?

My crystal ball is in the shop for tuning, again. :thumbup:

The second screenshot shows that everything is correct BUT the cddeploy.bat fails.

Unless you post it's contents it will be tough to understand what the problem is (see above).

Cannot you simply REMOVE the stoopid batch and check MANUALLY if the drives are accessible?

WHAT are these drivers?

DEVICE=btdosm.sys
DEVICE=flashpt.sys

maybe they create a conflict of some kind. :(

:ph34r:
Wonko

#32 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 12:28 AM

LOL - must the best crystal ball in town with all that tuning, will I win the lottery, Wonko? :ph34r:

http://radified.com/...?num=1258054404 (3/4's down about)

im not sure what those things sys's do but of course will test their absence in this....

copying a "proper" set of files across will take ages and thus its bed time, will report back asap seargent! :(

#33 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 17 July 2010 - 12:34 AM

I have been downgraded before in my life, but maybe from captain to sergeant in one single step is a bit too much :cheers:

will report back asap seargent! :thumbup:



Any ideas, captain? :ph34r:


:(

:cheers:
Wonko

#34 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 08:17 AM

ow, come on!....captain, seargent........whatever............you just know your the boss! :thumbup:

Hey something weird with this, not looking too hot, will try and get all the info you need. ALTHOUGH SERIOUSLY I'm CLOSE MAN
PLEASE PLEASE JUST HONE IN AND NOBBLE THIS chdk dis

1. Removed the two entries in config.sys
DEVICE=himem.sys /testmem:off /v
rem DEVICE=btdosm.sys
rem DEVICE=flashpt.sys
DEVICE=RAMFD.SYS
Device=usbaspi.sys /v
Device=di1000dd.sys
LASTDRIVE = Z

didnt make no difference BUT THIS DID AND THIS REALLY MESSING

autoexec.bat
WAS
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
C:\32l\CDDEPLOY.BAT

(decided to just test having a flat file structure i.e no subdirectories all on root, so.......)
given that the above cinfig.sys gives the USB a D: letter I changed it to
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
D:\CDDEPLOY.BAT

and just feast on this , if I ok it starts ghosting, albeit slowly but this is a machine that doesnt need anyhelp so can create two
options in menu USB SUPPORT or STANDARD and fire them off 2 vfd's one with usb and not etc.
Posted Image

Uploaded with ImageShack.us

So now let me get on with the oddness on my sticks I need the ghosts for desktops and laptops in 2 separate folders ie. 32L & 32D
(version 3.2 laptops & version 3.2 Desktops) If I just tweak the known working solution, see what happens
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
D:\32L\CDDEPLOY.BAT

################################################################################
####################




MAJOR UPDATE - I THOUGHT "GET RID OF THE NUMBERS IN THE FOLDER NAME"

JUST CHANGED TO
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
D:\LAPTOP\CDDEPLOY.BAT

Posted Image

Uploaded with ImageShack.us

And, check it outtttttttttttttttttttttt!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Posted Image

Uploaded with ImageShack.us
Obviously any paths in the cddeploy read d:\LAPTOP instead of C:\32L
I don't think this will work for ALL usb sticks will it? Some it wont detect? On this test laptop with out this USB support
it would be really fast but just looking its terrible??? Can that be right, need to test on the older slower machines first dont I?

#35 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 11:12 AM

DAMN spoke too soon................getting general read failure right at the end of the script after ghost......................... here it is...........BTW....I didn't write it LOL. have ammended right where it fails - fingers crossed you can see

@ECHO OFF
REM Deployment Procedure
REM
REM Set the image variable (so it's obvious)
REM Set Image=SR31
Set Image=SR32
REM Set Image=SR40
REM set Image=Flexi
REM
REM Get the Bios info in SMBIOS2.TXT on the local ram drive (Q:)
rem
dir q:\ > q:\dir.txt
D:\LAPTOP32L\smbios2.exe /G > q:\smbios2.txt
REM
D:\LAPTOP32L\sed -n -e "s/Product Name:/Set MBoard=/w q:\MBoard.Bat" q:\smbios2.txt
D:\LAPTOP32L\sed -e "s/ '//g;s/'//g" q:\MBoard.bat > q:\prodname.bat
REM
D:\LAPTOP32L\sed -n -e "s/Product:/Set MBoard1=/w q:\MBoard1.Bat" q:\smbios2.txt
D:\LAPTOP32L\sed -e "s/ '//g;s/'//g" q:\MBoard1.bat > q:\prodcode.bat
REM
D:\LAPTOP32L\sed -n -e "s/Asset Tag Number:/Set AssetTag=/w q:\Asset1.Bat" q:\smbios2.txt
D:\LAPTOP32L\sed -e "s/ '//g;s/'//g" q:\Asset1.bat > q:\asset.bat
REM
REM Set the AssetTag environment variable
Call q:\Asset.Bat
REM
REM Set the MBoard environment variable
call q:\prodname.bat
Call q:\prodcode.Bat
REM
REM Validate the AssetTag as being Znnnnnnn where n is 0-9
ECHO Have determined machine as %mboard% , code [%mboard1%]
ECHO Have determined machine name as %AssetTag%
rem
pause
rem
D:\LAPTOP32L\sed -e "s/AssetTag/AssetChr/" q:\Asset.Bat > q:\Asset1.Bat
D:\LAPTOP32L\sed -e "s/Z1/zdOK/g" q:\Asset1.bat > q:\Asset2.Bat
D:\LAPTOP32L\sed -e "s/z1/zdOK/g" q:\Asset2.bat > q:\Asset3.Bat
D:\LAPTOP32L\sed -e "s/Z2/zlOK/g" q:\Asset3.bat > q:\Asset4.Bat
D:\LAPTOP32L\sed -e "s/z2/zlOK/g" q:\Asset4.bat > q:\Asset5.Bat
D:\LAPTOP32L\sed -e "s/[0-9]/nOK/g" q:\Asset5.Bat > q:\AssetChk.Bat
Call q:\AssetChk.Bat
If %AssetChr%==zdOKnOKnOKnOKnOKnOKnOK Goto :DoGhostD
If %AssetChr%==zlOKnOKnOKnOKnOKnOKnOK Goto :DoGhostL
ECHO.
ECHO Asset Tag retrieved from BIOS does not match Znnnnnnn where n=0-9
ECHO.
ECHO Asset Tag discovered is %AssetTag%
ECHO.
ECHO Change the Asset Tag in the BIOS and retry the installation
ECHO.
Pause
D:\LAPTOP32L\reboot.com
EXIT
:DoGhostD
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
D:\LAPTOP32L\ghost.exe -nousb -fni -clone,mode=load,src=D:\LAPTOP32L\D%Image%.gho,dst=2 -sure
Goto :DISKINFO
:DoGhostL
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
D:\LAPTOP32L\ghost.exe -nousb -fni -clone,mode=load,src=D:\LAPTOP32L\L%Image%.gho,dst=2 -sure
Goto :DISKINFO
REM
:DISKINFO
REM
echo omnifs
REM Determine the hard drive volume number - Get disk info into text file
D:\LAPTOP32L\OMNIFS -nousb INFO > q:\DSKINFO.TXT
REM
echo volinfo
REM Determine the hard drive volume number - Get volume info of NTFS drive into text file
D:\LAPTOP32L\SED -n "s/NTFS/SFTN/w q:\VOLINFO.TXT" q:\DSKINFO.TXT
REM
echo volnum
REM Determine the hard drive volume number - remove everything after the " (" - that is space open-bracket
D:\LAPTOP32L\SED -e "s/^[ ]*/Set Vol=/g;s/ (.*$//g" Q:\VOLINFO.TXT > Q:\VOL.BAT
REM
Call q:\VOL.BAT
ECHO Using %VOL% as volume number for hard-drive
REM
echo sysprep read
REM Get the sysprep.inf file from the image to the local ram drive (Q:)
D:\LAPTOP32L\omnifs -nousb copy %VOL%\sysprep\sysprep.inf q:\sysprep.old
REM
echo set computer name
REM Substitute the AssetTag into the ComputerName sysprep entry (requires original sysprep.inf as sysprep.old)
D:\LAPTOP32L\sed -e "s/ComputerName=.*$/ComputerName=%AssetTag%/g" q:\sysprep.old > q:\sysprep.inf
REM
echo update uphal check
REM Check for the n620 (0824) and the nc6000 (0890) and do the HALFix otherwise don't
If %Mboard1%==0824 Goto :HAL_Fix
If %Mboard1%==0890 Goto :HAL_Fix
Goto :NoHAL_Fix
REM
REM Comment out the UpdateUPHAL line for the n620 (0824) and the nc6000 (0890)
:HAL_Fix
D:\LAPTOP32L\sed -e s/UpdateUPHAL/;UpdateUPHAL/ q:\sysprep.inf > q:\sysprep.new
:NoHAL_Fix
REM
echo replace modified sysprep
REM Copy the modified sysprep.inf back to the image <<<<<<<

FAILED HERE WITH general read failure reading C:\
seems to have a problem with C: I tried adding DI1000DD.sys /DC to config.sys
but it hangs as soon as the C: is allocated in dos


D:\LAPTOP32L\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM
REM If there is a sysprep.new (with the commented out UpdateUPHAL) then overcopy it
if exist D:\LAPTOP32L\sysprep.new D:\LAPTOP32L\omnifs -nousb copy D:\LAPTOP32L\sysprep.new %VOL%\sysprep\sysprep.inf
REM
:EXIT_POINT
REM
D:\LAPTOP32L\reboot.com

#36 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 17 July 2010 - 02:15 PM

ow, come on!....captain, seargent........whatever............you just know your the boss! :thumbup:

Hmm :thumbup:, nice try, but I've seen doing better :cheers::
http://www.boot-land...?...=2958&st=15


With all due respect for the peep that wrote that batch, I have rarely seen such a convoluted way to write anything in batch, which doesn't mean that it shouldn't or it wouldn't work :cheers:, only that it would be probably easier to re-write it than to understand how it works and what it is (supposed to be ) doing. :cheers:

This seems like the "crucial" part:

REM Determine the hard drive volume number - Get volume info of NTFS drive into text file
D:\LAPTOP32L\SED -n "s/NTFS/SFTN/w q:\VOLINFO.TXT" q:\DSKINFO.TXT
REM
echo volnum
REM Determine the hard drive volume number - remove everything after the " (" - that is space open-bracket
D:\LAPTOP32L\SED -e "s/^[ ]*/Set Vol=/g;s/ (.*$//g" Q:\VOLINFO.TXT > Q:\VOL.BAT
REM
Call q:\VOL.BAT
ECHO Using %VOL% as volume number for hard-drive



The only clear thing is that the RAMDISK gets letter Q: (because you assign it with
XMSDSK 2048 Q&#58; /y
The CD (COMPLETELY uneeded in such a scheme) WAS assigned letter X::
REM LH MSCDEX.EXE /D&#58;cd0 /L&#58;X
WHAT the heck is supposed to be letter D: ? :thumbup:
Please choose one:
  • The USB stick
  • The Internal hard disk
  • Something else

WHAT he heck is supposed to get letter C: ? :(

This:
DI1000DD.sys /DC
is to have the USB stick as C:

Then WHICH letter will get the HD?

Post the ORIGINAL batch file (the one BEFORE you fiddled with it), maybe I can make head or tail of that. :cheers:

As a general rule, unless you are writing a quick and dirty something for your private use, a batch should be written in such a way that is easily understandable.
Example:
&#58;&#58;SET THE DRIVE LETTERS

SET RAMDISK=Q&#58;

SET THECD=D&#58;

SET THEHD=C&#58;

;)
Wonko

#37 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 03:14 PM

Nice! :thumbup:

Basically the build process went from DVD's & ISO's to USB. The same batch files are involved but got changed a bit, not by me, but by our builds guy on the other side of the country.

So what your seeing was originally sat in a DVD. Was then ripped out and tweaked a little to use USB. The only thing I have done is change the path but here it is untouched from a work build stick. Basically what it does it check the computer name of the PC and then uses that info to lay down the appropriate ghost image (for a desktop or laptop or different model of either) after the appropriate ghost gets laid (you can see in the script L for a laptop D for desktop). After the ghost finished it then modifies the sysprep file with the correct machine name from the BIOS (obviously as when ghosted its a clone etc). Then it reboots hits sysprep with the correct name and joins domain, gets patched etc. So with this in mind I answer these.

The CD (COMPLETELY uneeded in such a scheme) WAS assigned letter X::
CODE
REM LH MSCDEX.EXE /D:cd0 /L:X
WHAT the heck is supposed to be letter D: ?
Please choose one:
The USB stick
The Internal hard disk
Something else

IT WAS THE DVD WOULD GET IT SINCE THIS IS STRIPPED FROM THE DVD'S WE USED TO USE etc.
I remember X got the dvd, but as for D: God knows. (<you sure LOL)

WHAT the heck is supposed to get letter C: ?

This:
CODE
DI1000DD.sys /DC
is to have the USB stick as C:

Then WHICH letter will get the HD?
This is true, I was just trying to see what would work but it ain't happening. Funny how its the same error I got at the start when I have my folder called 32L. I wonder if there is a folder or file name being created that is causing the same problem. Hmmm.

here is the error
Posted Image

Uploaded with ImageShack.us

@ECHO OFF
REM Deployment Procedure
REM
REM Set the image variable (so it's obvious)
REM Set Image=SR31
Set Image=SR32
REM Set Image=SR40
REM set Image=Flexi
REM
REM Get the Bios info in SMBIOS2.TXT on the local ram drive (Q:)
rem
dir q:\ > q:\dir.txt
C:\smbios2.exe /G > q:\smbios2.txt
REM
C:\sed -n -e "s/Product Name:/Set MBoard=/w q:\MBoard.Bat" q:\smbios2.txt
C:\sed -e "s/ '//g;s/'//g" q:\MBoard.bat > q:\prodname.bat
REM
C:\sed -n -e "s/Product:/Set MBoard1=/w q:\MBoard1.Bat" q:\smbios2.txt
C:\sed -e "s/ '//g;s/'//g" q:\MBoard1.bat > q:\prodcode.bat
REM
C:\sed -n -e "s/Asset Tag Number:/Set AssetTag=/w q:\Asset1.Bat" q:\smbios2.txt
C:\sed -e "s/ '//g;s/'//g" q:\Asset1.bat > q:\asset.bat
REM
REM Set the AssetTag environment variable
Call q:\Asset.Bat
REM
REM Set the MBoard environment variable
call q:\prodname.bat
Call q:\prodcode.Bat
REM
REM Validate the AssetTag as being Znnnnnnn where n is 0-9
ECHO Have determined machine as %mboard% , code [%mboard1%]
ECHO Have determined machine name as %AssetTag%
rem
pause
rem
C:\sed -e "s/AssetTag/AssetChr/" q:\Asset.Bat > q:\Asset1.Bat
C:\sed -e "s/Z1/zdOK/g" q:\Asset1.bat > q:\Asset2.Bat
C:\sed -e "s/z1/zdOK/g" q:\Asset2.bat > q:\Asset3.Bat
C:\sed -e "s/Z2/zlOK/g" q:\Asset3.bat > q:\Asset4.Bat
C:\sed -e "s/z2/zlOK/g" q:\Asset4.bat > q:\Asset5.Bat
C:\sed -e "s/[0-9]/nOK/g" q:\Asset5.Bat > q:\AssetChk.Bat
Call q:\AssetChk.Bat
If %AssetChr%==zdOKnOKnOKnOKnOKnOKnOK Goto :DoGhostD
If %AssetChr%==zlOKnOKnOKnOKnOKnOKnOK Goto :DoGhostL

ECHO.
ECHO Asset Tag retrieved from BIOS does not match Znnnnnnn where n=0-9
ECHO.
ECHO Asset Tag discovered is %AssetTag%
ECHO.
ECHO Change the Asset Tag in the BIOS and retry the installation
ECHO.
Pause
C:\reboot.com
EXIT
:DoGhostD
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
C:\ghost.exe -nousb -fni -clone,mode=load,src=C:\D%Image%.gho,dst=2 -sure
Goto :DISKINFO
:DoGhostL
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
C:\ghost.exe -nousb -fni -clone,mode=load,src=C:\L%Image%.gho,dst=2 -sure
Goto :DISKINFO

REM
:DISKINFO
REM
echo omnifs
REM Determine the hard drive volume number - Get disk info into text file
C:\OMNIFS -nousb INFO > q:\DSKINFO.TXT
REM
echo volinfo
REM Determine the hard drive volume number - Get volume info of NTFS drive into text file
C:\SED -n "s/NTFS/SFTN/w q:\VOLINFO.TXT" q:\DSKINFO.TXT
REM
echo volnum
REM Determine the hard drive volume number - remove everything after the " (" - that is space open-bracket
C:\SED -e "s/^[ ]*/Set Vol=/g;s/ (.*$//g" Q:\VOLINFO.TXT > Q:\VOL.BAT
REM
Call q:\VOL.BAT
ECHO Using %VOL% as volume number for hard-drive
REM
echo sysprep read
REM Get the sysprep.inf file from the image to the local ram drive (Q:)
C:\omnifs -nousb copy %VOL%\sysprep\sysprep.inf q:\sysprep.old
REM
echo set computer name
REM Substitute the AssetTag into the ComputerName sysprep entry (requires original sysprep.inf as sysprep.old)
C:\sed -e "s/ComputerName=.*$/ComputerName=%AssetTag%/g" q:\sysprep.old > q:\sysprep.inf
REM
echo update uphal check
REM Check for the n620 (0824) and the nc6000 (0890) and do the HALFix otherwise don't
If %Mboard1%==0824 Goto :HAL_Fix
If %Mboard1%==0890 Goto :HAL_Fix
Goto :NoHAL_Fix
REM
REM Comment out the UpdateUPHAL line for the n620 (0824) and the nc6000 (0890)
:HAL_Fix
C:\sed -e s/UpdateUPHAL/;UpdateUPHAL/ q:\sysprep.inf > q:\sysprep.new
:NoHAL_Fix
REM
echo replace modified sysprep
REM Copy the modified sysprep.inf back to the image
C:\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM
REM If there is a sysprep.new (with the commented out UpdateUPHAL) then overcopy it
if exist C:\sysprep.new C:\omnifs -nousb copy C:\sysprep.new %VOL%\sysprep\sysprep.inf
REM
:EXIT_POINT
REM
C:\reboot.com

#38 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 17 July 2010 - 04:39 PM

Ok, now I am completely lost.

You should start learning to use the board software, your posts are UNreadable. :thumbup:

Use the [ quote ] [ / quote ] tags (without spaces) to enclose something you DID NOT write or some code that you need to highlight with colours or font formatting.
Use the [ code ] [ /code ] tags (without spaces) to enclose somethig that is supposed to be CODE (ONLY if it's a few lines long).
Use the [ codebox ] [ /codebox ] tags (without spaces) to enclose something that is supposed to be CODE (ONLY if it's several lines long).

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
  • the code of the ORIGINAL cddeploy.bat BEFORE you modified it
  • the code of the ORIGINAL autoexec.bat BEFORE you modified it
  • the code of the ORIGINAL config.sys BEFORE you modified it
  • the code of any other ORIGINAL batch involved in the procedure BEFORE you modified it
  • a DIR listing of the ORIGINAL WORKING (albeit slowly) USB device (run DIR M: /S>N:\CDDIR.TXT - change drive letters according to your setup) NOT a lousy screenshot
In other words, I need to look at something that was surely WORKING before you started messing with it, this may (or may completely fail to) lead to giving you some good advice in how to fix the issue and PROPERLY change the batch to work with the ramdisk and USB drivers.

:thumbup:
Wonko

#39 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 17 July 2010 - 06:51 PM

Sorry fella. It has indeed turned into frantic "mess", let me bring this on down.........

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
the code of the ORIGINAL cddeploy.bat BEFORE you modified it


This is the CDDEPLOY.BAT code that worked on USB, before, ANY, usb 2.0 driver "injection" attempts.......
For your convenience, please accept the file in it's entirety (for any potential manipulation, if required) from here

Please check PM for PW for all file downloads

WONKOS CDDEPLOY

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
the code of the ORIGINAL autoexec.bat BEFORE you modified it


This is the AUTOEXEC.BAT code that worked on USB, before, ANY, usb 2.0 driver "injection" attempts.......
For your convenience, please accept the file in it's entirety (for any potential manipulation, if required) from here

WONKOS AUTOTEXEC

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
the code of the ORIGINAL config.sys BEFORE you modified it


This is the CONFIG.SYS code that worked on USB, before, ANY, usb 2.0 driver "injection" attempts.......
For your convenience, please accept the file in it's entirety (for any potential manipulation, if required) from here


WONKOS CONFIG

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
the code of any other ORIGINAL batch involved in the procedure BEFORE you modified it


&#34;NO other batches. Just a simple DOS set up with no extra batches, scripts etc other than what you have downloaded already WITHIN this thread&#34;

And I will try again I DO NOT CARE to learn the history of what you have been doing in the last few days, I already know it, in order to try and help you, I need to see:
a DIR listing of the ORIGINAL WORKING (albeit slowly) USB device (run DIR M: /S>N:\CDDIR.TXT - change drive letters according to your setup) NOT a lousy screenshot


(albeit slowly) I know the set up you are referring to as it was working until the end when the final problem arrived on the scene which has caused this.

WONKOS CDDIR.TXT

There is also a VFD in there which you may or may not want to look at but there it is in case you do.
That's what I start the build process up with using a simple G4D mapping command.

WONKOS VFD

In other words, I need to look at something that was surely WORKING before you started messing with it, this may (or may completely fail to) lead to giving you some good advice in how to fix the issue and PROPERLY change the batch to work with the ramdisk and USB drivers.


I have now done this to my best but remember when I was VERY excited about the WORKING it wasn't until the end of the build process that I realised it wasn't working (ref crappy screen shot)

Fingers crossed bro

#40 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 17 July 2010 - 10:06 PM

Ok, basically the batch does (possibly in a very complex way) a number of transformations from the output of smbios2.exe using SED.

BOTH utilities are inside the \LAPTOP\ directory on the stick according to the CDDIR.TXT, though the cddeploy.bat points to them in C:\32L\ :w00t" ( why do I have the feeling that the cddeploy.bat and the CDDIR.TXT do not match...:thumbup: )

Then it compares the result with something like an "asset Tag" mask, and if it matches "forks" between Laptop and Desktop, of it doesn't reboots the PC.

If Desktop:
c&#58;\32L\ghost.exe -nousb -fni -clone,mode=load,src=c&#58;\32L\D%Image%.gho,dst=2 -sure

If Laptop:
c&#58;\32L\ghost.exe -nousb -fni -clone,mode=load,src=c&#58;\32L\L%Image%.gho,dst=2 -sure

Since image name is hardcoded in the beginning of the file:
Set Image=SR32

The deployed image names are either DSR32 or LSR32.

Then OMNIFS is used to extract drive and volume info, and some other manipulation with SED is made in order to be able to edit a copy of syspep.inf from the RESTORED image (which in plain English should mean from the drive) writing to it the right "Asset Tag" and - if needed - ready it for a HAL patch.

Then it reboots the PC.

So, since the problem is here:

FAILED HERE WITH general read failure reading C:\
seems to have a problem with C: I tried adding DI1000DD.sys /DC to config.sys
but it hangs as soon as the C: is allocated in dos

D:\LAPTOP32L\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM
REM If there is a sysprep.new (with the commented out UpdateUPHAL) then overcopy it
if exist D:\LAPTOP32L\sysprep.new D:\LAPTOP32L\omnifs -nousb copy D:\LAPTOP32L\sysprep.new %VOL%\sysprep\sysprep.inf


Try (after making up your mind and decided WHICH path to use among LAPTOP, L32 or LAPTOP32L ) to amend like:

FAILED HERE WITH general read failure reading C:\
seems to have a problem with C: I tried adding DI1000DD.sys /DC to config.sys
but it hangs as soon as the C: is allocated in dos
ECHO Variable VOL is %VOL%
PAUSE

D:\LAPTOP32L\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM
REM If there is a sysprep.new (with the commented out UpdateUPHAL) then overcopy it
if exist D:\LAPTOP32L\sysprep.new D:\LAPTOP32L\omnifs -nousb copy D:\LAPTOP32L\sysprep.new %VOL%\sysprep\sysprep.inf


And post the results.

BEFORE that let's talk about drive letters.
Since you are booting from USB, the USB stick will be BOOT device (please read as "the USB stick will be (hd0) in grub4dos notation and the actual partition in it - primary and Active - will be (hd0,0) ) then with a menu.lst in which most probably you don't fiddle with hard disk order :cheers:, you chainload the 32L.vfd and boot DOS from it.
Thus the USB device remains the first hard disk (hd0) and the first active partition on it (hd0,1) becomes in DOS drive C:\ (the .vfd gets letter A:\) and the internal hard disk (if accessible at all from DOS) gets some other letter.
Then in the autoexec.bat XMSDSK creates a RAMDISK as Q:\.

So, in the original working:
  • The partition on the USB stick is C:\
  • The .vfd is A:\
  • The internal hard disk is <a suffusion of yellow> (at least until OMNIFS has made his trick).

So, if you use
DI1000DD.sys /DC
you try to force the USB stick to be assigned the SAME letter it already has.
and if you use
DI1000DD.sys
the driver will most probably get first available letter (possibly D:\) IN ADDITION to the C:\ it already has.

My guess is that in order to have the (whichever) driver working, you need to unmap the (hd0,1), or more probably the (hd0) as soon as you have loaded grub4dos.

I'll think a bit about a way to get rid of most (if not all) the overlays that have been unneededly added in the transformation from CD to USB stick using grub4dos. :thumbup:


:cheers:
Wonko

#41 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 18 July 2010 - 07:59 AM

Morning!

Set up the extra line and ran the test, and this is the result. (I'll spare you and any other readers a crappy screenshot).
1. Code change to CDDEPLOY

echo replace modified sysprep
REM Copy the modified sysprep.inf back to the image
ECHO Variable VOL is %VOL%
PAUSE
D:\LAPTOP\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM
REM If there is a sysprep.new (with the commented out UpdateUPHAL) then overcopy it
if exist D:\LAPTOP\sysprep.new D:\LAPTOP\omnifs -nousb copy D:\LAPTOP\sysprep.new %VOL%\sysprep\sysprep.inf



2. RESULTS
onmifs

volinfo

volnum

using 2.1&#58; as volume number for hard-drive

sysprep read

set computer name

update hal check

replace modified sysprep

Variable VOL is 2.1&#58;

press any key to continue...

and of course pressing the "ANY" key incurs (as we know)

General failure reading drive C
abort, retry, fail?

I see about the drive letter now, my main area of confusion was whether or not DOS would see the USB-HDD as C: automatically, or whether it would only become C: unless something told it to be. Especially with all the different things going on here that label disks in a different way; DOS A,C,D: G4D (hd0) (hd0,0) & Ghost 1,2,3 etc or 2:1, 2:2. And of course this new panasonic USAPSI.SYS and how it saw all these things presented to it. Thanks for making it clearer.

Hope the result helps, will check back in an hour or 2,.. :thumbup:

#42 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 18 July 2010 - 08:56 AM

Good, now there should be no reason why accessing "drive 2.1" should result in:

General failure reading drive C
abort, retry, fail?


:cheers:

What if the problem is actually running OMNIFS itself?

What happens with:

echo replace modified sysprep
REM Copy the modified sysprep.inf back to the image
ECHO Variable VOL is %VOL%
PAUSE
Dir D:
PAUSE
DIR C:
PAUSE
D:\LAPTOP\omnifs /?
PAUSE

D:\LAPTOP\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM


About the overlays, it seems to me like there is an unneeded use of files scattered on a number of devices:
  • the floppy image
  • the USB stick
  • the XMSDSK ramdisk
I would take an approach where ANYTHING but the actual GHOST image fit in the virtual floppy image, i.e. something like:
08/06/2000  05:00            17.175 DISPLAY.SYS31/05/1994  07:22             5.861 DOSKEY.COM31/05/1994  07:22            66.294 DRVSPACE.BIN23/04/1999  10:22           125.495 EMM386.EXE12/08/1998  01:09            19.472 emsdsk.exe16/01/2003  10:12            64.425 flashpt.sys06/02/2007  11:38             3.878 gcdrom.sys27/04/2010  02:50               347 GHOSTERR.TXT23/04/1999  09:22            33.191 HIMEM.SYS15/05/2001  06:57           116.736 IO.SYS08/06/2000  05:00            21.607 KEYB.COM08/06/2000  05:00            34.566 KEYBOARD.SYS31/05/1994  07:22            32.502 MEM.EXE08/06/2000  05:00            29.239 MODE.COM16/01/2003  10:12            37.681 MOUSE.COM23/01/2007  11:01                24 MOUSE.INI01/05/1990  04:00            31.701 MOUSE.SYS16/01/2003  10:12            21.180 mscdex.exe07/04/2001  01:40                 9 MSDOS.SYS16/01/2003  10:12            41.302 oakcdrom.sys31/05/1994  07:22           124.262 SCANDISK.EXE31/05/1994  07:22             9.432 SYS.COM12/08/1998  01:09            20.016 XMSDSK.EXE31/05/1994  07:22            12.241 CHKDSK.EXE08/06/2000  05:00            93.040 COMMAND.COM17/07/2010  12:20               152 CONFIG.SYS20/05/2010  09:00                 0 BOOTLOG.PRV16/01/2003  10:12            30.955 btdosm.sys21/04/2010  06:57            10.672 BOOTEX.LOG17/07/2010  12:21                83 AUTOEXEC.BAT07/11/2004  05:20            39.179 USBASPI.SYS16/08/2001  02:00            16.368 DI1000DD.SYS17/07/2010  12:03            22.080 RAMFD.SYS27/03/2008  02:06            52.106 ASPIEHCI.SYS17/07/2010  12:24             4,117 CDDEPLOY.BAT26/08/2004  15:25           469,184 gdisk.exe25/10/2005  10:35         1,397,900 Ghost.Exe19/04/2007  20:43         1,334,348 omnifs.exe20/10/2000  16:20                32 REBOOT.COM01/10/1991  10:58            22,104 SED.EXE07/09/2001  21:07           203,840 smbios2.exe12/03/1995  18:57               192 EDIT.INI
as it would be far easier to mantain and one would get rid of most if not all possible drive letter/path problems.
BTW, the .vfd contains any number of files that are either unneeded or unused, and that could be removed without any adverse effect, particularly since everything is batch driven, waht is the use of Mouse support?

The flashpt and btdosm appear like SCSI drivers from BUSLOGIC:

FLASHPT COPYRIGHT© 94-95 BUSLOGIC <J.F.Z>
FLASHPT MGR 1.xxBusLogic BL-93x
BUSLOGIC BT-930
BTDOSM COPYRIGHT© 93, 94 BUSLOGIC <J.F.Z>
0x45 0x20 BL ASPI MGR 4.30BusLogic

if you don't have (anymore) machines that use that interface, they can also be removed for good.

:thumbup:
Wonko

#43 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 18 July 2010 - 10:22 AM

Hi...

What happens with:
QUOTE
echo replace modified sysprep
REM Copy the modified sysprep.inf back to the image
ECHO Variable VOL is %VOL%
PAUSE
Dir D:
PAUSE
DIR C:
PAUSE
D:\LAPTOP\omnifs /?
PAUSE
D:\LAPTOP\omnifs -nousb copy q:\sysprep.inf %VOL%\sysprep\sysprep.inf
REM


Have just set that going so will report back.....


I would take an approach where ANYTHING but the actual GHOST image fit in the virtual floppy image, i.e. something like:


Now that is a wicked idea. :thumbup:
If "we" ( :cheers: you really) can get this primary issue sorted I will be doing that.
Actually I might have to anyway to get rid of any drive letter issues if nothing comes from the above test like you say.
Just so we stay on track and I don't wreaking havoc in the thread again (veering of course with new issues etc.) you dont mind if I put that on hold till after the above test; unless required of course?

Quick pre thoughts on this though are as follows.

1. Create a large® floppy image to accommodate the extra files.
2. Default paths in CDDEPLOY.BAT to A:\.

>>>>>>>>>>>>>>>>APART from the ghost files locations which should remain in their own folders<<<<<<<<<<<<
example
REM

REM Load the Ghost image &#40;Note&#58; Ghost.exe is delivered by the OS Software worksheet&#41;

A&#58;\ghost.exe -nousb -fni -clone,mode=load,src=D&#58;\DESKTOP\D%Image%.gho,dst=2 -sure

Goto &#58;DISKINFO

&#58;DoGhostL

REM

REM Load the Ghost image &#40;Note&#58; Ghost.exe is delivered by the OS Software worksheet&#41;

A&#58;\ghost.exe -nousb -fni -clone,mode=load,src=D&#58;\LAPTOP\L%Image%.gho,dst=2 -sure

Goto &#58;DISKINFO

REM

Anything I missed?

(I already trimmed down some crap from the floppy mouse, those to archaic .sys files)

#44 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 18 July 2010 - 10:39 AM

2. Default paths in CDDEPLOY.BAT to A:\.


Or, even remove paths :cheers:.
Like:

A:
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
ghost.exe -nousb -fni -clone,mode=load,src=D:\DESKTOP\D%Image%.gho,dst=2 -sure
Goto :DISKINFO
:DoGhostL
REM
REM Load the Ghost image (Note: Ghost.exe is delivered by the OS Software worksheet)
ghost.exe -nousb -fni -clone,mode=load,src=D:\LAPTOP\L%Image%.gho,dst=2 -sure
Goto :DISKINFO
REM


JFYI, about the use of REM in batch files:
http://www.chebucto....S/Bat-Tips.html

Use Double Colons for Comments. To prevent comments from resulting in error messages, use a double colon ( :: ) before each line containing any remarks. The "REM" command may be used instead, but DOS will read the entire line and actually perform some things such as redirection and piping. That could cause problems under certain circumstances, so employing the double colon is a better method.

When DOS comes across a double colon, it ignores everything from the second colon onward because this second colon is an illegal label character. (The single colon is used as a label precursor in batch files.) DOS immediately skips to the next line after reading a double colon. I also place a space after the double colon. This gives an extra degree of readability when perusing a lengthy batch file. (See Batch Basics for how this method is used. You may also be interested in the lesson on DOS Characters.)


:thumbup:
Wonko

#45 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 18 July 2010 - 10:55 AM

Yess, even better, :thumbup:

Just realised now with that method can have one big .VFD and 1 folder called IMAGES with Lghost(laptops) & Dghost(desktops) and that's it.
Cant wait to get that nailed will be soooo streamlined and uncluttered. Oh man sooo good!
While results in prog, just one more thought in the past I have used easyboot to create big images which worked well on my bios update project for the machines but will it suffice with this as that RAMFD.SYS (which had to be included to get USBASPI.SYS & DI1000DD.SYS to work) seems to set up some kind of ram disk of its own, it might freak out when it finds a super floppy image in the mix? Should be in the copy of my vfd you downloaded if need to see it in action.

Back in a bit.... :cheers:

#46 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 18 July 2010 - 12:28 PM

A 5760 Kb floppy image should do:
http://bootcd.narod.ru/images_e.htm
http://bootcd.narod.ru/fd005760.zip

What I would do if I were you, would be to put aside for the moment the cddeploy.bat and check if something like this works (after having copied to it the files, BUT NOT cddeploy.bat AND adding CTLOAD) - you can also quickly try this approach with your current .vfd, of course you won't be able to test the OMNIFS behaviour:

title fd005760.ima
find --set-root /fd005760.ima
map --mem /fd005760.ima (fd0)
map --hook
root (fd0)
chainloader /io.sys

the above should allow to access the USB stick as C:

title fd005760.ima unmap HD
find --set-root /fd005760.ima
map --mem /fd005760.ima (fd0)
map --hook
root (fd0)
chainloader /io.sys
map --unmap=0x80

or:

title fd005760.ima unmap HD
find --set-root /fd005760.ima
map --mem /fd005760.ima (fd0)
map --hook
root (fd0)
chainloader /io.sys
map --unmap=0x80
map --rehook

this should make the USB stick UNaccessible by DOS. :cheers:
At this point you try running on command line:
ctload aspiehci.sys /all /int

ctload di1000dd.sys /DC

or:
ctload usbaspi.sys /v

ctload di1000dd.sys /DC

And see what happens, if everything is as I am guessing, the USB stick should be mapped and accessible as C:

:thumbup:
Wonko

#47 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 18 July 2010 - 05:14 PM

Awesome, got that downloaded just now! and will try all requested and let you know what happens.

###UPDATE###
the second test you asked me to do this morning......failed on DIR C: :cheers:

#CODE SUMMARY#
echo replace modified sysprep

REM Copy the modified sysprep.inf back to the image

ECHO Variable VOL is %VOL%

PAUSE

Dir D&#58;

PAUSE

DIR C&#58;

PAUSE

D&#58;\LAPTOP\omnifs /?

PAUSE

D&#58;\LAPTOP\omnifs -nousb copy q&#58;\sysprep.inf %VOL%\sysprep\sysprep.inf

REM

Posted Image

Uploaded with ImageShack.us

#48 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 18 July 2010 - 06:59 PM

Ok here's the latest action :cheers:

First off I made the super floppy as instructed using the files we have been using to get as far as trying to figure out the omnifs issue.
I include it for examination if required. :cheers:

title fd005760.ima

find --set-root /fd005760.ima

map --mem /fd005760.ima &#40;fd0&#41;

map --hook

root &#40;fd0&#41;

chainloader /io.sys

the above should allow to access the USB stick as C:


WORKING
Left out the autoexec for now and just let it go to A:\ from there C:\ from there DIR, (which showed folders & files on USB Disk) from there could access any folders and even attempted to run something and it did so with out any general read error's. So that was as you expected.

title fd005760.ima unmap HD

find --set-root /fd005760.ima

map --mem /fd005760.ima &#40;fd0&#41;

map --hook

root &#40;fd0&#41;

chainloader /io.sys

map --unmap=0x80

this should make the USB stick UNaccessible by DOS


NOT WORKING
1. C: took me to USB, DIR listed all the files and folders there, and could attempt to start files etc.
2. CTLOAD gave me UNKNOWN VERSION OF DOS! error.

So I went back to the "HOW TO USB-DOS" where I saw this file before and copied the core win98se boot files from there and over wrote the ones in my new SUPERFLOPPY so it was using the DOS files it was used to.

3. CTLOAD ASPIEHCI.SYS. NO DEVICE FOUND
4. CTLOAD USBASPI.SYS /V loaded OK.
5. CTLOAD DI1000DD.SYS /DC set the USB as C: but immedialtley complained "driver initialisation failed".

title fd005760.ima unmap HD

find --set-root /fd005760.ima

map --mem /fd005760.ima &#40;fd0&#41;

map --hook

root &#40;fd0&#41;

chainloader /io.sys

map --unmap=0x80

map --rehook

this should make the USB stick UNaccessible by DOS


ALSO NOT WORKING :cheers:
1. C: took me to USB, DIR listed all the files and folders there, and could attempt to start files etc.
2. In light of above can't USE ASPIEHCI.SYS (in current test set up at least)
3. CTLOAD USBASPI.SYS /V. Loaded OK
4. CTLOAD DI1000DD.SYS /DC. Set the USB as C: but immedialtley complained "driver initialisation failed".

EDIT
DI1000DD.SYS /DD will allow USB mapped as D with no error I guess because no C drive clashing, but here's the rub.
When I just did D:\DIR says "file not found" and cant list any files or folders. Seems this driver is behaving in a very strange way.

copies of files used

MENU.LST AND SUPERFLOPPY

#49 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 19 July 2010 - 08:49 AM

Hmm. :cheers: it's possible that I completely failed to understand the usage of the map --unmap command. :cheers:

Apart from the not-so-slight-detail above, maybe the problem is due to the fact that BIOS (and DOS) sees the USB stick as first drive. :merc:

Try a few commands in grub4dos (press c to get to command line).

find --set-root /fd005760.ima

map --mem /fd005760.ima &#40;fd0&#41;

map --hook

root &#40;fd0&#41;

chainloader /io.sys

then:
map &#40;hd0&#41; &#40;hd1&#41;

map &#40;hd1&#41; &#40;hd0&#41;

map --hook

boot

Now drives should be exchanged.

What happens now in DOS?
Which drive letter gets the USB stick?
What happens with:
CTLOAD USBASPI.SYS /V

CTLOAD DI1000DD.SYS

What happens (re-booting) if you try using a new instance of command.com? In DOS:
copy /b command.com Q&#58;

copy /b ctload.com Q&#58;

copy /b usbaspy.sys Q&#58;

copy /b di1000dd.sys Q&#58;

Q&#58;

command.com

CTLOAD USBASPI.SYS /V

CTLOAD DI1000DD.SYS

:dubbio:
Wonko

#50 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 19 July 2010 - 10:09 AM

OK will test this later today......

FYI UPDATE ON CDDEPLOY TIDY (NOUSB)
Superfloppy with all files and just the images in a folder, working a treat, sat here now @ work and built with no hassles. V. Tidy.

Set A: at the start of cd deploy and point ghost images path to C:\IMAGES
when USB is working :dubbio: (just need to copy the superfloppy and make the appropriate changes) then update MENU
gonna be brillaint!
1. Build 3.2 (NOUSB)
2. Build 3.2 (USB ENABLED)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users