fizban2

9l is the directx9 release for vista (for better backwards compatability with Dx9 games) it isn't for XP at all

freakin ell, i check there site, go to lunch and they launch new drivers...<shakes fist> curse you Nvidia!! oh and also thanks!!!

are the 2 applications domain specific (ie he has to logon to that domain to get to those documents or progams) or is it possible that his account can be trusted in both domains (is there any trust between the 2 domains?)

if you needed to install software as a user (say usera) you can always run the installation as an administrator either by right clicking the .exe and choosing "run as administrator" or if you script it out you can use runas commands

DX9.0L is a special version of DirectX 9 for Vista only that allows DX9 games to run with Vista's new driver model. It's not possible to run D3D10 on XP without running in pure software emulation. Pure software emulation... bet that would run Battlefiel2142 really nice :-D

d3d10 port to xp can't be very good, it won't be the same as what is in vista

you can also use a R2 key to install the first CD (2003 SP1) it will work and then you won't have to change the key the second time

the admin account has always been like this, normally it is disabled by default (not sure why MS decided that one but eh) this is the account you should use to install and configure your computer. then use a account created and added to the administrator group if you want for everything else.

The domain controller that is the schema master must have Microsoft Windows Server 2003 Service Pack 1 (SP1) installed. (By default, the schema master runs on the first Windows domain controller installed in a forest.) • You must have at least one global catalog server in every Active Directory directory service site where you plan to install Exchange 2007. This global catalog server must be running Windows Server 2003 SP1. • Windows Server 2003 SP1 is recommended for the following reasons: • Windows Server 2003 SP1 supports Exchange 2007 service notifications. When a configuration change occurs in Active Directory, a notification is sent to the service. Several Exchange 2007 services use this notification. The notification mechanism in Windows Server 2003 SP1 is an improvement over the notification mechanism in Windows 2000 Server. • Windows Server 2003 SP1 allows users to browse the address book in Microsoft Outlook Web Access. • Windows Server 2003 SP1 provides the ability to look up distribution list membership in a more efficient manner than in Windows 2000 Server. • In each domain where you will run Setup /PrepareLegacyExchangePermissions, setup must contact a Windows Server 2003 SP1 domain controller. Setup /PrepareLegacyExchangePermissions will not complete successfully if it cannot find at least one Windows Server 2003 SP1 domain controller. exchange 2007 requires the AD schema to be at 2003 level, it cannot run with the AD domain at 2000. You might be able to upgrade to 2003 mixed mode and get away with having your Schema Master at 2003 SP1 and the GC for each domain 2003 SP1 while the other DCs are 2000. but i doubt that it would be a recommended configuration

connect.microsoft.com if you cannot get it there then the beta is been closed and they will be going to rtm soon. they have to have the BDD done the same time they do vista for business's so that they can use it to deploy vista

I downloaded the driver file from the link in your post, decompressed it and manually installed the drivers by pointing a folder where the decompressed files are. The date and the version as shown in the properties of the installed driver are 9/18/2006 and 6.0.1.1220. The problem symptom remains the same as stated in my original post. did you install the drivers as the admin or as your own account? make sure you install all drivers and apps as the administrator, an account with admin rights is no longer the same, see if that helps

for the most part it is to deal with the issues companies have had with trying to fix office setups when patches would look out to a network share files the install files to configure office, besides disk space is cheap these days,

you got both of them (i remeber that deal), i would download RC1 if you want to try it out, RC2 is no longer available but is a better build. it should fine on your system thought

exporting out the list to a csv and importing it into your AD as mail-enabled contacts would be the easiest way i can think of off the top of my head, you could script it out to happen every night or something like that

so just to clarify, you have multiple domain setup (domain.yourcompany.com, domain2.yourcompany.com etc) andyou want all the different emails to be available in you top level domain (yourcompany.com). is exchange on each domain? or just one central exchange group?

have you installed beta 2 first? you cannot do a full install with just the TR2 bits, you need to first install from the beta 2 install then install Tr2 on top of that

