LiquidSage

Check the fans and the grills for obstructions or misalignment. Fans spin fast during normal operation and tend to rotate smoothly. However, much like a spinning top that is losing speed, the wobble becomes quite evident at the end. Regardless, since it is new, I would go get an exchange. A PSU (esp. new ones) should not whine and I'm sure that is not what you paid for nor is it what they advertise on the box.

when you install from a hd, an answer file is created telling windows that the install is from the hd and where the install files are located. when you copy from a cd, the answer file is of the type 'cd' install, and the loc. of the cd files is noted. You basically have a 'cd' type install pointing to the hd as the location of the files. There are methods talked about in this forum which in a general sense, boot from cd, copy installation files (source) to hd and then trigger the installer. Start an install while in windows, tell it to copy source files to d:\ and then cancel the reboot screen. You will note in the answer files created in the pre install folders ($WIN_NT$) that there are very important differences.

might be best to redo your project and make it basic (1 diff OS of xp 2003, 2000, no winnt.sif no extra prog install, no hacks, etc) Verify that it works and then start with winnt.sif and extras. If you get Balder Multiboot, you can have it build the structure (1 OS at a time unless you pay for this overpriced utility) and just put the pieces together. otherwise, post your folder stucture and the different winnt.sif files. Are you building winnt.sif yourself, or are you using MS setup generator?

you might try to do a quick pre- install from an OS, grab the answer file and replace the one which is copied from your dvd install. Windows generates a different answer file for a HD install. i think gosh's website has a method for copying the source to hd from a cd.

http://cquirke.mvps.org/sp2intel.htm

good to hear! if after checking the guide out you still have probs, Don't hesitate to ask! An easy way to check OS version and build # would be to point AutoStreamer to the folder you think contains a window source and if it is, AutoStreamer will let you identify, slipstream a sp, and generate a bootable ISO for you to burn to cd. Balder multiboot and Nlite can do the same as well, plus extra options.

exactly where did you place your winnt.sif? do you have any unattend.txt files in either the cd folder or the boot folder? if so, delete them. if you can post your multiboot dir, it may be helpful. Despite the winnt.sif issue, win2000 installs correctly and error free right? may help, w2k OemPnPDriversPath= is very limited in length compared to xp and 2003. you may have to cut the depth of your driver folders for them all to fit in OemPnPDriversPath. i know this was discussed a while back on this forum.

either you do not have a fully lic. copy of bart or you did not make your iso with the proper settings during creation. (avast bart files might not all be uppercase in your project) I find it better just to make a menu and call the avast bart exe's as a plugin for bart pe. that way, you can ditch ASWSHELL2.EXE, ASWSHELL.EXE, and ASWSHMIN.EXE.

for starters, you do not have enough info for a fully unattended winnt.sif file. You need to include name, computer name just glancing at it. check that your sif file does not have a '.txt'. that is probably the most common problem with winnt.sif not loading correctly. also I can't remember if it matters, but my UnattendedInstall= is "Yes", not Yes. good luck

folliw the cdshell easyboot etc script. look for a folder that has a setup.exe, i386 folder and xxxip files. it's pretty easy. even taking a quick glance at the aio guide hosted here would be enough for you to see what is what. Though i'm sure you would find someone here to go over a dir listing of your multiboot cd, the time waiting for someone to do it would be longer than the 5min looking at the guide and working backwards.

delete splash.csi and splash.bmp in the graphics folder....actually....just delete the graphics folder altogether. for the press anykey... grab the file bootfix.bin from a windows installation cd and add it to your cdshell project or code a keystroke check yourself as your first action when you make your cdsh script.

yes... DD 9 is my first choice for OS prep. I have set a 300 gb HD as ntfs with it. Correct detection through mobo and 48-bit LBA ATAPI support could be a set back. This microsoft link explains how to enable 48 bit lba via cmdlines during XP OS install. I have found that though XP sp1 and above support this, it is not enabled by default (at least for me ). 2003 should be fine using that link. I think the minimum build for 2000 supporting LBA is sp4. Also, I have done very large HD formats with paragon's recovery kit cd ran in linux at the menu, not DOS (uses partition manager 6 lite). Getting 237gb from a 250gb HD is around the correct size using ntfs just in case you weren't sure...

You are more than likely to have difficulties with MagicISO, Newest BCDW or cdshell would be your best bet. Some like EasyBoot and I think more types of iso's converted to bif (at least acronis) work in EasyBoot.

