InTheWayBoy

Well, I decided to invest some time into AutoIT and I think I'm glad I did...it's really slick, and I see a lot of uses for it. Essentially I setup everything in "install.au3", compile it to "install.exe", which is called from "config.txt" when making the sfx...which is currently still "build.bat". With the "install.exe" all commands are scripted, so there is now no need to hide a cmd window. install.au3 RunWait ( @ScriptDir & "\setup.exe" ) Sleep ( 10000 ) ProcessClose ( "qttask.exe" ) FileDelete ( @AppDataDir & "\Microsoft\Internet Explorer\Quick Launch\QuickTime Player.lnk" ) FileDelete ( @DesktopCommonDir & "\QuickTime Player.lnk" ) RegDelete ( "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run", "QuickTime Task" ) config.txt ;!@Install@!UTF-8! RunProgram="install.exe" ExtractTitle="Preparing For Installation..." GUIMode="1" ;!@InstallEnd@! build.bat copy /b 7zs.sfx + config.txt + QuickTime.7z QuickTime.exe Of course I have customized the script to remove certain items...shortcuts, folders, startup entries, etc...in the end it runs as silent as you can get I think. There is a little systray application that runs while "install.exe" does it's thing, but that's cool, cause then I know when it's done.

I'll look into the autoit script idea...was kinda hoping not to have to learn something new.

How can I make the CMD never appear during installations. Currently I have all my setup routines controlled by a batch file. The batch file calls CMDOW first so as to keep it from showing, but you still see the flash of the windows before it processes the CMDOW command. I'm calling the batch file from config.txt that I am using to create a 7zip installer. As it is right now I just call my 'setup.bat' and everything works as explained. I thought maybe I could do something different like run cmdow and then feed it the batch file. It works fine in a regular command window, but when I compile and run the installer it extracts and then complains about program not found and the like...I don't have the exact message. So I tried nircmd and got similar results. So how can this be done? I know there has to be a way to do this...if I understand it as I do, the only real way to do this would be to call the batch file from a program that hides the box, but how do I do that with a 7zip sfx? Anyone? Here's my current setup: setup.bat start "" /wait .\setup.exe /S del "C:\Documents and Settings\%USERNAME%\Desktop\ABC.lnk" config.txt ;!@Install@!UTF-8! RunProgram="setup.bat"" ;!@InstallEnd@! build.bat copy /b 7zs.sfx + config.txt + ABC.7z ABC.exe so in this case I make an archive (ABC.7z) containing setup.exe and setup.bat. I then execute build.bat which does all the magic and presto it works. Now I was including cmdow.exe in the archive with an entry at the beginning of setup.bat, but of course that's where I'm not happy. I saw on some forum about a new tools made by someone at another forum...runhiddencmd.exe or something. It sounded like just what I'm looking for, but I can't find it anymore. I think I'm getting mixed up on the syntax for config.txt, so if you have any examples that would be nice too...thanx!

WPI is the only one I've used so far, and there is a reason for that...it works! You will need some time to get it going, but it's easy once you get the hang of it. And it's pretty too!

Or you could use RyanVM's excellent silent installer...it's very nice. http://ryanvm.msfn.org/ The Java and Framework are essential too!

This really isn't all that great of a fix, but try this: http://support.microsoft.com/default.aspx?...kb;en-us;290301 It's a tool M$ put out to manually remove Windows Installer information from your computer...I've used it in cases like this. Basically what I do is find what Windows Installer is launching, then remove it. Of course, that 'breaks' that programs uninstall, so it's not the best as I mentioned, but it stops the pop-ups. Maybe someone else has a better way of doing it?

Nothing?

Same thing I was gonna say...sometimes you have to disable the floppy disk controller as well, but same idea.

So this is still burning me...I've already found a psuedo-fix for this problem, but now that's not enough. Here's the original post if you like: http://www.msfn.org/board/index.php?showtopic=44868&hl= Basically it's like this...when I test my multi-boot DVD everything is fine except during the first stages of the GUI install, I get an error about the Battery not passing Windows Logo certification. Now in the past I just included DriverSigningPolicy="Ignore" in my winnt.sif, and everything was great. But I'm trying to include a cherry copy of the OS so I can do a regular install as well...cover all my bases. So the unattended versions aren't a problem, but I just don't like the error on the non-unattended...any ideas? It's funny because I'm using a totally new source for the xp installations...btw, this is happening using winxp sp2, both home and pro. It seems like to me it has to do with the boot files then...I'm following the flyakite method. So maybe something in the txtsetup.inf? Problem is I have no idea what to look for! I did search through txtsetup.inf and came upon a few entries: batt.dll = 100,,,,,,,2,1 battc.sys = 1,,,,,,,4,1 battery.inf = 100,,,,,,,20,0,0 I've seen similar things like this when playing with BartPE, but I have no idea what this all means...is it even relevant? I checked the source files, and they are all included and look to be in original condition... I'm really lost on this one...anything? Thanx in advance!

I don't know if it's 100% legit, but MagicISO has a command-line version that they offer with the program that might do what you want it to. They even have a link to an updated version on their website that doesn't require registration or anything...I guess they just don't care or haven't noticed. The link is all the way at the bottom of this page: http://www.magiciso.com/tutorials/miso-iso-image-burner.htm Even if you have to buy it though, MagicISO is a nice program.

I think I see what you are saying. I forgot that UBCD's boot files just so happen to already be setup in a similar fashion.