More Info (:-D i can find stuff if i ever have any freaking free time) Precache the local installation source for the 2007 Office system When you deploy the 2007 Microsoft Office system, Setup creates a local installation source on the user's computer — a copy of the compressed source files for the Office product you are installing. Once the files have been copied to the user's computer, Setup completes the installation from the local installation source. You can minimize the load on your network by deploying the local installation source separately, before you deploy Office. To deploy the local installation source by itself 1. On the network installation point, open the Config.xml file in a text editor such as Notepad. By default, Config.xml is located in the core product folder for the Office product you are installing. For example, if you are installing Microsoft Office Professional 2007, open the Config.xml file in the Pro.WW folder. 2. Find the <LIS> element; uncomment the line by deleting the opening <!-- and closing --> tags. 3. Set the <CacheAction> attribute to "CacheOnly". The line in Config.xml should look like this: <LIS CacheAction="CacheOnly" /> 4. Save the Config.xml file. 5. Run Setup.exe on users' computers; on the Setup command line, specify the path to your modified Config.xml file. Note that you must use a full qualified path. For example: \\server\share\Office12\setup.exe /config \\server\share\Office12\Pro.WW\Config.xml where Office12 is the root of the network installation point. Note: If you precache the local installation source on users' computers and subsequently need to remove it, you can set the <CacheAction> attribute to "RemoveCacheOnly" and rerun Setup. This setting works only if users have not yet installed Office. When users with a precached local installation source on their computers run Setup from the network installation point, most of the activity takes place on the local computer instead of over the network. Precaching also allows you to coordinate the upgrade to the new version. You can distribute the local installation source to groups of users over time and then schedule a simultaneous installation throughout the organization without over-taxing the network. Setup handles the creation and maintenance of the local installation source automatically. The default location is \MSOCache\All Users at the root of the drive on which Office is installed. In addition to installing Office from the local installation source, Setup also uses it to repair, reinstall, or update Office later on. If the local installation source is corrupted or deleted, Setup uses the original source on the network to repair or recreate it.

shouldn't be an issue but be warned*** Changes in the 2007 Office system Administrative installation images Description: Administrative installation images have been replaced by a required local installation source. Reason for change: Administrative installation images were difficult to sustain. Requiring a local installation source prevents source resiliency problems when updating. http://technet2.microsoft.com/Office/en-us...3.mspx?mfr=true more info here

nakatomi do you have an AMD cpu as well? just wondering if your guys issue of having to decompress the drivers and install them manually is related, on my machine for 64bit the installer went through fine (intel core duo) install as admin (the actual admin) always install drivers and software as the actual admin, even if you account is in the administrative group, there are things that it cannot do that the admin account can do. Oh but i do agree the sound is just beautiful comping from vista, i switched back to XP and it pales by camparison

if you at least wanted to implement imagex, you could prep your Windows XP image just the same way that you did before, sysprep the machine, then at the stage where you would capture the HD with ghost, capture it with Imagex instead, you will have to script out how the image is laid down again, depending how you apply it (network chare, DVD, WDS) but that will at least allow you to use imagex, i have heard that you can use the BDD to capture XP installs now but have not had the time to try it

good to hear that cluberti's problem is probably tied to the hardware he is working with. thanks for the input rob, and welcome to the forums!

the .h and .lib files are now available for you to write c++ apps witht them

Ok, i know people have been trying to get some AVs to work with vista, not many work and here is Symantecs newest version for everyone ot test. reminder that this a beta software and will not behave as a porduction software so PLEASE don't install this on a production machine or one that is vital to you step one sign up here. https://et.symantec.com input your email and wait for email from symantec to verify your email. from email create a username and password and profile for your computer. go here https://et.symantec.com/callout/default.htm...0-B72AAD2CF25B} sign up for the beta with the username and password you created above. download the beta ***warning*** read the reported errors for NAV before installing there are several issues with Office 2007 TR2 and other items!!!

so am i the only that this build has worked flawlessly for? i have had increased preformance, my creative card now works beautifully (good what great sound it can produce) i would have to say the sound is more crisp and clear then anything i ever got on XP. both 32 bit and x 64 have installed without a hitch, working very well on everything i have install (minus VS 2005 )

those files can be deleted once your installation has finished, i have not found a way to do it from an automated install yet though