azaze1

Member
  • Content count

    61
  • Joined

  • Last visited

Community Reputation

0 Neutral

About azaze1

Contact Methods

  • AIM
    azazel dot us
  • Website URL
    http://
  • ICQ
    46247206
  • Yahoo
    Lord_Azaze1
  1. Is there a reason why the resolution setting would fail to work when installing inside XP Pro versus XP Mediacenter or Server 2003 ? This never used to happen UNTIL I used the RyanVM post SP2 update pack. Granted that does not modify anything inside WPI, however I use the exact same WPI folder for all of my OS installations by way of junction points so I know for a fact that the WPI folder contents is identical, yet in XP Pro it remains @ 640x480 despite the fact that I have configured WPI to run @ 1024x768. Inside XP Mediacenter it switches to 1024 upon launch, same with Server 2003. XP Pro doesn't. Strange.
  2. I did this to the Royale theme (since I'm too impatient to wait for the author's rerelease). It didn't work. It still complains that it is not a 5.5 compatible theme.
  3. *sigh* that was it. I guess I thought it was relative to the path of where wpi.hta was called. My bad
  4. Here's another much easier way to produce the failure. I created a batch file in the WPI folder called WPI.cmd In it: I simply have WPI.hta options=useroptions_int.js Now... when in windows, and I double click on wpi.cmd: it launches just fine. When I type <path to wpi folder>\wpi.cmd at a RUN box, it launches just fine. However, when at a command prompt and I type <path to wpi folder>\wpi.cmd it FAILS with the same complaints of no glossy theme. I also tried (from a command prompt) to launch WPI.hta and passed the options=useroptions_int.js and it failed again with the No Glossy theme error. So when run from a command prompt environment and not within windows explorer, it doesn't parse the options= variable and looks for the default useroptions.js which, in my case, does not exist. So it uses what would be default values upon creating one which uses the Glossy theme. Again in my case that folder doesn't exist anymore as I only use the Royale theme. The root of the problem is that it doesn't parse the options (or most likely any other value) properly when run from a command prompt. Just try it.
  5. I tried calling mshta and pointing to the complete path of wpi.hta and the same problem occurs.
  6. When my useroptions.js file is named a certain way, WPI fails to launch via GUIRunOnce (as it is called with an entry in winnt.sif) The error says: 'Glossy' theme does not exist. Switching to 'Glossy', the default theme. Now the funny thing is, is I do NOT have a glossy folder in my Themes, nor is my useroptions configured to use the Glossy theme. I use the Royale theme. Here is how I can reproduce the error. Rename useroptions.js to useroptions_una.js Make a new string entry in your HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce make its value the complete path to your WPI.hta with options=useroptions_una.js It should fail to load the next time you log in. Now, if I rename the useroptions_una.js back to useroptions.js it will work. OR, if I call WPI with the options=useroptions_una.js from the windows' run box, or from command line, it will work just fine. The only time it doesn't work is when WPI is called from the GuiRunOnce. Finally, when I copy my Royale theme and name the folder "Glossy", the WPI launches okay but it completely ignores the useroptions file. It instead loaded a default useroptions template with a default timer (mine was 300 seconds and it launched with roughly 30 secs remaining). So something is not working right when WPI is run from GuiRunOnce with an options= value provided and it generates a default file or something and that explains why it looks for a Glossy theme and complains when it's not there.
  7. How do you remove the extra buttons now that the option is no longer there?
  8. I'm having a strange issue on my system with buffered writes. According to benchmarks, my buffered writes are only 51 MB/sec. This is incredibly slow for a 3 drive SATA 10,000 rpm RAID 0 array. In fact, the very same program (PC Wizard 2006) on my workstation at work scores 162 MB/sec which is just a single 250 GB Seagate SATA drive @ 7200 RPM. Why would a 3 drive raid with 16MB buffers @ 10,000rpm be performing 1/3rd the rate of a single 7200rpm drive with an 8MB buffer? For the record, I have installed the nForce 590 drivers.
  9. I'm not posting this to point fingers in a negative way, but you started by saying this is going to be done by editing txtsetup.oem. It is even referenced twice, but then you specify editing the built in txtsetup.sif. In which case this method is covered already in the Drivers forum. It would be nice to just drop your drivers and 1 new text file into the I386 dir.... but that can't be done as initially suggested at the beginning of this post. Oh well.
  10. I always do. In fact I even removed all partitions from the physical drive and did a slow (not quick) format just to be on the safe side. Didn't make a difference.
  11. I've got a strange problem affecting only one machine (my own workstation). Let me say first of all that I'm using a multiboot environment, so my SetupSourcePath for XP Pro is \SETUP\XP\Professional\ For whatever reason, when I burn my unattended ISO, I get a TON of file not found errors at the start of GUI mode (T-39 minutes). It allows me to browse for the file, and upon doing so it shows me that the path it is looking for is my cdrom drive's root. In my case H:\ I could never figure out WHY it is doing this when I have my txtsetup.sif setup correctly, and any ISO I burn works and installs just fine on every machine at my work. When I try it on my home machine, I have to type H:\SETUP\XP\Professional and copy it and paste it about 200 times to get through a window install. Upon further investigation after install, I notice the following my my C:\WINDOWS\system32\$winnt$.inf [Data] floppylessbootpath=no producttype=winnt standardserverupgrade=no winntupgrade=no win9xupgrade=no win31upgrade=no sourcepath=\device\cdrom0\SETUP\XP\Professional\ AutomaticUpdates=Yes AutoPartition=0 MsDosInitiated=0 UnattendedInstall=yes dospath=H:\ EVERY single other machine has these two paths matching as it should. This is why (on my home machine only) I cannot get windows installed properly when the I386 dir is not at the root. Any ideas as to why this is happening?
  12. Fernando 1, I'm about to attempt an ISO for a nForce 590 raid setup, but I'd just like to clarify one thing based on some confusion from reading different threads: Should the contents of the $OEM$\$$\OemDir folder contain ONLY inf files from the SATARAID folder, or every file from that folder, or just specific files? I ask because I dont plan on using nLite. I've never used it and I don't want to start (nothing against it I just like knowing what happens under the hood so I do it all manually). I've included three other massstorage drivers manually and I wanted to do the same for the nForce 590 RAID. The confusion on the contents of the OemDir folder comes from a different thread that suggests the only thing that should go into the OemDir folder is files other than .inf .sys or .cat. In other words, only .dll .vxd .cpl or other files should go in OemDir. Does that hold true in the case of nForce raid drivers or in light of the [OemInfFiles] section which was not part of the do-it-yourself massstorage guide.
  13. I had this problem too and thought I'd get rid of it with a few lines using AutoIT It works beautifully. Just compile this to an exe, and make it the first thing you run via CMDLINES.TXT (if you have batch scripts running before GUI setup is complete). ALSO, make it the first thing run via GuiRunOnce if that is how you start WPI (most do). While 1 < 10 WinWait("C:\WINDOWS\") WinSetState("C:\WINDOWS\system32\cmd.exe", "", @SW_HIDE) WinSetState("C:\WINDOWS\SYSTEM32\cmd.exe", "", @SW_HIDE) WEnd IMPORTANT NOTE: You must launch it via a batch script itself so that the install doesn't hang waiting for the autoit script to terminate. Because this is going to run until reboot (or until forcably stopped) you need to launch the exe in a batch with something like @ECHO OFF start %SYSTEMDRIVE%\INSTEMP\CMDHIDE.EXE EXIT
  14. Here is one of my logs. WPI Installation Log File Install process started at: Saturday, July 08, 2006 8:50:03 PM List of programs to be installed: .Net Framework 1.1 SP1 CPU-Z 1.35 Java Runtime Environment 5 O&O Defrag 8 Professional SysInternals Core Applications Microsoft Office Professional Edition 2003 SP2 Nero 7 Ultra Edition 7.2.3.2b WinRAR 3.51 Tweak UI for Windows XP AnyDVD 6.0.1.1 CloneDVD2 2.8.9.9 Picasa 2.2.0 QuickTime 7.1 Windows Media Player 10 XP Codec Pack 1.3.4 Google Toolbar for Internet Explorer mIRC 6.17 uTorrent 1.6 Symantec AntiVirus Corporate Edition 10 ----- Saturday, July 08, 2006 8:50:04 PM Program: .Net Framework 1.1 SP1 UID: DOTNETFW1 Order: 000105 Category: System Software Saturday, July 08, 2006 8:52:56 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\DNFW\dotnet11sp1.exe" Saturday, July 08, 2006 8:52:56 PM Finished installation ----- Saturday, July 08, 2006 8:52:56 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:54:27 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:54:27 PM Finished installation ----- Saturday, July 08, 2006 8:54:27 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:54:39 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:54:39 PM Finished installation ----- Saturday, July 08, 2006 8:54:39 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:54:51 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:54:51 PM Finished installation ----- Saturday, July 08, 2006 8:54:51 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:55:04 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:55:04 PM Finished installation ----- Saturday, July 08, 2006 8:55:05 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:55:16 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:55:16 PM Finished installation ----- Saturday, July 08, 2006 8:55:16 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software Saturday, July 08, 2006 8:55:29 PM cmd1 Success (returned code 0): "C:\INSTEMP\APPS\JAVA\jre507.exe" Saturday, July 08, 2006 8:55:29 PM Finished installation ----- Saturday, July 08, 2006 8:55:29 PM Program: Java Runtime Environment 5 UID: JRE5 Order: 000180 Category: System Software
  15. Very strange problem now. Upon clicking Install, it fails on random applications and loops endlessly, marking failure "X" symbols next to each application. So if app 2 succeeds, but app 3 fails, it'll mark a red "X" next to app 3, and move onto app 4 (at least the GUI says it has moved on) but it retries app3. I can tell because I see it extracting the same package over and over again, and beginning the MSI based setup with the title window. It fails within a second of launching the MSI, then marks a red "X" next to whatever application is next in line, then retries etc. This literally never ends.