Jump to content











Photo
- - - - -

Speed UP USB ghost image transfer in Dos


  • Please log in to reply
64 replies to this topic

#1 Technotika

Technotika

    Frequent Member

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

Posted 14 July 2010 - 10:25 AM

Hi Guys,

I have a project where by I have "all" of my works system images loading of USB.
Been great and works nicely for the most part but now we have been using it a bit we are in agreement that on the majority of the older machines (and some newer) the ghost image transfer is
SLOWER than DVD which is a real shame as that it what it was intended to replace.

On a decent system 900/1000 mb per minute (thats what we like!) 4/5 mins per build etc. :thumbup:
On many can just be 40/40 mb per minute (that's what we don't like)...basically it's time to shave again by the end of that painful transfer!!! :thumbup:

Now I have been looking into this and seen quite a lot of different approaches, but am a bit stuck when it comes to incoperating something into our system. I expect I need to load some sort of driver into config.sys and autoexec.bat, but which one (best compatability etc) and also HOW? I will need a bit of hand holding on this as am not too hot at DOS.

HISTORY
I have tried PLOP. Plop is ace! Where I have needed to speed up the loading of a RAM image or the loading of a VISTA PE. Plop just handles that nicely...really speeds things up, even on the older systems. However when it comes to ghost images, ghost no longer see's the USB stick for some reason (due to the plop controller) and just cannot load an image. I have posted in plop forum and the guy who wrote plop wasnt too sure about this and also I posted in symantec aswell about this and no body has answered yet.
So is the mission to get some kind of USB driver built into the dos start up disk for the ghost images.

THE IMAGE PROCESS
The image system loads a win98 DOS boot disk tweaked to then start ghost loading from usb under the instruction of a Batch file that gets computer name info from the mainboard then modifies a sysprep file in the ram drive Q, then updates it AFTER the ghost image has loaded. I know, there must be an easier way.

here is the config sys entry

#config.sys#
DEVICE=himem.sys /testmem:off /v
DEVICE=btdosm.sys
DEVICE=flashpt.sys
LASTDRIVE = Z

#autoexec.bat#
MOUSE.COM
REM LH MSCDEX.EXE /D:cd0 /L:X
XMSDSK 2048 Q: /y
C:\32L\cddeploy (<<<<that is the script that does all the sysprep swapping and bios/mainboard interogating)

QUESTIONS
What (and if there is one) is the simplest way to get faster USB transfer speeds looking at this situation. I have tried a few things off the net like USBASPI.SYS, however so many versions floating around I couldnt get it to work and wasnt sure how to integrate in this situation, other examples were using standard floppy's and things.

I just know some one here will have done this already and was hoping they could lend their experiences to this new situation I'm in.

If you need any extra info just let me know. If can get this working, would so immense.
Thanks chaps!

#2 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 14 July 2010 - 11:26 AM

Perhaps the problem is not with USB driver, but with the lacking of UDMA driver for hard disk.

#3 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 14 July 2010 - 11:56 AM

Seek and you shall find....
http://www.boot-land...?...c=4260&st=0

There are as many versions of GHOST as stars in the sky, you will need to be more explicit, but - rather obviously - the drivers that ship with it should be the "best" available.

BTW, and AFAIK, Symantec GHOST DOS versions use IBM PC-DOS and NOT MS-DOS.

There are NO such things as "decent" and "many".
There are systems with USB 2.0 controllers and systems with USB 1.1 ones.
The former will be fastish, the latter will ALWAYS be slowish.

Of course if you add to it a "wrong" driver things may worsen, but I don't think that there is an easy "one-size-fits-all" solution.

You can try getting this floppy:
http://johnson.tmfc.net/dos/index.html
http://johnson.tmfc....dos/usbdrv.html

and start your own experiments.

There is a "dedicated" board to GHOST, here:
http://radified.com/...n/yabb2/YaBB.pl?
where you may find more accurate and specific advice.

:thumbup:
Wonko

#4 Technotika

Technotika

    Frequent Member

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

Posted 14 July 2010 - 02:07 PM

:(

Righty ho, here's what happened already

I am reading this first, from the links supplied - < thanks!

http://www.computing...isys/13288.html

this is the first thing I tried.............

Recommended Usage:

> To detect your USB Mass storage device (.e.g. a USB 2.0 external hard drive) put this line in your boot diskette CONFIG.SYS file

device=USBASPI.SYS /w /v

.............AAAAAAAAnd, close, but no nicorette inhaler; "TARGET USB DEVICE NOT DETECTED"

the second thing I tried.............

> If you want to enable only the high-speed USB controller and external hard disk drives, try

device=USBASPI.SYS /w /e
device=DI1000DD.SYS

"TARGET USB DEVICE NOT DETECTED"

Before I go any further is fat32 on a 16gb thumbstick good for this?
I tried on someones 8gb to no avail also?

Jeez :thumbup:

#5 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 14 July 2010 - 06:15 PM

I am reading this first, from the links supplied - < thanks!

http://www.computing...isys/13288.html

this is the first thing I tried.............


What you may have missed that in the given thread the "first link" that you attempted using is reported as something that DID NOT work for the OP (and a working solution was later found). :cheers:

Before I go any further is fat32 on a 16gb thumbstick good for this?
I tried on someones 8gb to no avail also?

It's not a FAT32 problem (as long as the partition type is 0C and not 0B), but it is common that the board BIOS provides NOT a proper INT13 extension on the USB bus, and thus anything above 8 Gb will result in a "suffusion of yellow".
Some older motherboards do have a 512 Mb limit, too.

The good news is that under DOS the "removable/fixed" bit is ignored, and you can then have more that one partition on the USB stick easily.

A good idea is to do the experiments with a small partition on the stick, a 100 Mb one and FAT16 is more than enough, and only once everything has proven to be working, try to "pass" the 512 Mb and the 8 Gb boundaries.

Reference for the boundaries:
http://www.pcguide.c...d/bios/size.htm

However what you reported sounds a lot more like a "wrong" (or wrongly loaded) driver.


"Baby steps, learn to walk before attempting running" :thumbup:

:cheers:
Wonko

#6 Technotika

Technotika

    Frequent Member

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

Posted 14 July 2010 - 10:31 PM

Ok well read some of the post (responses) in question and also "radified" and am a little closer, BUT a new problem has happened. So maybe further away :thumbup:

In "radified" many were told to use the PANANSONIC USBASPI.SYS V2.20 as it had better results.

I had to try.

For the first time my USB stick got loaded/detected BUT then seems to throw the rest of the dos boot process into turmoil!?

Take a look at the SDUMP below.........

If I REM the DI1000DD.SYS out the error in config.sys error disappears but still command.com error.

I thought perhaps grub4d might have been involved in causing probs as I map from a floppy.vfd with the boot info.

So to disprove or prove I just made a pure dos boot disk USB with an old 2gb I have lieing around.
Resulrt: no g4d and still the same.

I also tried forcing a drive letter to the new USB drive with a switch on device=di1000dd.sys /d >>"here"<< a: c:. Same
Seems as soon as the USBASPI.SYS kicks in all dos booting cant be carried on.

I also did a step by step DOS boot process by hitting F8, and loaded everything one by one.
The USBASPI.SYS does its, finds a Device and then it asks to load DEVICE=DI1000DD.SYS YES/NO..as soon as I hit YES =BOOM!= the error above (error in config.sys etc)

NOW I'm stuck? Any tips peeps (fingers x'd)

Posted Image

Uploaded with ImageShack.us

#7 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 14 July 2010 - 11:14 PM

Let's start from the beginning, OK? :thumbup:

FORGET anything else and just try the suggested floppy:
http://johnson.tmfc.net/dos/index.html
http://johnson.tmfc....dos/usbdrv.html

Try it WITHOUT changing ANYTHING in it.

It will give you several options, see if you can find one that it is working for you. :cheers:

Post which one (if any :cheers:) it is.

BTW you do understand that from what you posted you have an error in line 5 of your current config.sys related to the fact that DI1000DD.SYS is corrupted or missing, but you did not post your whole CONFIG.SYS, nor a DIR /S of your floppy, so there is no way to even GUESS what's happening, don't you? :cheers:

As well there are almost as many version of the Panasonic driver as stars in the sky (still less than GHOST versions, though :cheers:), please try the said floppy and report, so we will know EXACTLY which files you are using and with which config.sys settings.

Then FORGET anything of the above and just read the whole first post of the already given thread:
http://www.boot-land...?showtopic=4260
Download the file "howto_updated.zip" attached to it:
http://www.boot-land...?...ost&id=4860

Open it, read it's readme.txt and do EXACTLY what's in there.

