Ghost 11 5 Exe Dos S
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. 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!!! 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?
Ghost 11 5 Exe Dos S Gris
I will need a bit of hand holding on this as am not too hot at DOS. HISTORY I have tried PLOP. 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 (. Seek and you shall find.
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: and start your own experiments. There is a 'dedicated' board to GHOST, here:?
Where you may find more accurate and specific advice. Righty ho, here's what happened already I am reading this first, from the links supplied - 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? I am reading this first, from the links supplied. 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 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.
Ghost 11 5 Exe Dos S Nos
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'. Let's start from the beginning, OK? FORGET anything else and just try the suggested floppy: 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.
Post which one (if any ) 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? As well there are almost as many version of the Panasonic driver as stars in the sky (still less than GHOST versions, though ), 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: Download the file 'howtoupdated.zip' attached to it: Open it, read it's readme.txt and do EXACTLY what's in there. Report what happens.
Let's start from the beginning, OK? Smile.gif FORGET anything else and just try the suggested floppy: 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' ( )about USB key at home so cant create a proper DOS usb booter. I have set up a VFD (32L.VFD) and installed the (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 2.XMGR +JEMM386 cannot open cd driver SHCDX33E cannot load 3.JEMMEX cannot open cd driver SHCDX33E cannot load 4.NO ULTRA DMA (No CD) cannot open cd driver SHCDX33E cannot load 5.CLEAN 'appears to have worked; got to A: but previous mentioned No EDD BIOS logic. Unit 80h & 81h ignored'. 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: 22:22 33,191 HIMEM.SYS 11:17 COPY2RAM 01:09 20,016 xmsdsk.exe 21:14 18 config.sys 11:33 71 AUTOEXEC.BAT 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. 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.
I am missing something. Ok looks like 3 are goodies!!! 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!
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 22:22 222,390 IO.SYS 21:05 9 MSDOS.SYS 22:22 93,890 COMMAND.COM 22:22 33,191 HIMEM.SYS 07:38 COPY2RAM 01:09 20,016 xmsdsk.exe 21:14 18 config.sys 21:13 71 autoexec.bat 7 File(s) 369,585 bytes 1 Dir(s) 2,025,095,168 bytes free COPY2RAM 07:38.
Ghost 11 5 Exe Dos Set
You are on the right track, but still you are a bit confused. Create the ntfs4dos floppy image. Open the image with 7-zip. Biohazard gamecube iso roms. 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. 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!.And the oscar goes to WONKO 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. LOL well I guess I do now!
(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. 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. 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. And still you are missing the general idea. BATCH files are a handy way to replicate easily what you KNOW it's working manually.
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: 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. 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. Changed to what I know works ctload usbaspi.sys /vpanasonic 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?
Comments are closed.