MSFN Forum: Unattended DX9.0c on Win 2000 - MSFN Forum

Jump to content



Unattended CD/DVD Guide Homepage · MSFN Forum Rules

Welcome to the Applications Installs forum. Make sure you read the forum rules before you start posting.

Links/Requests to warez and/or any illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated.

We try our best to keep this forum clean of illegal content. If you see any illegal activity use the "report" button you find in every post to report the specific post to the moderators. If you ignore any of the rules you will be banned without notice.

Read Forum Rules
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Unattended DX9.0c on Win 2000 Rate Topic: -----

#1 User is offline   NoUTurn20 

  • Newbie
  • Group: Members
  • Posts: 34
  • Joined: 18-March 04

Posted 30 July 2005 - 03:58 PM

I have tried to integrate a silent install of DirectX 9.0C into my unattended Windows 2000 but so far have been relatively unsuccessful (I have SP4 and SR1 for SP4 slipstreamed). I have tried both a .bat file run from GUIRunOnce and via cmdlines.txt. I extracted the redis package and have been using the switch dxsetup.exe /silent. I have also attempted to use the /install switch alogn with /silent but always get an invalid switch error. When using the .bat method I get memory errors during install. When running it via cmdlines.txt I don't get any install errors but either running it via .bat or cmdlines.txt when I run dxdiag in windows I get an error about GDI32.dll and User32.dll. I searched around on google and found If I replace to files d3d8thk.dll and dinput8.dll with alternate ones from the .cab files those errors do go away. If I do a regular install using the same redis package (Aug 4 2004) with no switches I don't seem to have this problem. Perferably I would like to use the cmdlines.txt method and stay away from using any hex edited setup files etc... If any one can shed some insight it would be appreciated.


#2 User is offline   blinkdt 

  • Somewhat Knowledgeable
  • PipPipPipPip
  • Group: Members
  • Posts: 582
  • Joined: 30-September 03
  • OS:Vista Ultimate x64
  • Country: Country Flag

Posted 31 July 2005 - 01:52 AM

Quote

Perferably I would like to use the cmdlines.txt method and stay away from using any hex edited setup files etc...

I don't think that's doable. I'm sure you have read THIS THREAD, which dicusses the no-ifs-ands-or-buts necessity of editing the dxsetup.exe file for a Win2K install. This has been an issue for DX9a, DX9b, and DX9c. My RunOnceEx.cmd for Windows 2000 Advanced Server:
@Echo Off

SET PP=%systemdrive%\Install

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Applications" /f

REG ADD %KEY%\060 /VE /D "DirectX9c" /f
REG ADD %KEY%\060 /V 1 /D "%PP%\DX9c\dxsetup.exe /install /silent" /f


You can grab the 42.05k dxsetup_new.zip file at the end of page three of the thread mentioned above. I'm just thankful that nxskingdom made it available.

I'm using TommyP's integration method for most of the install work (try it, it is truly fantastic), but using the "/Q:A /R:N" switches as Tommy suggested together with nxskingdom's IExpress guide to pack a switchless silent DirectX9.0c installer did not work for me. Tommy didn't indicate that I needed to use the hex edited dxsetup.exe, and so maybe I shouldn't have. Or maybe I really did need to use the "/install /silent" switches despite Tommy's admonishments. Dunno. Anyway, it's done: I use the hexed dxsetup.exe file together with the /install /silent switches from cmdlines.txt as indicated above and all is well. And since it is installing from cmdlines.txt, I can always remove it easily to cut bloat.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy