Jump to content

jgurtz

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About jgurtz

  • Birthday 03/23/1975

Contact Methods

  • AIM
    co1ophon
  • MSN
    ctsurfjay@hotmail.com
  • Yahoo
    flakier

jgurtz's Achievements

0

Reputation

  1. Background: I installed this machine a while back with nLited XP SP2 media. Spring of 2008 I applied SP3... The Issue: Today I wanted to check something in Add/Remove Windows Components and lo, error after error of missing .inf and .dll files (starting with fxscom.inf and fxscom.dll). Hmmm....how very strange. Resolution: So I look in %systemroot%\inf and wouldn't you know that sysoc.inf was modified on 03 Apr 2008. Thankfully I had not yet deleted the $NtServicePackUninstall$ and was able to replace the SP3 installed version. So now, the question is (when comparing non-modified OEM SP2 sysoc.inf and SP3 sysoc.inf) what are the changes in the SP3 version? After comparing files from a different PC (stock install, no nLite used) the answer turns out to be "not much." Besides a few whitespace changes that shouldn't affect anything there is one changed line and one added line. View the attached patch generated from WinMerge to see the differences. It is a "Unified Style" diff so with a command line unix style patch utility you should be able to script the fixing of many machines. sysoc.inf.sp3patch.txt
  2. I'm not sure about XP x64 but Server 2k3 x64 and ia64 do not ship with .NET 1.1 (which is 32-bit only distribution). It is supported install by running via WoW64. I have an extensive report about this and related issues that shall be posted in a bit in a different thread as I have been working about 4 days solving....
  3. yes indeed incredible work MS should hire him!
  4. I've noticed a problem with getting .Net 1.1 installed on this platform and after doing quite a bit of searching I'm tending to think that something was taken away by accident via using nlite. The redistributable from: http://www.microsoft.com/downloads/details...;displaylang=en states that 64-bit server 2003 is supported. But, when you run it, it says: The stand alone SP1 package for .NET 1.1 from http://www.microsoft.com/downloads/details...;DisplayLang=en says this: I'm really at a dead end here. Anyone have some clue or better google-foo than me?
  5. I'm not sure what happened on the HP machine but I redid an image with the last stable and it worked near perfect like always so...? I don't think it's 100s of issues just several that were standing out. Didn't mean to sound mad or anything...just wanted more to warn people to watch closely with this new release. I now have in front of me an old piece of S*** pcchips mobo (1Ghz P3 w/512MB) and this time more than a day to get into production (it's a side project) so I will try 1.4 again and can look more in detail at the issues this time. Thanks EDIT: this poor little thing is gonna be a DC and DNS/WINS so it's a good testing scenario I think
  6. Wow, new version and many many good looking changes. I tried this out on a new HP DL140 G3 installing Win2k3 R2 with SP2 slipstreamed into the source cause the SFC issue was a bit irksome. Sorry to say I found many regressions compared to the previous stable. So many I don't have the time to try and make a complete list. I found the start menu was missing nearly everything (no command prompt, no windows explorer) Quick launch was displayed, but empty. Automatic Updates service not installed. I started fixing icons and things by hand but now I'm finding so many b0rked things I'm giving up and just faster/easier to remake CD with last version of nLight. Many other minor settings were also not as selected (some my Computer->properties->advanced tab->performance settings, start menu settings, right-click My Computer settings). Hopefully others will elucidate some of the particulars here. See ya in a few builds...
×
×
  • Create New...