Mr_Smartepants

Thanks bober, I'll give that new code a shot when I get home.

OK, the bug still exists in the batch addon. I don't know what's going on in the code, but the final product doesn't get copied back to \i386\ Is there a way to implement logging? At least a 'debug' mode?

Found a bug in Batch-addon beta16! winntbbu.dll disappeared from i386\ after integration. Cause: :winntbbu title XPtsp script Progress 87%%%... set name=winntbbu set ext=dll set big=WINNTBBU set com=DL_ if exist "i386\%big%.%com%" %xp% "i386\%big%.%com%" "%tmp%\%name%.%ext%" >nul if exist "i386\%big%.%com%" Del "i386\%big%.%com%" >nul if not exist "i386\%big%.%com%" set com=DLL if exist "i386\%big%.%com%" %cp% "i386\%big%.%com%" "%tmp%\%big%.%com%" >nul if not exist "i386\%big%.%com%" goto winntbba %rh% %del% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", stringtable,, %rh% %ao% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", "%res%\%name%.%ext%.res",,,&echo patching %name%.%ext% %pe% -c %tmp%\%name%.%ext% >nul %cp% /v /y "%tmp%\%name%.%ext%" "i386\%big%.%com%" >nul It should be: :winntbbu title XPtsp script Progress 87%%%... set name=winntbbu set ext=dll set big=WINNTBBU set com=DL_ if exist "i386\%big%.%com%" %xp% "i386\%big%.%com%" "%tmp%\%name%.%ext%" >nul if exist "i386\%big%.%com%" Del "i386\%big%.%com%" >nul if not exist "i386\%big%.%com%" set com=dll if exist "i386\%big%.%com%" %cp% "i386\%big%.%com%" "%tmp%\%big%.%com%" >nul if not exist "i386\%big%.%com%" goto winntbba %rh% %del% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", stringtable,, %rh% %ao% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", "%res%\%name%.%ext%.res",,,&echo patching %name%.%ext% %pe% -c %tmp%\%name%.%ext% >nul %cp% /v /y "%tmp%\%name%.%ext%" "i386\%big%.%com%" >nul Note the change in case from set com=DLL to set com=dll This bug is also in :winntbba :winnt32a :winnt32u Another 'annoyance' I just noticed with beta16 batch-addon is bober's added a check in the batch file to look for \i386\driver and if it's there to halt the integration. I use AutoImage and perform all integrations in one shot, this new batch file breaks that. I've altered the batch file to remove the check and everything is fine for me. (But I use OnePiece's AIO updatepack)

You know, I never really noticed it before, but winntbbu.dll has all the text missing from the main (right) pane during setup. When did this change happen? :/ Not that I'm worried about it, like I said, I just noticed it. Keep up the great work guys!

Thanks bober. I think my install got botched somehow, since oemgen.exe WAS missing on my end. RVMI has been twitchy lately.

There's a bug in the batch-addon in "addrunonceexe.bat". I got a "file not found" error at ROE. @echo off title= adding OEM info generator to runonceexe echo adding OEM info generator to runonceexe FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\i386\svcpack\oemgen.exe SET CDROM=%%i: SET PP=%CDROM%i386\svcpack\ SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\987 /VE /D "running OEM info generator" /f REG ADD %KEY%\987 /V 1 /D "%CDROM%i386\svcpack\oemgen.exe" /f What's with the SET PP ? %PP% isn't called anywhere... Notice the lack of forward-slashes? It should be this: @echo off title= adding OEM info generator to runonceexe echo adding OEM info generator to runonceexe FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\i386\svcpack\oemgen.exe SET CDROM=%%i: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\987 /VE /D "running OEM info generator" /f REG ADD %KEY%\987 /V 1 /D "%CDROM%\i386\svcpack\oemgen.exe" /f Also, oemgen.exe is missing from i386\svcpack\

Well, it's downloaded, the hash matches, but I get an error immediately following extraction saying "XPtsp.exe - file not found". Opening the archive shows that file doesn't exist. Sorry for the bad news.

Sorry, download link fails on your site.

Rick, Downloaded file doesn't have the term "_AddOn" in the filename. And the version# is the same.

