Regarding Installation on x86-64

crashfly · Post by **crashfly** » Thu Jan 08, 2009 12:35 am

I have what I would call a problem. Being that I updated from an x86-32 to an x86-64 OS, a number of things have changed on the new installation setup routine.

Since I am only now getting into slipstreaming my x86-64 media, I need to know where SVCPACK installations go. Under x86-32, it was I386\svcpack. Is it still the same for x86-64, or does that location change depending on if it is a x32 bit install program or x64 bit install program?

Edit: As an addon to the above question, where does the winnt.sif file go in an x86-64 installation (\AMD64 or \I386)?

Post by **5eraph** » Thu Jan 08, 2009 4:06 am

It changes, crashfly. Everything now goes into AMD64; such as WinNT.sif, SvcPack.inf and the SVCPACK folder.

crashfly · Post by **crashfly** » Thu Jan 08, 2009 12:21 pm

The reason I had asked this, I have worked quite a bit with the XP x86-32 setup. In the x86-64 setup, I was verifying the changes since the guides out there do not explain that x86-64 has these changes. They "assume" that most everyone knows. Personally, I wish msfn would update their guide on the 64bit systems.

Post by **5eraph** » Thu Jan 08, 2009 12:35 pm

I know what you mean. I'm thinking that the people that put up the guides didn't know either. I had to find out for myself.

crashfly · Post by **crashfly** » Thu Jan 08, 2009 8:37 pm

One more thing on installing addons with nlite or the Integrator. Switchless installers I realize do their own thing at svcpack and runonce. Do the 32bit programs (and addons) also get added to the AMD64 folder, or will those 32bit files get put in I386?

Specifically, what I would like to do is take one of Kelsenellenelvian's packs (his Uber pack) and try and convert it over to use and install on x86-64. I realize some of the programs may not "quite" work as expected, but I wonder if the x86-64 setup routine will be smart enough to understand what to do with the files. What is worse, I have to figure out *how* to modify his addon to make install properly for 64bit Windows anyway.

Any pointers, suggestions, tips, or even stuff to just watch out for?

Post by **5eraph** » Thu Jan 08, 2009 9:24 pm

All switchless installers get added to AMD64\SVCPACK, regardless of "bitness." Things get sorted out at install time by the emulation layer, if necessary.

I posted some guidelines on WinCert, but with an addon as complicated as the UberPack I don't know how well it'll work.

code65536 · Post by **code65536** » Thu Jan 08, 2009 9:58 pm

This is why I love switchless installers. No need to worry about source locations. No need to worry about how the Wow64 emulation layer will affect you (make the emulation layer work for you!). Just one very simple rule: launch the INF w/ a 32-bit host process if you're installing a 32-bit app and with a 64-bit host process if you are installing a 64-bit app. A switchless INF-based installer is the most pain-free way to ensure that things get installed correctly, IMHO. So instead of converting his 32-bit addon pack into a 64-bit addon pack, consider instead converting it into INF-based switchless installers.

crashfly · Post by **crashfly** » Thu Jan 08, 2009 11:43 pm

I like the idea. However I lack the knowledge of creating a switchless installer to do that. Being that Kel's Uber pack is already "inf" based, (and actually can be launched from the inf), what I would need to figure out is how to successfully create the "switchless" installer.

conan · Post by **conan** » Mon Jan 12, 2009 7:53 am

These days a system with 2GB RAM is mandatory. In the days of 2005 year, 1GB was enough.
Probably over 5 years, 4 GB RAM will be the standard, so 64 bit OS will meet a wide propagation.
And MSFN Unattended Guide will be a little bit different.