flyakite

There was a file called findcd.exe that I saw included in a bootdisk once. Running it set's the %cdrom% variable to your cdrom drive. You could include it in your $OEM$\$1\install directory. Then, it will get copied to your C:\install folder during guisetup. From there, just have your batch file run %systemdrive%\install\findcd.exe to set the %cdrom% variable.

For those of you wanting to install Microsoft Office 2003, it is the same process listed on the guide here. And of course, you need the Office 2003 Toolkit, not the XP one. EXCEPT: You MUST complete step 8. Choose "Configure local installation source". Enter your key with NO hyphens or dashes. And check "I accept the terms in the License Agreement". This step is not needed for slipstreamed Office XP installs because the slipstream somehow disables the need to enter the key. However, with 2003 that is not an option yet so you MUST complete that step, or it will never install. It took me a true hard drive install and 2 VMware tests to finally figure out why it wasn't installing.

No, see, you don't understand. Deleting from a batch does not work because the font that is used in the .bat and .cmd windows does NOT support the 'ñ' character. So therefore, when I tell it to RD, RMDIR, or DEL C:\ñ it can't see the 'ñ' character. It is for sure an empty folder, and what's interesting is the apps I have on my unattended cd are the same ones I install normally. Nothing new. So I'm curious as to what is creating that folder. It's not a big deal, I was just wondering if anybody else had run into that before.

Yeah I know I can delete it manually, lol. But I'm curious as to why it's there. I wondered if anyone else has run into that before. No it's not hard drive corruption of any sort considering it happens in Virtual PC and VMware as well.

I've had this problem ever since my first unattended cd. After Windows starts up for the first time, there is an empty folder in the C:\ called ñ. So, C:\ñ I have absolutely no idea what program or process has created that, and I can't get rid of it through a batch file, since batch's run through a dos command prompt and the font the command prompt uses does not support that character. Does anyone know of any other way to delete it? Or, what in the heck is creating it in the first place?

There's no entry in their start menus for the program? What if you manually went into the Program Files directory and tried to run it? What happens then?

AWESOME! Thank you for that. That is the ONE thing that bothers me about SunJava more than anything else. I hate that stupid tray icon always popping up.

Yeah, CDIMAGE 2.47. It says copyright 1993-2000. I'm curious as to why there isn't a newer version or anything. I mean, it's been 3 years, lol.

Another note you might find interesting willpantin, when I made an image of a 4.4GB folder in UltraISO, it made me a 4.4GB iso. When I made it in cdimage, it made me a 2.56GB iso, which, when burned to a DVD, truly only used up 2.56GB worth of space! (and everything works like a charm still) So now I can actually add my $OEM$ folder to my DVD without having to worry about a 2 cd install! (which is a PAIN)

Thanks Ryan. I never check the switches thread anymore, there's just too much **** info in there. And the search feature on here is a little qwirky at times.

Exactly how do you install this silently? Every Java release since 1.4.1 is not extractable, so I'm not quite sure what to do with this.

start D:\XPCD\cdimage.exe -lXP2K98 -t08/23/2001,09:00:00 -bD:\XPCD\ROOT\loader.bin -h -n -o -m D:\XPCD\ROOT C:\XP2K98.ISO That is the current command I use to make my image. It is all on one line of course. "D:\XPCD\cdimage.exe" - change to the location of your cdimage.exe file "D:\XPCD\ROOT\loader.bin" - change to directory or your xpboot.bin file (mine is loader.bin because I use a 10 OS multi-boot dvd) "D:\XPCD\ROOT" - change to the root folder that all your files are in "C:\XP2K98.ISO" - change to the name and location where you want your ISO file created Also: I placed this into a file called makeiso.bat and that way when I make changes to my folders I just delete the old ISO and run the .bat file to create a new one. And if Virtual PC 5.2 is causing you problems, try VMware 4.0.5. I like it more than Virtual PC, although each one gives me a couple of problems depending on what I'm trying to do. Oddly enough, if something doesn't work for me in VPC, it does in VMware, and same the other way around.

Um... yes, they did. Use cdimage to build your ISO and it should work just fine. Also, in Virtual PC, create a PC that runs XP with 128mb. Don't choose 'Other'. I"ve captured 4.4 GB (yes, gigabyte) iso files in VPC and never had a problem. If it doesn't work, I also recommend VMware 4.0.5. I have had different problems with each, so if something doesn't work in one, I try it in the other, and usually it works. Odd, I know. Also, just in case: Do NOT try to use your iso file as the Hard disk image. Create a new pc through the wizard, don't use default. Use 'Guide Me' and create it to run Windows XP. Then, start up the pc and in the CD menu choose 'Capture Image' then reset the PC. It's worked for me too many times to count.

Umm... the DirectX 9.0b OPK .exe file that was posted here before is only 11.2 MB in size, and installs with no switches, so I'm not quite sure what the point of this method is.

Australia? That's all. I don't know if that's enough. But anyway, some people that know of www.MSFN.org don't necessarily know about the entire tutorial on how to create a complete cd. Read about it here. If you have read that already, then you bypassed some information. It tells you how to add applications and where to keep them on your cd as well as what to do with your 'winnt.sif' file and all that good stuff.

Also, is I386 in the root of your cd? If so, is $OEM$ parallel to I386. In other words, both folders can be seen at the same time?

No it's the same in essence. And I figured out what was wrong. It's a problem within Virtual PC 5.2. What exactly, I don't know. But I know that once I switched to VMware 4.0.5 everything has worked flawlessly on test runs.

No problemo . By the way for anybody wanting to test their CDs without actually burning a cd, I seriously suggest using VMware 4.0.5 for testing purposes, instead of Virtual PC 5.2. Switching has fixed many issues I've been having with my DVD.

Add this section to your unattended file for the classic theme [Shell] DefaultThemesOff = Yes This registry tweak forces Classic Control Panel: ;Force Classic Control Panel [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "ForceClassicControlPanel"=dword:00000001 The other I don't know about.

Interesting..... I rebuilt my iso in CDIMAGE and decided to give VMware 4.0.5 a try. What do ya know, it works fine now. By the way, I think VMware 4.0.5 is sooo much nicer than Virtual PC (at least until Virtual PC 2004 is out). It allows you to configure many more options, and now gives me a chance to test out my 2 disk setup, without having to burn a single cd!

Well my Nero only has .nrg listed in the drop down box, lol. BUT, I was looking online, and I recommend checking out UltraISO. It's like WinISO, but better. It also supports directly burning to Nero through the program. Just click a button and that's all you have to do. You can check it out here.

Sent. Let me know if you get 'em.

I've ran into this problem. From what I've seen it generally happens when the correct OS identification files (win51ip, win51ic, etc.) is not found in the root of the CD. As a precaution, I would also keep copies of those files in the setup folder of your OS if you have a multi-boot OS cd. That may or may not fix this problem.

Well, what about MsDosInititated="0" Did you change that? In that thread that was the real problem. You have Inititated, which is not a word. It should be Initiated.

How exactly do you make an ISO in Nero 6? I have only been able to make .nrg images, not iso.