fizban2

basically they are making it possible for multiple DLL versions to coexist to take care of some many issues that result when DLLs are changed. just eats up more space. but from reading your sig EL, you seem to have some space to spare

good job sereby!

nlite really isn't a deployment method that you would want to use to a corporate environment, if this is something that you just want for use at home or the like then nlite would work, you would just have to wait for people to create a version of nlite for vista

LH server is suppose to be end of 2007, thought betas are out now. it runs amazingly well even at this point in development and they have a year to go with it!!!

there aren't anymore problems with rolling out vista then there were with rolling out XP chrisitan check out the BDD 2007 http://www.microsoft.com/technet/desktopde...07/default.mspx that is everything you need to accomplish your goal you can also check out MS webcasts on deploying vista, those should help get you in the right direction http://www.microsoft.com/events/webcasts

it will be the public IP of your line, the 192.x..x.x will not work on the internet, you should have it where the public ip (202.x.x.x) goes to a NAT on your netowrk and then routed to your VM (192.x.x.x)

the new packaging has a two fold effect, 1. smaller packaging = cheaper just like the video game makes found it, there is no reason for a huge honking box for software. it is a waste of money. the new packaging is big enough to be noticed (especially by the design) and serves the purpose of protecting the DVD, nothing more. 2. Pleasing to the eye. Just like with some of the big selling marks for vista is eye candy. the box looks good and sorta says "look at me i look cool and fast" the box also reminds me of a little macish look to it, but agian that is the plesasing eye candy.

http://www.microsoft.com/technet/desktopde...07/default.mspx check out Microsofts Business Desktop Deployment Tools, everything that you are looking for can be found within this toolset

Thanks for letting us know BL! I suspected foul driver play hopefully we can get the issue narrowed down soon

one would hope that you connect through a VPN first then remote to the server as needed, but mattering the situation that maybe all he can do

like Valter said, Setting up Routing and Remote Access to NAT your connection would help, but if you already have a static IP from you ISP, you can just enable remote desktop and connect via IP address

http://dmzweb3.europe.creative.com/SRVS/CG...com/,case=14186 go here and make sure you have gotten the RC1 driver package, also go into cmputer management and enable the administrator account and set a password for it. then logon as the administrator and install the software drivers. any and all software and drivers should be installed as that admin, even if your account is in the admin group you are restricted in some ways

steve, real quick what version on vista are you on, what video card are you using, and what version of the drivers are you on.

outlook 2003 would allow for a larger PST size, you might want to look into why are that is needed, possibly some archiving solution, keep the last 6 months information in one PST and after 6 months, archive it and save the PST to his backup drive or Burn it to DVD. depends on how you are setup to do back ups and such

drivers are a trickey situatiob because alot of drivers that are being used technically are not certified for vista. this causes issues with the installation and teh PNP functionality, at least that is what i have been lead to believe. hopefully we will see a new version of the BDD nov 7 or soon after when vista is releases

go download the IEAK for IE7 http://www.microsoft.com/technet/prodtechn...7/relnotes.mspx you and customize the installation with it

The Microsoft-Windows-PnpCustomizationsWinPE component is used to add one or more out-of-box drivers to a Windows installation. Drivers that are located in the path specified by DriverPaths are copied to the driver store of the Windows installation during the windowsPE configuration pass. You can add boot-critical as well as non-boot-critical drivers with this component to a Windows image before it is installed. XML ExampleThe following XML output specifies the UNC paths to additional locations for device drivers and the credentials used to access those paths. <DriverPaths> <!-- First PathAndCredentials list item --> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>\\myFirstDriverPath\DriversFolder</Path> <Credentials> <Domain>MyDomain</Domain> <Username>MyUsername</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> <!-- Second PathAndCredentials list item --> <PathAndCredentials wcm:action="add" wcm:keyValue="2"> <Path>C:\Drivers</Path> <Credentials> <Domain>MyComputerName</Domain> <Username>MyUsername</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths>

what kind of sound card you using? are the drivers installed correctly? which drivers did you use?

-only- if you allow it though, through the use of ActiveX. injected java script can do it to, though not very easily from what i am told, but that is beyond the realm of my knowledge so i won't continue further. as for the original question @ kartel the "blue Pill" exploit has already been patched, it will no longer work

correct, right after your install vista will be indexing everything on the computer so it can give you faster search results, rather then the old fashioned snail crawl search it keeps everything up to date with an index, the first time it does this you get some pretty slow results with vista but onces its done it flies, i think at this point we need to rule out bad media by having him reburn either 32 or 64 and reinstall, troubleshooting can start indepth from there. i know i have had media problems before (my TDK didn't burn a dvd+RW right once) it was slower then &*$# when i booted up

@ bled, RC2 is no longer available for download, it had a cap of 200,000 downloads which finished in 72 hours, @ spooky, since he has a 64 bit CPU he can install 32 bit or 64 bit, which ever he likes better, that won't effect this much. i am still going with a bad burn till we can rules that out

was this a clean install? what kind of HD is it installed on? most installs that act like this have been from bad media (DVD), try reburning the DVD at the slowest speed your burner has, and do a clean install to a HD. see if that helps at all

it isn't that they won't make DX10 compatible with XP and 2003, it is they can't, the amount of changes that they have made to the UI and graphic sub systems means that there is no way to port those features and advancements back tp XP and 2003, the Sub systems of boths OSs would not know how to handle those new features. @delprat i agree with you fully until we see some actual bench marks and realife tests there is no way for sure to state that one will be faster then the other. hopefully we will be able to see those tests soon!

which driver is that?

do a search of the forums for office 2007 unattanded, it has been posted a couple times