Report what happens.

:thumbup:
Wonko

#8 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 08:42 AM

Let's start from the beginning, OK? smile.gif

FORGET anything else and just try the suggested floppy:
http://johnson.tmfc.net/dos/index.html
http://johnson.tmfc....dos/usbdrv.html

Try it WITHOUT changing ANYTHING in it.

It will give you several options, see if you can find one that it is working for you. unsure.gif

Post which one (if any scared9.gif) it is.
###########################################################################
Hi there WONKO
Yep, lets get on the same bus as it were. Ok, here is what happened with part 1 (as above)

[First be warned of this booting scenario. Right now at work and have left spare "DOSSING" ( :cheers: )about USB key at home so cant create a proper DOS usb booter. I have set up a VFD (32L.VFD) and installed the http://johnson.tmfc....dos/usbdrv.html (installer.exe) to the VFD and used that on my works project stick from G4D]

[I.E map /ISO/32L.vfd (fd0)
map --hook
root (fd0)
chainloader /io.sys
boot]

As long as that's ok for this???? here's what happened

1.XMGR +UMBPCI
[cannot open cd driver SHCDX33E cannot load] :thumbup:
2.XMGR +JEMM386
[cannot open cd driver SHCDX33E cannot load] :cheers:
3.JEMMEX
[cannot open cd driver SHCDX33E cannot load] :cheers:
4.NO ULTRA DMA (No CD)
[cannot open cd driver SHCDX33E cannot load] :cheers:
5.CLEAN :thumbup:
"appears to have worked; got to A:\> but previous mentioned No EDD BIOS logic. Unit 80h & 81h ignored"

#9 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 11:35 AM

Have now also tried "how to updated" and this is what happened

firstly.......

here are my USB dir and COPY2RAM dir

USB root
Volume in drive F is RSUBM
Volume Serial Number is 6AB5-46E9

Directory of F:\

23/04/1999 22:22 33,191 HIMEM.SYS
15/07/2010 11:17 <DIR> COPY2RAM
12/08/1998 01:09 20,016 xmsdsk.exe
30/03/2008 21:14 18 config.sys
15/07/2010 11:33 71 AUTOEXEC.BAT
15/07/2010 12:04 0 log.txt
5 File(s) 53,296 bytes
1 Dir(s) 1,010,024,448 bytes free
also command.com, io.sys & msdos.sys

COPY2RAM
Directory of F:\COPY2RAM

..
16/08/2001 02:00 16,368 DI1000DD.SYS
ASPIEHCI.SYS
command.com
ctload.com
DI1000DD.SYS
load.bat
ntfs4dos.exe


I followed the guide to the "t"
the only thing I had issue with was NTFS4DOS.exe. If I extracted and copied as asked, no NTFS4DOS.EXE present only when I installed the ANTIVIR package and created floppy. I only copied the NTFS4DOS.EXE though?

RESULTS TIME
cant do screen shots at work (proxy)

c: copy toram

r:command.com
bad command or file name

r:ctload aspiehci.sys /all /int

IOMEGA BLAH BLAH

no devices found
driver init' failed

r: ct load di1000dd.sys
ASPI DISK DRIVER Ver2.00
NOVAC BLAH

ASPI Manager not installed
driver init failed

:thumbup:

#10 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 15 July 2010 - 11:41 AM

I am missing something.

The disk (at least the usb19.zip, which contains a RAW image that you can use with grub4dos mapping) that you should have downloaded has this in config.sys:
MENU   +-----------------------------------+

MENU   | Motto Hairu &#40; Panasonic / Novac &#41; |

MENU   +-----------------------------------+

MENU	1 - HIMEM + EMM386

MENU	2 - XMGR + UMBPCI &#40;default&#41;

MENU	3 - XMGR + JEMM386

MENU

MENU   +------------------+

MENU   | DUSE &#40; Cypress &#41; |

MENU   +------------------+

MENU	4 - HIMEM + EMM386

MENU	5 - XMGR + UMBPCI &#40;Recommended&#41;

MENU	6 - XMGR + JEMM386

MENU

MENU   +----------------------+

MENU   | ASPI xHCI &#40; Iomega &#41; |

MENU   +----------------------+

MENU	7 - HIMEM + EMM386

MENU	8 - XMGR + UMBPCI &#40;Recommended&#41;

MENU	9 - XMGR + JEMM386

So you should try 9 items and report about 9 items numbered as above.

Try changing this in autoexec.bat:

:loadcdex
echo ------------------------------------------------------------------------
shcdx33e /d:usbcd001 /r-
echo ------------------------------------------------------------------------

to:

:loadcdex
echo ------------------------------------------------------------------------
A:\DOS\shcdx33e /d:usbcd001 /r-
echo ------------------------------------------------------------------------

probably a glitch in the matrix :cheers:

:thumbup:
Wonko

#11 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 12:01 PM

Ok I'll cracking on this one !

#12 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 12:19 PM

ok got the raw image, I havent booted a BIN file before with G4D.

Tried to convert to an iso but it wont let me I gather I can boot this RAW file but not sure how, what do I change in the below? ta :thumbup:
title USB DOS TESTING
find --set-root /ISO/usb19.bin
map /ISO/usb19.bin (0xff)
map --hook
root (0xff)
chainloader (oxff)

#13 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 15 July 2010 - 12:42 PM

Ow, come on :thumbup:, it's a floppy image 1474560 bytes in size.

title USB DOS TESTING

find --set-root /ISO/usb19.bin

map /ISO/usb19.bin &#40;fd0&#41;

map --hook

root &#40;fd0&#41;

chainloader +1

:cheers:
Wonko

#14 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 12:45 PM

Ohhhhhh right - I see I see - Sorry fella - I'll get right on it!!!! :thumbup:

#15 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 01:10 PM

Ok looks like 3 are goodies!!! check it :cheers:


MENU +-----------------------------------+
MENU | Motto Hairu ( Panasonic / Novac ) |
MENU +-----------------------------------+
MENU 1 - HIMEM + EMM386 >>> "INSTALLED ASPI MANAGER :DRIVER LOADED"
MENU 2 - XMGR + UMBPCI (default) >>> "INSTALLED ASPI MANAGER :DRIVER LOADED"
MENU 3 - XMGR + JEMM386 >>> "INSTALLED ASPI MANAGER :DRIVER LOADED"
MENU
MENU +------------------+
MENU | DUSE ( Cypress ) |
MENU +------------------+
MENU 4 - HIMEM + EMM386 >>> "HANGS @ EMM386.26"
MENU 5 - XMGR + UMBPCI (Recommended) >>> "INVALID OPCODE"
MENU 6 - XMGR + JEMM386 >>> "JEMM386 EXECPTION tons 'o' numbers"
MENU
MENU +----------------------+
MENU | ASPI xHCI ( Iomega ) |
MENU +----------------------+
MENU 7 - HIMEM + EMM386 >>> "ADAPTOR NOT PRESENT"
MENU 8 - XMGR + UMBPCI (Recommended) >>> "NO DEVICES PRESENT"
MENU 9 - XMGR + JEMM386 >>> "ADAPTOR NOT PRESENT"

Ok so I guess now its a case of "medling" working option/s above with current dos boot set for project? :cheers: Cant wait! :thumbup:

#16 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 05:39 PM

I'm looking between the work DOS and the NEW USB DOS and I think (danger danger!) the new USB DOS takes care of the booting side of things (did need to make sure there was a xmsdsk.exe; needed in work dos), I think I need to add some lines to the autoexec to get it to launch the build process!

here is current work DOS autoexec with no USB driver
Posted Image

Uploaded with ImageShack.us

Here is the autoexec from working USB DOS
@echo off

path=\freedos;\dos;

if "%config%"=="1" goto USBASPI
if "%config%"=="2" goto USBASPI
if "%config%"=="3" goto USBASPI

if "%config%"=="4" goto DUSE
if "%config%"=="5" goto DUSE
if "%config%"=="6" goto DUSE

if "%config%"=="7" goto ASPIHCI
if "%config%"=="8" goto ASPIHCI
if "%config%"=="9" goto ASPIHCI


:DUSE
DEVLOAD \USB-DRV\DUSE49.EXE VER DMA EMU
DEVLOAD \USB-DRV\DUSE44.EXE VER DMA EMU
DEVLOAD \USB-DRV\DUSE42.EXE VER DMA EMU
goto loadcdex


:USBASPI
rem without switch, USBASPI automatically attempts all versions of USB
echo.
echo Load Panasonic v2.20 - USB to ASPI converter?
?devload USB-DRV\USBASPI3.SYS /V
if exist SCSIMGR$ goto ASPIDISK
echo.


from what I gather the above (the default, and also OPTION 2 from the menu) indicates that this is the driver that worked, loaded, installed ASPI manager and then sat at A :\>

Now how do I get it to load these instead of sitting at A:\>

XMSDSK 2048 Q: /y
C:\32L\cddeploy


echo Load Panasonic v2.15 - USB to ASPI converter?
?devload USB-DRV\USBASPI2.SYS /V
if exist SCSIMGR$ goto ASPIDISK
echo.
echo Load Panasonic v2.06 - USB to ASPI converter?
?devload USB-DRV\USBASPI1.SYS /V
if exist SCSIMGR$ goto ASPIDISK
echo.
echo Load Panasonic v1.07 - USB to ASPI converter?
?devload USB-DRV\USBASPI0.SYS /V
if exist SCSIMGR$ goto ASPIDISK
goto loadcdex

:ASPIHCI
rem IOMEGA USB to ASPI converters. Drivers are not smart enough to autodetect USB type.
echo.
echo Load IOMEGA USB 2.0 - USB to ASPI converter?
?devload USB-DRV\aspiehci.sys /R /V
if exist SCSIMGR$ goto ASPIDISK
echo.
echo Load IOMEGA newer USB 1.x - USB to ASPI converter?
?devload USB-DRV\aspiohci.sys /R /V
if exist SCSIMGR$ goto ASPIDISK
echo.
echo Load IOMEGA older USB 1.x - USB to ASPI converter?
?devload USB-DRV\aspiuhci.sys /R /V
if exist SCSIMGR$ goto ASPIDISK
goto loadcdex

:ASPIDISK
echo.
echo Load Panasonic ASPI Mass Storage Driver (USB Flash Drive / USB External HD)?
?DEVLOAD A:\USB-DRV\di1000dd.sys
echo.
echo Load Workbit Corp. ASPI USB CD Driver?
?DEVLOAD A:\USB-DRV\NJUSBCDA.SYS /D:USBCD001
if exist USBCD001 goto loadcdex
echo.
echo Load Panasonic ASPI USB CD Driver?
?DEVLOAD A:\USB-DRV\USBCD.SYS /D:USBCD001
if exist USBCD001 goto loadcdex
goto noloadcdex

:loadcdex
echo ------------------------------------------------------------------------
A:\DOS\shcdx33e /d:usbcd001 /r-
echo ------------------------------------------------------------------------

:noloadcdex
ctmouse /y

#17 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 15 July 2010 - 07:28 PM

The floppy uses FreeDOS.
You are using MS DOS.
Autoexec.bat and config.sys (ex fdconfig.sys) need to be modified.
Now it's time to check again the "how-to updated, that was designed with MS DOS in mind.

:thumbup:
Wonko

#18 Technotika

Technotika

    Frequent Member

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

Posted 15 July 2010 - 08:20 PM

Ok I'm gonna smash this tomorrow got some ideas already. Will sleep on it and come back Tomorrow.
C u in a bit ! :-)

