Jump to content

Alanoll

Patron
  • Posts

    5,494
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Alanoll

  1. UXtheme.dll is technically language dependant. Perhaps that should be said. BUt unfortunately I don't know how to fix it. Besides you searching the net for the bytes to change for SP2. The royale theme works because it's an official Microsoft theme (sort of) and doesn't require a hacked UXtheme
  2. well dang.... if they're gonna have a upgrade thing, then by golly, I"m gonna upgrade my "bronze". lol. Or I may buy an edition, just to buy it.
  3. It's all good. I typically stay around here too lol
  4. I"m just curious...... have you not been to the board lately? In most release scenes, this would be a "dupe" Look in the Windows XP forum, under "Needed Hack FIles". THere is a website linked with this info, ALONG with a program to patch it for you.
  5. I pseronally am looking forward to playing Half-Life in Source. That would make it quite entertaining. But it's not included with the ATI/HL2 bundle. CS:Source is quite fun though.
  6. YAY!! I maybe able to update my Mobility Radeon drivers now..... darn HP for being 4 months behind.....
  7. did you also add an entry to DOSNET.INF? and LAYOUT.INF
  8. hehe I change my screen at first logon as well. But i use the bootcfg route, but I have like 12 different screens on my CD, and the batch file randomly selects which to use.
  9. I should note, you don't need to create your own WINAMP.INI if you use this MSI. there is a switch XSKIN that all it does is set the skin= setting in the winamp.ini file. It puts WHATEVER you specify directly into that setting. So theoretically, if you new the name of the skin, you could put it there, and if present upon first run (meaning you could copy it just before you started Winamp for all it cares)it will use the skin, otherwise it will default to Classic.
  10. Xfull negattes all else (in terms of components). It supercedes XAgent and Xtray. As for the shortcuts....only thing that affects them are those switches.
  11. $OEM$ should along side I386 if you're doing a CD install, over the network, it should be within I386.
  12. REG ADD %KEY%\001 /VE /D "Adobe Reader 6" /f REG ADD %KEY%\001 /V 1 /D "%systemdrive%\Install\Applications\AdobeReader6\AdbeRdr60_enu.exe-P"-s/v\"/qn\"" should be REG ADD %KEY%\001 /VE /D "Adobe Reader 6" /f REG ADD %KEY%\001 /V 1 /D "%systemdrive%\Install\Applications\AdobeReader6\AdbeRdr60_enu.exe-P\"-s/v\"/qn\"\"" REG ADD %KEY%\003 /VE /D "TweakUI Powertoy" /f REG ADD %KEY%\003 /V 1 /D "%systemdrive%\Install\Applications\Powertoys\TweakUiPowertoySetup.exe /qn" /f Won't work. Period. Read the unattended site. If the file you have here is from the MICROSOFT site, it won't work. The other powertoys will, but this one is different. Download the MSI file that's in the guide, and use it. REG ADD %KEY%\005 /VE /D "Nero Burning ROM 6" /f REG ADD %KEY%\005 /V 1 /D "REGEDIT /S %systemdrive%\Applications\Nero\register.reg" /f REG ADD %KEY%\005 /V 2 /D "%systemdrive%\Install\Applications\Nero\nero60019.exe/silent/noreboot" /f should be REG ADD %KEY%\005 /VE /D "Nero Burning ROM 6" /f REG ADD %KEY%\005 /V 1 /D "REGEDIT /S %systemdrive%\Applications\Nero\register.reg" /f REG ADD %KEY%\005 /V 2 /D "%systemdrive%\Install\Applications\Nero\nero60019.exe /silent /noreboot" /f REG ADD %KEY%\006 /VE /D "FireFox 1.00" /f REG ADD %KEY%\006 /V 1 /D "%systemdrive%\Install\Applications\FireFox\Firefox Setup 1.0PR.exe /qb" Wrong swtich, and no spaces in the name. Read : http://www.msfn.org/board/index.php?showtopic=26240 REG ADD %KEY%\008 /VE /D "Office 2003" /f REG ADD %KEY%\008 / V 1 /D "%systemdrive%\Install\Applications\Office2003\TRANSFORMS=Unattended.MST /qb-" COuld have sworn you actually have to call SETUP. lol should be REG ADD %KEY%\008 /VE /D "Office 2003" /f REG ADD %KEY%\008 / V 1 /D "%systemdrive%\Install\Applications\Office2003\SETUP.EXE TRANSFORMS=Unattended.MST /qb-" As another note. Unattend.txt should be in I386 called winnt.sif , RunOnceex.txt should be runonceex.cmd and called through CMDLINES.TXT [COMMANDS] ".\RunOnceEX.cmd" Save CMDLINES.TXT in $OEM$ , and also put Runonceex.cmd in there as well. The Start /wait method will bring up a black dos box. You can change the size and color of the dos box, but that's about it. You won't be able to get it to look like the RunOnceEX window simply because that window is created by ierunonce.dll.
  13. Thread Closed. Obtain a legal key, then come back.
  14. second resolution... Don't buy an eMachine. lol.
  15. @prathapml I had such high hopes for you..... Knew we had to disagree on SOMETHING. lol. True, Windows ME does have a few bugfixes Windows 98 needed. However, it was based off of an unfinished Windows 2000, and then altered to work with the 9X kernel. It you work hard enough, you will find MANY more bugs in ME then in 98 simply because of the transition of kernels. 98 is far more stable for longer period of time. And I personally rather have real-mode DOS then what's in ME. 98 may have a few bugs, but they're not kernel based. ME has a newer driver set to start, but who uses the defaults for most of their hardware anyway? System Restore could come in handy, but it rarely worked correctly in ME, and wasn't fixed till 2000 was released and then "perfected" in XP. But alast, I can not vote for Windows 98. I still have it on one system, because it's the only one that can still play my old DOS games, that REQUIRE DOS. Even XP compatibility doesn't work. and ME doesn't have a real dos. the game cannot even be run in a WINDOW. I vote for Windows 1.0. Well technically the version of windows Microsoft bought and then changed it's name. But of the options, I vote 98. I have ME full retail lying around somewhere, but since the 6th test run, it hasn't graced a system.
  16. kernel - ALL images are 16bit. the original artist just did a really good job picking colors wisely. You weren't so fortunate. 16bit are the highest possible simply because the video card drivers aren't loaded, and the system is using VESA mode. logonui - If you're comfortbale with XML and HTML, open up the EXE file in a resource editor, like Resource Tuner. Not a HEX editor, but a resource editor. Open in the UIHost object. Puruse through till you find the top and bottom sections. I don't have an editor currently installed on this system, but I remember ID tags. There;s a hide attribute that you can set. I'll come back in the morning (just past midnight here) with more details hopefully.
  17. let the stalking begin...... wait, I already do keep an on a couple members......
  18. Nice copy paste job from the Microsoft Website. ;-)
  19. Man....it's good beign right As for classic, I think it's /S. Not sure, I have 2.43 somewhere, ir 2.42 one of the two (before 3 came out and it became classic) and i remember seeing wise on it. But it could very well have changed since then.
  20. you should be able to use just /qb on the commandline.
  21. have you tried either or? perhaps your modifying the hex wrong?
  22. Orgname should be in quotes. Components is spelled wrong. You could also try moving the UserData section above the Display section.
  23. anyone try a Silent search? Last few ACDSee packs have been Windows Installer, NOT InstallShield.
  24. I vote the man tried to add his RAID/SATA drivers using the MassStorageDevice method....
×
×
  • Create New...