Have you modified your distro at all? (EX - used nlite to reduce source, or 'gosh's method' ? Are you starting from a windows xp cd or a recovery distro provided by dell, hp, etc? If you have the cd i suggest using something simple and to the point to SS and build your ISO like AutoStreamer. Test it and if it works we can better pinpoint your problem

It could be useful if a critical app is damaged and is causing boot troubles. Sony for instance wraps their driver and critical apps (like power panel) in installshield. However, for this purpose, you would be better off grabing iscabview and the related mediabuildxx.dll from an installshield setup making program such as PRO 7 or Administudio 6 to extract the files and reg. tables. Even better would be to include WinPack v3.00 by snoopy81 which can extract whole dir and let you modify and update installshield setups for v 6 and under. I use WinPack to add files and modify files that then allow a very tidy silent install. This is one of my little jems i don't readily mention but since we are talking about installshield The major problem lies in making sure enough temp space is free and how to redirect file installs going to read only areas that are on cd such as system, system32 dirs. Maybe if PE is on HD you could run setups, but i would just use WinPack (to get files and whole dirs) and iscabview (mainly to get reg info) then use existing reg tools to import into the damaged OS.

Concerning password resets which can be used in RecCons. You could use the bootable recovery console build made by OOBlueConXXL which has a password reset tool + many others. Or you try something like ChangeNTPassword by Peter Nordahl-Hagen or EBCD. As i know, there are 3 different RecCons bootable ISO's circulating. One is a 2000 build, the other is XP SP1 Home ed. build. A third is the win2000 bootable reg repair utility merged with the bootable XP RecCons build. You can also make a 2003 build if you install RecCon to HD and know how to replace/rename the proper files to achieve a bootable CD copy. I have not seen any method to bypass the blue screen showing press'r' to ... and bypass admin password issues automatically. A good thing too! To bypass or reset account password puts private / EFS files in jeopardy.

post a few pics

WinISO is old and can't handle many of the new bootable Nx1 or modified bootable ISO's. Still useful for a few specific projects, but unless you know what they are, ditch WinISO. an easy way: Open your ISO and drop the files needed in the proper folders using a recent version of UltraISO. Save this modified ISO as a new file. Do not try to save the changes to the original ISO. The bootfile is preserved using this method. No need to change ISO attributes or mess with the bootable info. Since ERD Commander 2005 is under 300mb. You should be able to complete this project using UltraISO in trial mode if you are not ready to purchase the program. However, UltraISO (at least for me) is a corner-stone utility for doing bootable projects and I highly advise you to buy a lic. for it if you want to easily work with image files.

Dvd's have a limitation of files greater than 2 gb. You need to telll ghost to split your image into multiple files, each less than 2 gb.

sata ahci supports Hot Plug and Native Command Queuing. so yes, you would see an increase in speed using ahci though you will probably need to do an OS reinstall to use AHCI since AHCI is detected like a RAID setup. Maxtor isn't very truthful about their silent drives. They adjust the drive's speed settings changable through a utility that you can download (Maxtor’s Acoustic Management Utility). They have not really advanced in making the drive produce less noise at full speed. From the factory they are set in the middle area of performance for Acoustic Management, so as to seem quiet to the general consumer, plus since the drive doesn't work as hard as it could, it can prolong the life of the drive. I personally disable it through the utility and go full speed.

Try UPX on exe ocx dll and (+ a whole lot more file types) and you can easily free up some space. For example, all nero 32bit exe file can be UPXed. (Version 6.6.0.8 = 14.6 MB Same version using UPX = 4.17 MB.) Adobe exe and dll files work fine after UPX as well. Acrobat becomes A LOT smaller. Many windows files work fine too. Be sure to test all programs to be sure they work!! I cannot stress this enough. I personally use 2 different front ends for UPX. UPX Shell by Darklordz and GUIPex. Be warned... big files like nero.exe or photoshop.exe can take a long time to compress. A tip....don't use max compression, use the setting just below max. It will compress much quicker and the size difference between this and max is negligible.

you are calling the text color incorrectly. should be print c "\c092ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" Which would tell cdshell to print this line centered with a background color of bright blue and a text color of green. A little too funky for my eyes fix towards the end , I suggest you go to the cdshell site and read the instructions. You have many more syntax errors and 5 min of looking at the help (though hardly anyone does) will save hours of frustration.

Change diskdirector.exe to diskdirector.zip. with winrar installed, r.click on diskdirector.zip and extract... (you can do the same w/ the other exe's as well) the graphics look really bad booting from the kernels. If size is a must then it's a fair trade off. Ghandalf, please post in detail how you went about building your ima. Also, the wbt method will work (and is the easiest IMO) if you have the correct version of bcdw module and cdshell 2.0.11.

CD Shell 2.0.11 was the last fully stable release to work with the bcdw 1.5z plug-in. If someone is willing to host them for a good amount of time so all may share, I can send both full releases. (I also have the bcdw 1.5z plug-in for bscript as well if anyone is interested.)

this error is caused either by corrupt files or added drivers that are incompatible. try again making sure to copy each OS you add to your project from the original working source. Also make sure that every OS you add has the correct OS version added. If you are mixing and matching XP media and tablet that were SP2, w/ the regular and custom build of XP that was SP1. You might run into your problem.