#19 Technotika

Technotika

    Frequent Member

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

Posted 16 July 2010 - 07:07 AM

Morning! :cheers:

hmm before modding these I still can't get a successful run on the "how to" USB-DOS
triple checked it bro, I swear, the only confusing thing (for me) is the ntfs4dos driver bit....

and I quote "extract and copy the ntfs software to the same locaion (COPY2RAM)"
If I do that with 7 zip the ntfs4dos.exe doesnt appear. I just get guff and tripe.

Only when I install the avira packag and install the floppy to a VFD do I finally see this exe.
So query is do I need all the files from the nfts4dos floppy copying to the COPY2RAM folder or just the ntfs4dos.exe?? Here's my kit right now >>>>>>>>>>

ROOT of USB
23/04/1999 22:22 222,390 IO.SYS
18/07/1999 21:05 9 MSDOS.SYS
23/04/1999 22:22 93,890 COMMAND.COM
23/04/1999 22:22 33,191 HIMEM.SYS
16/07/2010 07:38 <DIR> COPY2RAM
12/08/1998 01:09 20,016 xmsdsk.exe
30/03/2008 21:14 18 config.sys
30/03/2008 21:13 71 autoexec.bat
7 File(s) 369,585 bytes
1 Dir(s) 2,025,095,168 bytes free

