Tripredacus

New topic next time huh? The fact that PEIMG said it went in doesn't mean it will work. It does not test for compatibility when installing this way, but it just puts it in the folder. Since no hardware profile is loaded when you do offline editing. You'll have to test it out yourself to see if it works.

I don't believe you can. You can, alternatively, mount the WIM, put the updates in a folder someplace, and edit your SYSPREP.INF (or load the registry hive to use RunOnce) to install the updates when the computer boots up after redeploy. Then you could have an additional program (if you so desired) that would delete the updates after you can confirm that they were run, idea script: IF reg entry exists for kb_x THEN del c:\updates\kb_x

Are you trying to inject these into an XP image or a WinPE?

Changed Identity back to NETWORK SERVICE (default). Attempted to install hotfix, but it failed (newer version already installed). Made cross-post in 2003 forum. Made cross-forum post on DevShed's IIS forum. I am effectively waiting for help at this point, unless I dream up something over the weekend, i'm spent on this issue.

Does your RAID controller have software that records array errors at all?

You might want to run Filemon and then open Outlook to see what its doing. You can specify to just monitor outlook.exe as a filter so it won't show you everything else.

SO you have a program that makes the changes in MSCONFIG? What happens if you go into MSCONFIG yourself and switch it to normal startup?

On any systems where I've had the chance to do an SP3 upgrade (rather than an install with SP3 built-in) I did notice an increase during the boot process. No other things tho. We decided not to continue evaluating SP3 so I haven't done a lot of testing with it.

I believe that there hasn't been sufficient time or usage of Vista 64bit to determine whether or not its truly more stable than 32bit. We do, however, know that x64 is more stable than x86 in prior versions of Windows, like XP, 2000, 2003, etc. I still believe that Vista x64 adoption isn't as high as it should be, since all further Windows releases will be 64bit. You'd figure that besides merely offering 64bit for each type, that only certain versions (like Business for example) would be 64bit only, in an attempt to get companies and developers to start adopting it. It is going to be a major problem when 64 suddenly becomes the only option, and I don't think the period of time offered by the Downgrade Rights program is long enough for a reliable development cycle. Sorry to derail.

Wasn't there a reghack you could do to fool Windows Update to think you already had an update installed when you didn't? I seem to remember reading it because someone had an update that was installed already and kept showing up to be updated...

Well you could also get those bootleg cars from China. I forget the name of the company now, but I do know the story behind them. A few years back, GM closed a bunch of plants in China. The workers there had kept copies of all the designs and duplicated all the machinery and re-opened the plants. They then started making bootleg GM cars. Like they looked like the same model as current or near-current GM cars but they had their company name on them. They said they had an SUV (it looked like the big Cadillac one) that got 60mpg (converted estimate) and they were showcasing them at a car show in Singapore or someplace. They were showing them off and one guy from the company said they are selling pretty well in China but they can't export them because the car makers in the US are blocking their attempts to sell them in the US. The guy laughed saying how they were too much competition for them to handle or something.

After much troubleshooting, I have determined that my install of PHP is causing IIS to crash on either boot or a service restart. My original problem(s) did not (always) include this issue but I found it to be the source the further I went. I am out of troubleshooting options that I can find online, so I am reaching out here. I have installed the Hotfix for this issue but it said it can't install because my Service Pack version (its 2 not 1 as in that thread) it newer and there is no need to do the install. There are two behaviours I am experiencing: 1. If the PHP.INI is in the correct folder, IIS crashes when it tries to start the service. IIS then resumes but only ASP and HTML works. 2. If the PHP.INI is NOT in the correct folder, IIS does NOT crash. PHP works but only on default settings. Any ideas?

