spacesurfer

I understand your problem. I had custom made toolbars in 2003 and had a hell of a time getting them in 2007. The only way to do it was the method I mentioned above. However, I was unware that you are using 2002. I don't think there is a difference between 2002 normal.dot and 2003 normal.dot. If that seems to be the only problem, try this: open the 2002 normal.dot using a computer that has 2003 loaded. Then use the method I mentioned. Your customized toolbars should come up as a Add-in tab in the ribbon. Or here is the help from 2007 on how to load a template temporarily: Load or unload a template or add-in program Templates can store styles, AutoText entries, AutoCorrect entries, macros, toolbars, custom menu settings, and shortcut keys. Loading a template makes it available as a global template that you can use while you work with documents based on any other template. Add-ins are supplemental programs that you can install to extend the capabilities of Microsoft Office Word by adding custom commands and specialized features. An example of an add-in program might be a program designed and distributed by your company's IT department to highlight company names in any document you open on your computer. What do you want to do? -------------------------------------------------------------------------------- Load templates or add-ins Unload templates or add-ins Make a template or add-in available whenever you start Word -------------------------------------------------------------------------------- Load templates or add-ins When you load a template or add-in, it remains loaded for the current Word session only. If you quit and then restart Word, the template or add-in is not automatically reloaded. Click the Microsoft Office Button , and then click Word Options. Click Add-Ins. In the Manage list, select Word Add-ins, and then click Go. Click the Templates tab. Under Global templates and add-ins, select the check box next to the template or add-in that you want to load. If the template or add-in you want does not appear in the box, click Add, switch to the folder that contains the template or add-in you want, click it, and then click OK. Top of Page Unload templates or add-ins To conserve memory and increase the speed of Word, it's a good idea to unload templates and add-in programs you don't often use. When you unload a template or add-in that's located in your Startup folder, Word unloads the template for the current Word session but automatically reloads it the next time you start Word. When you unload a template or add-in located in any other folder, it is unavailable until you reload it. To delete a template or add-in from Word, you must remove the template or add-in from the Templates and Add-ins dialog box. Click the Microsoft Office Button , and then click Word Options. Click Add-Ins. In the Manage list, select Word Add-ins, and then click Go. Click the Templates tab. Do one of the following: To unload a template or add-in but leave it under Global templates and add-ins, clear the check box next to the name of the item. To unload a template or add-in and remove it from the box under Global templates and add-ins, click the item in the box, and then click Remove. Notes The Remove button is unavailable when the template you select is located in your Startup folder. When you unload a template or add-in, you do not remove it from your computer — you only make it unavailable. Where you've stored the template or add-in determines whether it's loaded when you start Word. Top of Page Make a template or add-in available whenever you start Word To have a template or add-in available whenever you start Word, store the add-in or template in the Startup folder. By default, the Startup folder is located in one of the following folders: Microsoft Windows Vista c:\Users\user name\AppData\Microsoft\Word\STARTUP Microsoft Windows Server 2003 or Microsoft Windows XP c:\Documents and Settings\user name\Application Data\Microsoft\Word\STARTUP If the location of the Startup folder has changed, you can find it by doing the following: Click the Microsoft Office Button , and then click Word Options. Click Advanced. Under General, click File Locations. Save the template that you want available when you start Word to the location that is listed for Startup.

try equation editor by mathtype

Office 2007 used the new Open XML format. Therefore, the Office 2003's normal.dot is the old version for 2007 to use. It will update the document template (i.e. 2003's normal.dot) to the newer version so that it can save documents correctly for the Open XML format. The only way around this is to copy your old normal.dot to the folder "%userfprofile%\Application Data\Microsoft\Word\STARTUP\" and word will import the contents of the 2003 version of normal.dot. Good luck.

You need to reshack logonui.exe. The location of file is %systemroot%\system32\logonui.exe.

I'm having the same problem on a Dell Latitude C600. I have an installation where the battery drivers are recognized on setup. I have a Ghost Image of that. Then I used RyanVM to update my XP SP2 installation source and installed and screewy! Battery does not get recognized. I can't put it to sleep. I've tried so much like 10 times. I EVEN TRIED WITHOUT THE RYANVM PACKS AND STILL IT WON'T GET RECOGNIZED. The only thing that works is my Ghost Image. Basically, my only hope is that Ghost Image that I have for my battery to work. I don't know what happened. I didn't changed anything except enable Infrared port in BIOS. I thought that was the problem, but I disable it and tried installing over 20 times with and without RyanVM packs and still no luck. It's nerve wrecking. I also used Double Drive to save the drivers from an install where the batter worked, but that didn't work either.

but for unattended installations, it's better to run a script to import your tweaks automatically rather than click on them all one at a time.

change the view of your document from the current to normal view by clicking on one of the three icons on left bottom. you will be able to see where the section breaks are and delete them.

Sorry, when my HDD crashed, I lost everything. I had a hard copy which I scanned and made into PDF. Here it is: Driver's Integration Thanks, Mazin, for upload site.

I assume you're trying to reduce the size since no space before or after. Have you tried deleting that partition and creating a new one (provided there's no data on it?

Do you have any data in your D, E, and F right now. If not, delete all partitions and recreate them and it should be reset. Otherwise, you might have to backup your data, then delete all partitions and recreate them.

