drmarvin

Just curious if anyone knows about problems when upgrading from a single to a dual core chip (same type). Is it required to reinstall Windows when changing a CPU in this fashion? Does it require a new HAL? Thanks DrMarvin

Use the wizard, or once you have create your VM, you can select Add, and use the wizard to create a virtual hard drive. VM Ware works beautifully for testing unattended CD's.

You can start the script in a number of ways. Good examples are the same as for XPlode (http://www.msfn.org/board/index.php?showtopic=15076), but I choose to start minhe with [GuiRunOnce] in the winnt.sif file. I haven't tried it any other way, but I figure any other way will work too. This is the command line that I use in the winnt.sif file: [GuiRunOnce] "%systemroot%\system32\cmd.exe /c cscript /nologo %systemroot%\wpi.vbs" This works because as I said before, I put the wpi/vbs script in the $OEM$\$$ directory under each OS. Then it works, and you just have to change the one post-install directory on the DVD.

Also, I have foudn that using Hmonitor, using the throttling feature, I can make it stable with the Radeon card, but it seems with other testing, the onboard video and a Kyro2 64megKyro2 64meg are stable without throttling, figuring it may be a problem with my Radeon card in this system. The card works flawlessly in my slower system, but the jump from an Athlon 650 to a P$ 2.8gig seems to be a problem.

Thanks for the replies. I have compe to the conclusion that it's a cooling problem. I believe that initially, it was a power supply problem, but that was rectified. Now I just have to plan out a good cooling option, since I think the freezing is from overheating.

I'm at a loss of what is wrong, with my new system, so I thought I'd throw it out there to the experts. The following is my prediciment. Brand new Soyo SY-P4VGA ATX P4 motherboard, BIOS flashed to most up to date (happened before flash too) Brand new Intel P4 2.8gig non-Prescott 512k cache Brand new 512meg DDR PC333 ram Board has onboard Audio, S3 video, and Ethernet Also have tried with my ATI Radeon 9000 Pro, Promise ATA 133 card + hard drives Symptoms occur with any configuration, even with just onboard equipment and hard drive. The computer is stable if very little is going on, but if you get it to do more than about 1-2 things at once, or anything graphical, this go down the tubes. The computer freezes all the time, for no obvious reason. The temperatures seem fine. The heat sink is mounted with thermal paste and the stock fan. No fan on the mainboard chip, but heatsink is in place. Now when looking at the temps with HMonitor, it looks like the mainboard may be heating up (say 74C in red) and the heatsink definately feels warmer than the one on the CPU. I have a feeling this is what it is related to, but I'm not sure. I have replaced the RAM to no avail, so I am looking for some input into what you think the culprit is. New Mobo? New CPU? I want to play with my new faster toy, so any help would be appreciated. Thanks Dr Marvin

Then the next thing to figure would be the DVD writer. It may be saying it's writing ok, but there may be small errors, especially if it is reproducable on other computers. The other thing to check would be the RAM with ramtest86, since this is where I got many errors on my system. One of my SIMM's sucked, and had a massive number of errors in it. Try copying the files to a different computer and building the ISO there and burning it.

You don't quite have the syntax for the line correct. it should be the following: cmd1[pn]=['cdrom','setup\\xp\\progr\\Office2k3pro\\SETUP.exe......'] In your case, though, you should actually have the following: cmd1[pn]=['root','setup\\xp\\progr\\Office2k3pro\\SETUP.exe......'] or: cmd1[pn]=['cdrom','progr\\Office2k3pro\\SETUP.exe......'] (I think...) The difference between 'cdrom' and 'root' is that 'cdrom' uses "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sourcepath" as the CD root, and 'root' uses just the drive letter from that. These differ because it's an all in one disk.

More than likely the error is supposed to be "Cyclical redundancy check failed". This usually happens when there is a scratch or something on the disk. I think it means that the error checking written in the disk is noticing that a file is not the same, and therefore errors out. The only way I know to fix that is burn a new disk. Good luck with that.

I don't know if anyone else would fine this useful, but I thought I'd offer what I had. When you make a Multiboot DVD, you most likely have the same stuff to install on most OS'es. Of course, you can make $OEM$ folders in each OS, and after optimization, there is no extra space, but if you make a change, you have to manually change all of them. Therefore, I came up with the idea that I wanted to have a Preinstall dir in the root of the DVD, and the Installer in the root also. The problem was of how to start the program off the CD. With this VBS script, you can put just this file in your $OEM$ directory (I put it in \$OEM$\$$ just for convenience). My exaple uses WPI (http://www.msfn.org/board/index.php?showtopic=28125) especially because it uses easy CDROM variables, but I guess it's no problem to use it with XPlode or something. The script uses the Sourcepath reg entry, but the problem was that on a multiboot DVD, the Sourcepath was not the DVD root. This fixes that problem. Feel free to hack and change, I just hope it's useful to someone else. Dim WshShell, testpath, key, fullpath, sliced key="HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sourcepath" Set WshShell = WScript.CreateObject("WScript.Shell") testpath=WshShell.RegRead(key) sliced = testpath.slice(0,2) ' change "wpi\wpi.hta" to whatever your path on the DVD is for your program fullpath = sliced & "wpi\wpi.hta" WSHShell.Run fullpath

Thanks so much, Raja, that was perfect, now I'm in business. Cheers

I am having a little trouble using VBS to parse a reg entry for me. I'm attempting to have this file launch WPI, because I only want to edit WPI config in one spot on my Multiboot DVD, so I have a VBS file in the $OEM$\$$ dir, so it's easily accessible, which then is launched from [GuiRunOnce], which in turn runs WPI.hta. I am attempting to have the VBS file read and parse "HKLM\Software\Microsoft\Setup\Sourcepath", but since it's a multiboot DVD, it's not just "d:\", it's "d:\setup\xp\pro". Therefore, I want the script to cut off the end, after the first 3 characters. My research suggests that the string.slice method should work, but it gives an error that "Object Required." My code is the following, so if anything might help to make this actually work, I'd appreciate it. Dim WshShell, testpath, key, fullpath, sliced key="HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sourcepath" Set WshShell = WScript.CreateObject("WScript.Shell") testpath=WshShell.RegRead(key) sliced = testpath.slice(0,2) fullpath = sliced & "wpi\wpi.hta" WSHShell.Run fullpath I know this reads the reg key fine because my previous code used the path, hence my previous debugging. The following looks for the file in "d:\setup\xp\pro\wpi\wpi.hta" instead of the required "d:\wpi\wpi.hta" Dim WshShell, testpath, key, fullpath, sliced key="HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sourcepath" Set WshShell = WScript.CreateObject("WScript.Shell") testpath=WshShell.RegRead(key) fullpath = testpath & "wpi\wpi.hta" WSHShell.Run fullpath Thanks in advance.

If you are talking about BackOffice 2000, I understand it's only 5 CD's which should be no problem to fit on one DVD. If there is another BackOffice, I'm not aware of it.

Just an update. It ended up that the reason it wasn't parsing the winnt.sif was because I forgot to hex edit the SETUPLDR.BIN to point to the new boot folders. Now it seems to be working fine. Thanks for the help though.

Well, it's a multiboot disc, so the guide says to put it in the boot folder for that option. I don't want this one to do an OEM Preinstall, but should I still make that switch "yes" and just not have an $oem dir in parallel? EG. root ----pro1 -------no winnt.sif ----pro2 -------winnt.sif with Unattended, but not OEM Pre ----pro3 -------winnt.sif with Unattended and OEM Pre ----hom1 ----hom2 ----setup --------xp -----------pro --------------i386 -----------home --------------i386