I think the problem may be with the actual files for UBCD isn't only one folder deep...meaning, when you edit the XXXX.dat file, you are replacing I386 with whatever four letter folder you made containing the boot files. Now for UBCD, your boot files are actually X:\UBCD\I386...so you can't just replace I386 with UBCD cause that would lead to the root of the UBCD, not the actual system files...make sense? And since I don't think you can replace I386 with anything other than four characters, I think you're screwed. I can understand the want to organize, but your best bet would be to dump the contents of the UBCD dir into the root of your CD, and then edit the appropriate boot loader to reflect that...

What are you using as your 'boot menu'? CDShell, BCDW, etc? Also, what are you using to compile the ISO file? You might wanna post some more info...such as your file structure, programs used, configuration files, etc.

Good luck to ya mjc...I hope your app turns out as planned. I find it rather odd to see such strife in this post, even after reading all eight pages. Seems to me like there is a little bit of a p***ing contest going on here. All the programs here are indeed useful, but the problem that most seem to come up with when you make an Unattended Multi-Boot DVD, or any other contraption, is that you have to use multiple tools to create it. That in and of itself isn't a problem, but what happens when you get an error? You get bounced all over the place or flamed or just flat-out ignored. If you had one application that did it all, then the diagnosis portion would be extremely streamlined. If you need more beta testers then I'm game...got about fifteen different configurations I could load it on.

I don't know how or why, but I remember back in my warez days I would see a lot of folders that had the 'com2' structure...was something about being a very hard directory to delete or even see! The idea for the warez use was that the server admin would probbably not see it...also, it seemed like when we had one of those, we would have to go PAST that dir to get anywhere. Meaning, you couldn't browse through the folders, you would have to go straight to the intended folder. Guess that was another feature...you couldn't access the software unless you know the full path to it, which was usually only known by the crew.

In the I386 dir, there should be a small file named "setupp.ini". In that file there is a line that contains "PID=xxxxxyyy". The 'x' are a five digit code to signify the type of install (Retail, Upgrade, OEM), and the 'y' are a three digit code that tells setup what kind of CDKey to use. I found most of this info at: http://www.thetechguide.com/howto/setuppini.html I recently tried to 'hack' a Dell OEM CD into a Retail CD and it did not go well, but then again Dell alters a lot of the CD. Either way, that should be a good starting place...you could also google 'setupp.ini' and see what you get...and yes there are two 'p' in the file name.

Yeah...it's probably defective if it's not showing up in Device Manager...rip it out and see what ya get.

I don't know how to do it by default, but what I have is an "Explorer" icon in my QuickLaunch with this at the command: %SystemRoot%\explorer.exe /n, /e, D:\Temp I don't know what the /n, /e, does, but the last part (D:\Temp) is basically what you edit to tell it where to start it. So when I click the icon Explorer pops up and defaults to the previously mentioned location...I've sure there is a way to further hack this into the registry somewhere, but I don't know that part. Good luck!

Yeah, I say RIS is the way to go if you can afford it's software requirements. I've seen sites and applications that allow the same end result, but for vanilla compatability I would say a Microsoft provided solution is the best track. Also, the partition blanking that someone mentioned earlier is only a product of using the default settings of the unattended file for RIS installs. You can configure it to ask you about partitioning, and then have the rest unattended so all you have to do is boot it and do the blue-screen setup and then you're done. Since it's basically streaming the CD from a share you can install or boot various things. BartPE or ERD for instance, which makes for a very handy network diagnostic tool. Or, you can have multiple unattneded files for different types of installs. And you still get the added benefit of only having to edit the source files and not re-burn CD's or re-create image files. RIS is a pain sometimes, but it's pretty cool once you get it working.

Install Program, Start Program, File > Open, Select *.ISO To Open...that's pretty much it. I prefer MagicISO, but that's just me. The real question is what do you want to do to/with that .ISO file after you open it?

I've seen somethings somewhere about installing linux and then using some emulator to install Win98, but it was slow as hell. You can't install any Windows OS directly to the xbox, and so the only option is the previously menitoned emulation. You have to remember that the xbox, while very close to a PC, is still limited in many ways. The 733 is a Super-Celeron of sorts, and it only has 64MB of RAM. I don't think you could get any sound or video drivers for it either. Again, with those limited resources running in emulation its pretty much only for show and tell, not to actually use. There is a section of xbox-scenes forums dedicated just to this topic, and after a quick look everyone is just bitching back and forth and there isn't any real solid info. Here's the link: http://forums.xbox-scene.com/index.php?showforum=68 Good luck!

If you use nlite I seem to remember you can disable WinXP's check for minimum requirements...you'll have to rebuild the WinXP disk using this, and then you should be okay. I would format the drive though, as I and many others don't trust upgrades...especially from Win95! And be warned, I don't think you can do much with only 64MB RAM...let alone 16MB! Good luck!

I copied this from another post (Don't have URL) in which you can configure Nero to burn an ISO image. I would assume you can replace the syntax with another program but I could be wrong: Open Explorer/Tools/Folder Options/{File types}. Select the entry for ISO and click "Advanced". Click 'New' and name it "Open with Nero" In the Application area enter: "C:\Program Files\Ahead\Nero\nero.exe" "%1" Also, this isn't a registry file, but you could take a snapshot of the registry before and after and see what changes. Good luck!

Yeah...I'm a big Win2000 fan, and thankfully there is no built-in firewall...that's why it's the best! No bloat, no excessive services...smooth.

Yet another Group Policy to look into is this one: "Accounts: Limit Local Accounts Use Of Blank Passwords To Console Logon Only" It's under: Computer Config > Windows Settings > Security Settings > Local Policies > Security Options If you leave it enabled (Default) then any account that doesn't have a password cannot access the machine. Of course, you should have a password, but some obviously don't. Disable it to allow passage...