So, you're adding :winntbbu and :winntbb2 sections, but that leave behind :winntbba which isn't indexed. Or does :winntbba get replaced too? Otherwise the code should look like this: :winntbbu title XPtsp script Progress 87%%%... set name=winntbbu set ext=dll set big=WINNTBBU set com=DL_ if not exist "i386\%big%.%com%" goto winntbbu2 %xp% "i386\%big%.%com%" "%tmp%\%name%.%ext%" >nul %rh% %ao% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", "%res%\%name%.%ext%.res",,,&echo patching %name%.%ext% %pe% -c %tmp%\%name%.%ext% >nul %cab% /D CompressionType=LZX /D CompressionMemory=21 "%tmp%\%name%.%ext%" "i386\%big%.%com%" >nul :winntbbu2 set name=winntbbu set ext=dll set big=WINNTBBU set com=DLL if not exist "i386\%big%.%com%" goto winntbba %cp% /v /y "i386\%big%.%com%" "%tmp%\%name%.%ext%" >nul %rh% %ao% "%tmp%\%name%.%ext%", "%tmp%\%name%.%ext%", "%res%\%name%.%ext%.res",,,&echo patching %name%.%ext% %pe% -c %tmp%\%name%.%ext% >nul %cp% /v /y "%tmp%\%name%.%ext%" "i386\%big%.%com%" >nul

I just got a weird error during txtsetup. "Could not copy winntbbu.dll" This was after using b13 batch. b13 gui has it's own strange error. I usually use RVMI to build my ISO but this time I thought I'd let the gui do it. Before txtsetup even starts, I get a screen that says I haven't declared a PC type and has "Other" highlighted in the middle of the screen. Reproducible in virtualbox and real hw. Building the iso with RVMI does not show this problem. Other than that, the eye candy looks awesome! I can't wait to finally reformat my notebook once the bugs are cleared.

You guys are awesome! Thanks. :thumbsup_anim:

As cool as that may look, I would prefer to keep the .exe additions to an absolute minimum. At the very least, optional from the GUI selection prior to integration.

How'd you manage to disable the embedded toolbar installer? I wrestled with it then gave up and wrote a .bat uninstaller that ran immediately after install to get rid of it. Not very elegant.

@Bober, Download links are both still pointing to the addon, not the batch installer.

This is the wallpaper I use personally. Very nice. BTW, both links in first post are for "batch ADDON".

OK Rick, now you've got me thoroughly confused! I have Vista64 Ultimate (with legit key). How do I get data.bin again? Step by step please...

OK, no problem. When you're used to seeing things a certain way, then something changes it draws your attention. Cool! :thumbsup_anim:

I don't use the gui to build the ISO. After the batch/gui patch, I run DriverPacks Base, then I build the ISO with RVMI. I have no problems with these steps if I omit the gui. Batch works fine except for my bug report above. Is there an unfinished task during the 'build ISO' phase in gui? Oh, one other thing. On the user login page, what's with the "EN" button on the bottom left of the screen? That wasn't there before (and does nothing when clicked).

Found a bug in each. In XPtsp.v1.0.10b11batch.exe, if there is no "setup.exe" at root of destination folder, batch file halts at "Replacing setup.exe". Creating a dummy .txt file and renaming it "setup.exe" fixes the problem. I simply cannot get XPtsp_v1.0.10b11a_GUI.exe to work. It seems to integrate fine into my source, but the resulting ISO is broken. When booting into VM (VirtualBox), you get to the 'format drive' option, the drive formats, then fails at the txtsetup filecopy stage with "CDROM drive cannot be read" error.

My OEMscan fully automated addon 1.8 is found here: http://siginetsoftware.com/forum/showthread.php?t=541 ...and my older OEMscan addon v1.6.9 is found here: http://siginetsoftware.com/forum/showthread.php?t=272 ...and Siginet's OEMscan addon v1.7b is found here: http://siginetsoftware.com/forum/showthread.php?t=276 Enjoy.

The head crabs are coming! Where's my gravity gun?

www.portforward.com It's a great resource for just this subject.

Don't count on it my friend! M$ doesn't enjoy people like us very much. Keep working on it though. We'll get there in the end. Good work everyone. Getting closer...

I personally use this addon here: http://www.ryanvm.net/forum/viewtopic.php?t=3477 Works exactly like you would want. The addon can be tailored to your own needs. The RapidShare links still work.