Back again after a great conversation about Vista commercials... Its a nice day outside today! It's 77 degrees at my desk! AHHH! unremark doc_root in PHP.ini. Restart IIS. Take PHP.ini into dev folder again. Restart IIS. PHP is working with no INI file again... So I can confirm that now IIS is looking for the correct place for the PHP.ini, but it can't start properly. Looking over the file itself, there isn't anything that appears wrong with it, and if so I've documented all changes I've made to it in this thread. Filled out the MySQL credential information. restart IIS. PHP failed. Moved file to DEV. Disabled SSL extension. Restart IIS. Added override for all websites (even though there are only 1) for Execute Permissions to Scripts Only. restart IIS. Changed this line: extension_dir="c:\program files\php\ext\" restart IIS. run PHP. Commented out all the extensions that PHP said it couldn't load. restart iis. Running PHP from the command prompt now does not give any errors but PHP still isn't working. Each time I'm restarting IIS, W3SVC is crashing still. There are no new Crash Dumps reported by the debugger. On to troubleshooting the event. Oops my bad, the debugger was disabled. Turned it back on and restart IIS... This bug is referenced here: http://bugs.php.net/bug.php?id=38111 Hotfix available (can't find it) http://support.microsoft.com/kb/892988 Changed Local App Pool to Local Service. Restart IIS. No user dump created. Service Unavailable message in IE. Change to Local System. Restart IIS. Blank PHP. New event: Specify Account: IWAM_DS1-SKYLYNX. Crash Dump created... Specify as Administrator... I'm going home...

Hmmm well PHP is totally down right now and I've got a lot of errors. Some came back from before. Here we go again! Error_01 Application Error Faulting application w3wp.exe, version 6.0.3790.3959, faulting module w3core.dll, version 6.0.3790.3959, fault address 0x000201b4. Error_06 W3SVC (1009) A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '3492'. The process exit code was '0xC0000005'. That's it in the Event Viewer. Obviously the W3SVC is causing an error again, that had previously gone away. I am to examine the crash dumps now to see what they have in store for me. There are 3 new IIS mini-dumps that were created since last time I checked this, but they are all from yesterday, not since the last reboot. For a hunch (so far 1-2 on hunches) I am going to take out the php.ini from the PHP folder to see if PHP comes back or not. If you remember, when I put the php.ini in the Windows folder, PHP also did not work again. I stuck it in PHP\DEV for now. Restart IIS. RESULT = PHP works again... There was another thing I saw mentioned on another website before I rebooted. I forgot to bookmark it but I think I can do it again. Comment out this line in PHP.ini and put back into PHP folder. ;doc_root = C:\Inetpub\wwwroot Restart IIS. Now PHP still works and the php.ini is in the correct folder. No config was loaded and config file is looking in the wrong place. Test, put php.ini into c:\windows. Restart IIS. Change Environment variable for PHPRC to C:\WINDOWS. Restart IIS. Verify no change in Firefox. Firefox shows nothing. Only IE shows this or any PHP page. Verified localhost is a Trusted Site. Add everyone read permissions on c:\windows\php.ini. Restart IIS. Modify the following registry entry to: restart IIS. PHP is broken. Remove PHP.INI from C:\Windows and reset environment variable. restart IIS. issue: IE was caching the page. PHP had stopped working and I had not known it... PHP still broken... No IIS crashes or hangs. Need to backtrack now. Taking a short break.

