LiquidSage

It is a problem. It does not write speciak builds like iso's that are optimized and other parameters that are now used. BartPE for instance. If your cd doesn't boot after playing with it, or it becomes corrupted all of a sudden, you probably used WinISO. It's been years since an update.

They are synergistic. Use both CDShell and the BCDW plugin. CDShell is powerful and easy to learn. Extremely compatible on a variety of systems, old to new. The limited GUI is supplemented with BCDW plugin module, Showgif. Now you can make animated, interactive menus using gifs. The BCDW itself is great for problem files and .wbt's (Acronis boot disks are easy to put in an AIO when they are converted to a wbt and called using bcdw.) Let's not forget that the new cdshell supports .imz booting. Now I have even more space on my CD to play with. I think I'm in love with both *Hint - An .imz is not made by WinImage. It is a compressed .ima/.img file made using gzip/gunzip. After compression, simply change the last letter of the file's extension to a 'z'. So after compression, of an ima, you would call it imz. Here is an nifty tool called WinGZ that will take care of any thinking involved in the whole process. Remember, if you use WinImage's .imz compression, your file WILL NOT BOOT! I don't think you should choose just CDShell or BCDW. Be naughty and choose both!

Norton is a problem. IMO McAfee isn't much better either. Have you tried NOD32? Here is a scan & clean version. It does not update itself nor does it offer resident or mail protection. You would have to buy the full version for that. However this is updated quite often @ Edskes, Quick and effective.

I have a feeling you tried overwriting a bootable image w/ WinISO.

the bcdw provides a graphic menu already with animation via showgif module

Using cdshell, CDShell will call the bcds.ini in the folder bcds folder. (The bcds folder should be in the same folder where cdshell.ini is, the boot folde) Modify the bcds.ini replacing an option that you will not use. Change the gif image corresp[onding to the option you are changing to reflect the proper title. Then simply call any boot command with "bcdw". Ex. Win98se....copy win98 install folder to cd root. Get win98 boot disk and place it in the folder "boot" call win98 boot by using bcdw \boot\win98.ima Using xp.......get the boot file....(im assuming you are putting I386 at root) change bcds.ini and the gif for the option # you are changing call xp using bcdw \i386\setupldr.bin call all other images the same way. The example .ini given in the bcdw plugin is easiy to modify plus the gif placement cordinates are already done for you. If you need more instruction read about the actual BCDW. It has more examples and scripts though the documentation is a bit thin. This page takes a lifetime + a few extra seconds to load.... http://bootcd.narod.ru/ntmultibootcd_e.htm A BartPE site that actually has a pretty well rounded tut. using BCDW and a variety of different boot options: XP, ERDCommander, OOBlueCon, Acronis ,Flonix ( Knoppix ) etc. Very decent for beginners. http://www.bootcd.uni.cc/Build_CECD.htm

try omega's ATI driver set or for the quick fix, d/l Force Refresh or something similar

Simply switching the cables would not cause an issue unless..... Did you... Plug in the cables all the way? Did you plug the master HD at the end and slave in the middle? Are you using the correct pin type? Could you have possibly bent a pin upon insertion? Did you unplug the power and ground yourself beforehand? Have you checked for changes in the BIOS?

All samples and instructions are on the same site that you d/l the BCDW plug-in example that is shown in your pic.

From Win 98SE , grab the"hidusb.sys" file and copy to your floppy. Load it in config.sys, or in autoexe.bat before PQMAGIC.exe. USB mouse should then work. If it doesn't, you may need a vendor specific mouse driver.

you can try this from kelly's korner

CD Shell has replaced BootScriptor. It would be to your advantage to just jump into CD Shell. However, BootScriptor has a quicker learning curve and also works with BCDW so if BootScriptor is your preference..... The BootScriptor Tutorial Two ways to add Acronis boot images to your AIO: EvilVoice's Guide

cdshw is only meant to debug the menu interface(s). It will always fail to load boot files by design. (Just think if you booted a self-automated disk wipe or partition formating utility for example.) You need to test it either in a virtual enviroment or burn to a disk and boot your pc w/ it.

nice to see you are on msfn as well as the 911cd.net. Seems these two forums go hand in hand

The GUI v1.0

Copy XP's ntdetect.com and ntldr over to the root of the 2000 partition

changing the pid is not a solution for xp. It's best to get a full copy of xp because what it takes to promote a upgrade to full would require replacing certain files to work around the limitation . In the end, for business...you expose your clients to an operating system enviroment that is not legal.

if you want to use the latest drivers or omega's ati drivers, get Patje's Mobility Mod - DH Mod tool to change the inf structure to allow mobility (laptop) driver installs. Use at your own risk! ( i have a 7500 also in my sony lappy. Omega's set usally screws up for me, but getting the latest drivers from ati and keeping the old control panel has been very positive.)

variety is the spice of life

don't use winiso!!! that will kill you multiboot iso...esp. if you have optimization involved. use ultraiso.

i hope you are saving the file as a fresh iso everytime you play w/ a multiboot iso. anyone using winiso? shame on you. Are you replacing the hex correctly? changing the boot file w/o recompiling a fresh iso can corrupt it

First make an admin install by running C:\WINDOWS\System32\msiexec.exe /I "C:\ACDSee v5.0 PowerPack\ACDSee 5.0 PowerPack.msi" (change DIR path as needed) Then try to SS. Put path in quotes!! Take off read only attrib if it is on. Make sure to full admin priv and also the right msp forv5. (either std or PP)

You did not format the system's primary boot partition. This happens if you have more than 1 hd, or more than 1 partition. You can check which is booting the system by finding ntldr , boot.ini, ntdetect.com or... open Disk Management and see what partition is defined as 'system'. You will need to edit boot.ini (uncheck 'read-only') and delete the OS that is not used.

you can mount the partition with your dir. as a virtual hard disk. ME will see it as nothing more than a plain hd.

Downlooad a trial version of installshield adminstudio (or just Tuner for mst's) , Wise Package Studio , or check out InstallSite for Installshield and MS specific info on MSI's. I really have learned a lot from that site. Here is a list of good info on MSI's and Installers to get your feet wet.