COPY2RAM
16/07/2010 07:38 <DIR> .
16/07/2010 07:38 <DIR> ..
23/04/1999 22:22 93,890 COMMAND.COM
27/03/2008 02:06 52,106 ASPIEHCI.SYS
18/08/1995 01:00 2,862 CTLOAD.COM
16/08/2001 02:00 16,368 DI1000DD.SYS
30/03/2008 21:14 50 load.bat
22/11/2006 17:19 118,743 NTFS4DOS.EXE
6 File(s) 284,019 bytes
2 Dir(s) 2,025,095,168 bytes free

when it get to loading the 2 drivers

c: copy toram

r:command.com
bad command or file name

r:ctload aspiehci.sys /all /int

IOMEGA BLAH BLAH

no devices found
driver init' failed

r: ct load di1000dd.sys
ASPI DISK DRIVER Ver2.00
NOVAC BLAH

ASPI Manager not installed
driver init failed


Now I'm thinking firstly that I need the driver from the WORKING USB-FREEDOS
AKA USBASPI.SYS needs to take over from ASPIEHCI.SYS in the "HOW TO DOS-SUB", am I on the right track? :thumbup:

#20 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 - 07:28 AM

You are on the right track, but still you are a bit confused. :thumbup:

Create the ntfs4dos floppy image.
Open the image with 7-zip.
Extract from it NTFS4DOS.EXE.
Copy it to your "COPY2RAM" folder. (this is the only thing *needed*)

OR

simply leave it alone for the moment, it is not connected with the driver issue.

Try changing the hidden attribute to the command.com copy in "COPY2RAM".
The command.com is evidently NOT copied to R: and this may be part of the problem. ;)

The general idea is to try things and replicate (if possible) what is reported as working, before attempting "mixing" things. :cheers:

;)
Wonko

#21 Technotika

Technotika

    Frequent Member

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

Posted 16 July 2010 - 10:15 AM

Jeees how much hassle removing hidden from that pesky little file! :cheers:
(me) attrib command.com -h
(Win) not resetting system file

(me) ok then I'll down load something that will (ireset) Done!

..And the oscar goes to WONKO :thumbup:

No ERRORS and now sits waiting @ R:\ (in qemu) but i'm confident that this is working now
in terms of setting up the "how to USB DOS"
that NTFS4DOS.EXE sorted too although for my needs I think its irelevant (for now).
So.....now for the final stage.....

the autexec in HOW to IS....

xmsdsk 16384 r: /y
cd COPY2RAM
copy *.* r:
r:
command.com
load.bat

the autoexec in WORK

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

the config sys in HOW TO DOS
device = himem.sys

the config sys in WORK
DEVICE=himem.sys /testmem:off /v
DEVICE=btdosm.sys
DEVICE=flashpt.sys
LASTDRIVE = Z
#########################################################################
Mix Up TEST
Final Mixed config sys to reside in the final HOW TO USB DOS version, I would have thought....

DEVICE=himem.sys /testmem:off /v
DEVICE=btdosm.sys (to be copied to HOW TO from work )
DEVICE=flashpt.sys (to be copied to HOW TO from work) (god knows what they do but in the interest of continuity etc)
LASTDRIVE = Z

#########################################################################
Final AUTOEXEC.BAT
hmmm

here's a punt......

stick the content of work autoe#.bat at the end of LOAD.BAT in copy2ram?????
EDIT nah wont work.....needs Q

soo........maybe...

XMSDSK 2048 Q: /y
cd COPY2RAM
copy *.* Q:
Q:
command.com
load.bat < then in there C:\cddeploy @ the end of

ctload aspiehci.sys /all /int
ctload di1000dd.sys
C:\path-tofolder-on-USB\cddeploy

#22 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 - 11:48 AM

Jeees how much hassle removing hidden from that pesky little file! ;)
(me) attrib command.com -h
(Win) not resetting system file

(me) ok then I'll down load something that will (ireset) Done!


The idea was to learn how to use attrib BEFORE using it. ;)

You cannot unhide a System file, you need to remove the S attribute, first.:thumbup:

attrib command.com -s -h

:cheers:
Wonko

#23 Technotika

Technotika

    Frequent Member

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

Posted 16 July 2010 - 12:28 PM

LOL well I guess I do now! :cheers: (in a fashion)

Right back to it.....having a bit of brainstew trying to get this flipping CDDEPLOY.BAT to load in the new HOW TO USB-DOS stick.

ATTEMPTS
1. With my limted knowledge I'd exepect all items in there to be, as in the name of the file, automatically executed. Big brain on brad I know.

so....

XMSDSK 2048 Q: /y
C:\cddeploy

Is the line i need from work INCLUDING in new USBDOS.

So I have ammended to make this

XMSDSK 2048 Q: /y
cd COPY2RAM
copy *.* Q:
Q:
command.com
load.bat

So a Q: is created that the USB-DOS floppy can use and also the WORK-DOS.
In "load.bat" I put

ctload aspiehci.sys /all /int
ctload di1000dd.sys
CDDEPLOY.BAT < (sat in both the COPY2RAM and the root of USB)

But each time It doesnt even see it and just sits @ Q:\

I also put it here too

XMSDSK 2048 Q: /y
cd COPY2RAM
copy *.* Q:
Q:
command.com
load.bat
cddeploy.bat

same thing But each time It doesnt even see it (no errors) and just sits @ Q:\

How come its missing out the last part (cddeploy.bat) of the autoexec?
I'm probably being dumb I thought I'd at least be able to trigger it and work it back but I'm missing somet :thumbup:
EDIT######################

Just done a F8 start up diag and noticed more issues - LOAD.BAT doesnt run by itself, which is why CDDEPLOY not running, ok, However when I do run load.bat from the command line it still doesnt load the USB driver.

Hang on got something

xmsdsk 16384 r: /y
cd COPY2RAM
copy *.* r:
r:\load.bat <<<<<<<<< with cd deploy in there - it runs - right now I can fiddle - will post back

#24 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 - 01:10 PM

And still you are missing the general idea. ;)

BATCH files are a handy way to replicate easily what you KNOW it's working manually. :cheers:

Just read SLOWLY this:

XMSDSK 2048 Q: /y
cd COPY2RAM
copy *.* Q:
Q:
command.com
load.bat

ctload aspiehci.sys /all /int
ctload di1000dd.sys
CDDEPLOY.BAT


This is executed when the current directory id the whatever you booted from, let's say "C:\" i.e. it runs from a C:\> prompt:

C:\>XMSDSK 2048 Q: /y = C:\XMSDSK 2048 Q: /y
this changes DIRECTORY:
C:\>cd COPY2RAM
now the prompt is:
C:\COPY2RAM\>
and
C:\COPY2RAM\>copy *.* Q:
works allright, then you do:
C:\COPY2RAM\>Q:
this changes CURRENT DRIVE and the new prompt is:
Q:\>
and all these will work:
Q:\>command.com
Q:\>load.bat
Q:\>ctload aspiehci.sys /all /int
Q:\>ctload di1000dd.sys
as these are files you just copied to Q:\
This:
Q:\>CDDEPLOY.BAT
will FAIL since there is NO "CDDEPLOY.BAT" in the Q:\ drive (current root).

this will work (provided that CDDEPLOY.BAT is in C:\:
Q:\>C:\CDDEPLOY.BAT

BTW the one in "WORK" you posted had the line:
C&#58;\cddeploy

Obviously whether CDDEPLOY.BAT will work will depend on WHAT is in it (relative or absolute paths to invoked executables or files).
;)



Moral: take your time to think about using ABSOLUTE paths in batch files OR use RELATIVE paths PROPERLY. :thumbup:

;)
Wonko

#25 Technotika

Technotika

    Frequent Member

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

Posted 16 July 2010 - 02:04 PM

I'm getting it by bit now

this HOW TO USB-DOS is kind of like a multipurpose floppy.

Get to the prompt then load the files eg LOAD or NTFS4DOS.EXE from there depending on what you want it for. "Load" for me coz I want USB etc.

So messing about and tweaking I have manage to fudge my way into gettting CDDELPOY.bat to load by itself if I want to. CDDEPLOY will work (in theory) once I apply the floppy to the main USB with the relevant files it needs and as long as can see on C: too.

HOWEVER I am now back right at the start in terms of another issue..........

For me
ctload aspiehci.sys /all /int
ctload di1000dd.sys

doesnt work.....

Either Hangs at the IOMEGA syntax or finds no device.
tried 2 x USB sticks and some different switches from the freedos version earlier today
(aspiehci.sys /r /v)
Nothing. Same.

So...........

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.

Any ideas, captain? :thumbup:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users