Another hunch. Disable Trend Firewall. Nope. Re-enable Firewall. Verified that ICF is disabled. Unable to turn on ICF for reasons: Add the EXT path (C:\Program Files\PHP\ext) to Environment PATH variable. Found a typo in there, appeared to have been created by the MSSQL 2003 install. Restart IIS. Change extension_dir to ./ext/. restart IIS. Change extension_dir to .\ext\. restart IIS. Examining Mambo source. Example: install.php does not work. It redirects to the site (mambo) index.php. The images do not appear on the index.php. Image path Source of install.php (which is supposed to do a pre-installation check) includes: if (file_exists( '../configuration.php' ) && filesize( '../configuration.php' ) > 10) { header( 'Location: ../index.php' ); exit(); I can confirm that there is a configuration.php, however this was because originally the first instruction was to rename a file to this before starting the installer. Renamed to x_configuration.php. This allows me to see the license aggreement. The first step (pre-installation check) is not available. Using installation/index.php, I can now see the pre-installation check. I can confirm that MySQL is not using strict mode. PHP.INI shows this var: The actual full name of the profile is cut off. A new Administrator account was created when this server was unpromoted! Changing to another folder for now, ie. E:\install_temp. Setting appropriate NTFS permissions. Restart IIS. Refresh installation\index.php, now PHP error: This refers to the following code: $filename = "langconfig.php"; if(is_writable($filename)) {} IIS_WPG and IUSR_DS1-SKYLYNX to permissions on folder. Add everyone full control to installation folder. Error resolved. Session Save Path is still not writeable. PHPInfo() shows session.save_path as having no value. This may be because PHP is looking for the PHP.INI in the wrong folder. HOWEVER it is obviously loading it from the PHP folder (not c:\windows) because SOME changes I do make to it actually work... So let's return to that issue to start with. PHP.net has a suspended bug report for this issue. http://bugs.php.net/bug.php?id=42849 Created the following registry keys HKEY_LOCAL_MACHINE\SOFTWARE\PHP\5\IniFilePath -> C:\Program Files\PHP\php.ini HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath -> C:\Program Files\PHP\php.ini restart iis. Another bug report: http://bugs.php.net/bug.php?id=37919 extension_dir is also incorrect, hence why MySQL isn't loading. Adding NEW environment variable called PHPRC to PHP folder. restart iis. restarting server. LUNCH TIME! I think i'm on the right path finally. I remember trying to get PHP to work with IIS6 and Server 2003 a few years ago. I ended up scrapping PHP and using ASP.NET exclusively. Now I know why!

Changed Application Mapping to: C:\Progra~1\php5\php5isapi.dll. Restarted IIS. Got 404 error. Changed back to original path. Added PHP ISAPI DLL (C:\Program Files\PHP\php5isapi.dll) to ISAPI Filters. Restarted IIS. Changed PHP.INI: extension_dir="C:\Progra~1\PHP\ext". Reorganized php.ini's extensions as follows: [PHP_MBSTRING] extension=php_mbstring.dll [PHP_EXIF] extension=php_exif.dll END OF THE DAY CURRENT ISSUES: 1. MySQL information (besides PATH variable info) is not showing up in PHPINFO() results 2. Mambo getting blank page on install2.php (where it is supposed to be connecting to MySQL to populate the database) 3. Unable to install PEAR

Added MySQL login information into mambo\configuration.php. Normally the installer script is supposed to do this for you. Created an empty database in MySQL called test. IIS Web Service Extensions. Enabled Server Side Includes. Enabled All Unknown CGI Extensions. Added MySQL\bin to Environment Variables PATH. Changed Application Extension Mapping for .php to C:\Program Files\PHP\php-cgi.exe. restarted IIS. Changed Application mapping back to php5isapi.dll. MySQL now appears in the PHPinfo, but only as the path environment variable. install2.php is still blank. Changed this in php.ini extension_dir="C:\Program Files\PHP\ext" Installed PEAR. About 30 other failures. I have tried ./ext, .\ext, \ext and the full path above. I confirmed that these files actually exist. Granted Everyone access to this folder.

On a hunch, removed php.ini from c:\windows and restarted the server. OK now PHP is working again. PHPinfo still does not show any MySQL information. Mambo install2.php is still blank. Back to working on that problem...

Changed php.ini line: doc_root = C:\Inetpub\wwwroot In both default location (from start menu) and c:\windows Restarted IIS. No input error is gone. Now PHP pages appear as blank! Error and And Error and

I installed Microsoft's IIS Debugger but I am unable to recreate the error from before. I am reverting back to the "no input file specified" issue. In IIS, Web Sites Properties, ISAPI Filters, add php with php\php5isapi.dll as the source. Restart IIS. Error after resumed: Still unable to view PHP. ASP working with debugger file which opened in IE. Results: And

NOTE: This is a live troubleshooting thread. Request: do not recommend updates (such as service pack) or disable programs as a first response unless absolutely required and backed up by proof that these things cause said problems. I will ignore any such posts as 'disable your anti-virus' or 'get the latest service pack'. Specs: OS: Server 2003 Standard SP2 x86 IIS: v6.0 PHP: v5.2.5.5 MySQL: v5.0.67 Testing source: Mambo v4.6.5 Testing browser: IE8 beta 2 with Dev Tools Additional Applications: - MySQL Administrator Things already done: - added PHP MySQL dll to Web Service Extensions - added PHP MySQLi dll to Web Service Extensions - copied PHP.ini to c:\windows* - copied libmysql.dll to c:\windows\system and c:\windows\system32** Behaviour Timeline 1. Installed PHP and MySQL. PHP automatically configured a website in IIS6. Was able to view localhost\test.php (phpinfo()) and it showed information correctly. 2. Installed Mambo into IIS and started the installation. After first page (install1.php) it loads install2.php where it is supposed to connect to the MySQL database and create the tables. This page ended up being blank. Mambo's forums are showing a multitude of possible resolutions, most of which are not applicable or did nothing for me. 3. I downloaded and installed MySQL Administrator to verify that the database was working properly with the credentials I set it up with. I set security to disable Grant Tables, as was directed by a mambo post. 4. I checked install1.php and it said that Strict MySQL was not supported. I used the MySQL's version of the Query Analyzer to set compatibility to MySQL v4. 5. Thinking that PHP wasn't able to see MySQL (it was not appearing in the test.php results), I added the Web Service Extensions for PHP's MySQL and MySQLi DLLs. no change. 6. I copied MySQL's libmysql.dll into c:\windows\system and c:\windows\system32 and restarted IIS (note: I restart IIS after each change) and now am receiving this message in IE8 to either test.php or install1.php. Event Viewer also gives me this message: Source: W3SVC Event ID: 1009 Desc: A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '2252'. The Process exit code was 0xC0000005. Thinking that IIS did not have access rights to the new DLLs I copied into the System folders, I added LOCALHOST\NETWORK SERVICE to read access to each of the files. This has not resolved the issue. I downloaded a program called iisstate which can debug IIS (inetinfo.exe). The new PID is 3988. I know Cluberti is good at reading these dump files, and I have a general idea about them, but I can't find an issue with this info: EDIT: Removed iisstart.exe dump information. The MS debugger (info in following posts) is much better with the information. The full dump file is 32MB! A note about the above message about ASP. ASP's Web Service Extension is Prohibited, but has ASP.NET v1.1.4322 and ASP.NET v2.0.50727 Allowed. I do not plan on using any form of ASP on my server.

Its funny to a point, especially if you are in a tight community, but in the end revealing ban reasons just lead to flame wars and more bannings, threads getting locked and everything else. You don't need it here. The last thing you need here are factions and forum wars.

I've got a Server 2003 machine that I want to convert how it looks to Windows Embedded. I already have some of it done but there are some things I need to find or edit to make it look real. Tell me something or lead me in the right direction for these items: 1. Winlogon screensaver, currently has the Windows 2003 logo that bounces around. Does Embedded have its own screensaver or how can I edit this screensaver to put a different picture in it? 2. Classic Start Menu, along the side in the gradient it says Windows 2003 Server. I'd like to change these words but don't know where they are kept. I am also having trouble figuring out how to change the boot logo, although I hear that this may be impossible on 2003. The computer is 32bit, standard version. I've already done wallpaper, theme and logos (like when you log on or lock the computer).

Try setting the compatibility options for it and force VGA or 256 colors on it.

Good luck on getting a response... this thread is hella old. For me its FPS although I think I've put more hours into RPGs than FPS. Then again, maybe not lol.