Yzowl and jaclaz, this is the error I get with Yzowl's script using mountvol. I modified the script a bit for my unattended to look for win51 and drivers.tag: REM NEW SEARCH FOR CD-ROM DRIVE REM ----------------------- for /f "delims=\" %%? in ('mountvol^|find ":\"') do dir/b/-d %%?\WIN51 &&SET CDDRIVE=%%? ECHO. GOTO DRVPATH REM SEARCH FOR DRIVERS PATH REM ----------------------- :DRVPATH SET DRVPATH=%CDDRIVE% for /f "delims=\" %%? in ('mountvol^|find ":\"') do dir /b /AS /-d %%?\DRIVERS\DRIVERS.TAG &&SET DRVPATH=%%? ECHO. goto STARTSETUP Here are the screens that show the extra spaces: This one shows the spaces before the drive letter assignment and after the dir command: This one shows the spaces in the echo command: And this one results in an error when I try to copy tweak.cmd to %systemroot%: Any ideas on what can be causing this? I probably will just have to use the for %%x in (c d e f g ....) and do the loop de loop thing.

i use metapad. much better than notepad. it has a toolbar, unlike xp notepad or even vista notepad. i simply rename metapad to notepad, makecab compress, and replace installation with this one!

I think 'batmeter.dll' has part of the icons. Some of the icons for your system tray objects are also in 'stobjects.dll'. Check this file as well.

Today, I just tried VTP 5.5 uxtheme.dll. I installed fresh XP in virtual pc. Then, I installed VTP 5.5. I grabbed uxtheme.dll (and some other files). I compressed it using makecab. Then, I replaced the original uxtheme.dl_ with this one in my ISO. Then I tried installing in my notebook... and I got an error about not being able to copy uxtheme.dll. I have used uxtheme.dll in MSFN's unattended section without a problem.

I had this problem before on a previous build. It would not let me do anything. Baffled me. I had to get rid of it and go back to XP. Thanks for this tip. I'll keep it in mind.

Yeah, give me some time to find it and I'll send it to you.

Absolutely, right, Jaclaz. The check file size is not needed. However, I once reinstalled XP and it automatically changed my primary partition to an extended partition (it had 8 mb unpartitioned space before my first partition - I couldn't get rid of it using XP setup. Only way to get rid of it was to delete all my partition, but I didn't want to delete D: and E: since they both had data). So my ntldr and boot.ini ended up on D: while XP was on C:\. What this means is that if you want to reinstall on C: when D: and E: are already present, don't delete C: and then create a new partition. Just install on C: and let it format. It baffled me until I figured out what happened. So, I at least need to make sure that ntldr and boot.ini ended up in the right place. The size check is not needed but gives you the assurance it's the right size... What the heck... I learned something new from all this... I'll post a screenshot later of the error I'm getting (the " c:\ntldr" error). Delprat should also know that his script about right-click installing fonts didn't work on my machine but it did on Windows 2000 I tested, so I have something wrong with my installation source. It's XP SP2 with Ryan VM packs.

Can you be specific about which icons? Are you talking about the toolbar icons, or the regular program icons (for shortcuts, etc.). Shell32.dll applies to the system and is not on a per user basis. Make sure your OS didn't restore the original file (check the size). If it's the modified file, then all users should have the same icons, without having to refresh the system.

That's awesome, MHz. This works for any command you specify. Here's a quick way to compress and expand your files using expand and makecab commands (using the Left Shift key to show them): [HKEY_CLASSES_ROOT\*\shell] [HKEY_CLASSES_ROOT\*\shell\Expand] @="Expand" "extended"="" [HKEY_CLASSES_ROOT\*\shell\Expand\command] @="expand -r \"%1\" %cd%" [HKEY_CLASSES_ROOT\*\shell\Makecab] @="Makecab" "extended"="" [HKEY_CLASSES_ROOT\*\shell\Makecab\command] @="makecab \"%1\""

I have noticed that if you install XP on an extended partition, then it will place your boot.ini and ntldr on the FIRST PRIMARY partition on the FIRST hard drive it finds.... someone correct me if I'm wrong. Anyway, that set up is not ideal since if you format the partition that has your boot files, you won't be able to load XP. Go to folder options and choose to unhide system files to locate these files. Also, check in computer management --> disk management to make sure your XP partition is not extended. If it is, you might consider formatting it to a primary partition. then it will place both files in the same partition.

I copied it exactly. I didn't retype it. Your scripts are baffling... they seem to work, except this one... I'll work on it some more to see what's wrong. Anyway, I found one script on this page that works. Thanks.

I think I missed something here. Vista CD's are UDF file system - which aren't they just images of DVD's instead of CD's? Daemon Tools can't mount UDF images, at least it's not listed. PowerISO can't mount it. Filedisk can't mount it - all you see is a readme.txt and nothing else. If it can be mounted, what program can mount UDF and see all the setup files instead of just the readme.txt? You can't mount the ISO is virtualpc either. it tells you ISO is not valid or something...

works for me. -P nuff said.

Since nobody's commented... I reinstalled like 20 times, and narrowed the runsetup.dll error during GUI setup to a device driver (I don't exactly know which one, but I was using Pyron's method to detect drivers during install). The battery problem still persists. I tried April, June, and August RyanVM packs and they all give me no battery drivers. So I have a laptop that I can't put into standby. It remains on all the time. My only option was to use a ghost image I had created that had those drivers.

Yzowl, your script in post #3 gives me extra spaces and it fails. What is does is: for ntldr do if exist " C:\ntldr".... There are spaces after the first quotation. It's strange. Is MY windows bugged?