fizban2

correct, updating the stack will allow for, if nothing else a better experience in windows since it won't BSOD as much since everything is in user mode versus kerne, mode, also remeber MS is trying to rewrite these stacks and apps and such to run all the up coming hardware and software that people will make and run for the next 10 years. though hopefully we will see updates before then technology moves to fast for things to take that long to change

Sound works fine but just like the network stack, it is almost 10 years old, - Audio stack has been running in Kernel mode, sound when your sound crashes you can get BSOD, the sound stack is now in user mode, sound when sound crashes, it restarts audio and that is it. -audio now can be controlled by a per application proccess, turning your sound up for Media player and down for your game or IE or any other app. - New Audio API, allows for people who write sound into apps or write drivers for sounds cards to more easily write code against to the sound stack

no problem just glad it worked, vista is hard to trouble shoot since most drivers are still written for XP and very few drivers act the same in vista in XP, it is just a matter of messing with it till it works (possibly with a sharp instrument) SLI may not working under Vista yet, if you getting it working please post, i haven't heard of anyone getting it working yet. i only have one vid card so i cannot try that yet

unless the upgrade to an newer build of vista fails you won't lose your settings, i upgraded from beta 2 to 5456, the upgrade proccess is much better with vista, it will laydown vista next to your current OS so it isn't truly an upgrade, more of a side by side install, then while both OSs are there your setting on your old OS are migrated to the new OS. just remeber that it is beta, i have done several upgrades of vista and it has failed once or twice.

- Ability to create users for a domain rather than for a machine. - Access rights for users on a network. any server software should be able to do this with ease, Server 2003 would be ideal since 2000 is 6 year old now, 2003 is very good and been well tested over the couple years. Any server OS will run your 32 bit software if it doesn't then it can't be that good of an OS software. just a note for on something i saw on your list, for remote access of files, VPN would be the ideal solution but the built VPN with windows is not so good and depending on your line speed and setup (single server as a DC should NEVER be a vpn server also) you maybe limited to what you can do. Sharepoint requires IIS 6.0 and at least a windows MSDE (SQL engine) to run.

check in the boot.wim that in the following directory the required files are there. in <mountfolder>\windows\boot\PXE\ there should be a series of files there. abortpxe.com bootmgr.exe hdlscom1.com hdlscom1.n12 hdlscom2.com hdlscom2.n12 pxeboot.com pxeboot.n12 wdsnbp.com at least those files should be present in the folder there. if they are not or you think they are wrong you can copy those files off your WDS server, they should be located in the distro folder that was created for WDS under the x86 folder\boot i believe. I would give a better location but my WDS server is in the proccess of being rebuilt

optional update through windows update? anyway to find what files it loaded?

16-bit (dos) applications are no longer supported by Vista as thunderbolt mentioned, best bet would be to start upgrading the software, .Net 3.0 just came out, would be an ideal time to start a revision of the software, are you still writing in pascal? or do you code in other languages also, c# vb.net etc?

#1 No CALs do not need activation, CALs are only needed to connect to the server, you will add them into your licensing manager on your server, #2 CALs do not have license keys, your Windows XP licenses will have product keys and your Windows Server also will have keys, the CAL only are used to connect to the server. #3 No #4 with the 25 CALS you will get a certificate for each CAL so you should get 25 certificates or a certifice for 25 CALs (not sure if they ahve changed it lately or not) to understand better, you will have an XP license for your client computer, a CAL for that computer to Connect to the Server, and a Server License for the Server itself, unless you by a per server licesnse for your Server, which then means you Here is the licensing scheme for server 2003 The Windows Server Licensing Model—Elements That Have Not Changed Although there have been changes to the Windows Server 2003 licensing model, the following elements have not changed: • Every installed copy of the server software requires the purchase of a Windows server license. • A Windows Server 2003 Client Access License (Windows CAL) is required in order to access or use the server software. • A Windows CAL is not required if access to the server software is via the Internet and is "unauthenticated"—for example, accessing a Web site for general information where no identifying credentials are exchanged. • A Windows CAL (Device or User CAL) can still be designated for use with a single server, authorizing access by any device or user, when the server software's licensing mode is set in "Per Server" mode. In this mode, the number of Windows CALs is equal to a maximum number of concurrent connections. Or, a Windows CAL (Device or User CAL) can be designated for use with any number of servers, authorizing access by a specified device or user, when the server software's licensing mode is set in "Per Device or Per User" mode (formerly called "Per Seat" mode). Other options have been added and are detailed below. • A Terminal Server Client Access License (TS CAL) is required to use Terminal Server or otherwise host a remote graphical user interface (GUI) session, except for a console session. In Windows 2000, there was an exception to this licensing requirement and that will change with this release, as outlined below. Top of pageTop of page Changes to Windows Server 2003 Licensing The following reflects changes to the Windows Server 2003 licensing requirements: • New user-based CAL. Microsoft is introducing a new type of Windows CAL. In addition to existing device-based CALs (Device CAL), a user-based CAL (User CAL) will be available for purchase. You can choose to purchase a Windows Device CAL for every device accessing your servers, or you can purchase a Windows User CAL for every named user accessing your servers. By having two types of Windows CALs, you are able to use the model that makes sense for your organization. For example, purchasing a Windows User CAL might make more sense if your company has a need for employees to have roaming access using multiple devices. Windows Device CALs may make more sense if your company has multiple-shift workers who share devices. Similarly, Terminal Server (TS) will offer both device-based and user-based CALs: TS Device CAL and TS User CAL. • New name for Per Seat licensing mode and expanded usage right. The two CAL licensing modes that exist in Windows 2000 Server still exist, but one of the modes has a new name: The Per Seat mode has been changed to the "Per Device or Per User" mode, and Windows User CALs can be applied. The name of the Per Server mode has not changed, and the rights associated with each of the modes have essentially not changed. Per Device or Per User mode is concerned with the total number of devices or users (or a combination of devices and users) accessing the server software across any number of servers, at any time. In this mode, you need a Windows CAL for every device or user that will be accessing Windows Server. In Per Device or Per User mode, only one Windows CAL is needed for any given device or user to access Windows Server, regardless of which servers it is accessing. Per Server mode is concerned with the number of concurrent connections to the server software. You need to purchase Windows CALs for the maximum number of simultaneous connections to that server. Any device or user can access the server, but the number of simultaneous access connections hitting the server at any given time must not exceed the number of Windows CALs designated to that server. • New External Connector License option. The new External Connector license (EC) can be purchased to enable access to your servers instead of buying individual Windows CALs for external users (or their devices). The EC license is purchased for every copy of the Windows server software that is accessible to the external user. An example of an external user is a person who is not an employee or similar personnel of the company or its affiliates. Terminal Server will also introduce an EC license—the Terminal Server External Connector (TS-EC)—to address a similar need: to enable external users to access a company's terminal servers, without the need to purchase individual TS CALs for them or their devices. Note: Companies can purchase Windows CALs and TS CALs for entities not owned by them—for example, business partners—in order to give those entities access to their networks and terminal servers. This may be the best solution when a small number of business partners or customers need access to a server or group of servers. • Replacing Internet Connector and TS Internet Connector licenses. The Internet Connector and TS Internet Connector licenses are being replaced by the respective External Connector licenses. • Removing Operating System Equivalency in TS. With Windows 2000 TS licensing, if a client device is running the most recent version of the Windows desktop operating system (OS), a TS CAL is not required to satisfy the licensing requirement. However, with Windows Server 2003, a TS CAL will be required for each Device or User using TS functionality, irrespective of which desktop operating system is running on the Device. Top of pageTop of page Terminal Server Licensing Transition Plan Microsoft realizes that the removal of operating system equivalency will affect customers and is committed to accommodating existing Microsoft customers who would like to take advantage of Windows Server 2003 features. Every Windows XP Professional desktop license that you own on the date of the public launch of Windows Server 2003 (April 24, 2003) is eligible for a Windows Server 2003 TS CAL. For more information, visit the Microsoft Terminal Server Licensing Changes and Transition Plan page.`1 So you have 2 option per server - which works by montoring how many concurrent connections are made to the server (down fall you have to do this for each server, if you have 23 computers connecting to 3 servers you need 69 per server licenses, 23 for each server) per user or per device - one license for each user or computer your have, you have 23 computer you have 23 licenses or if you only have 15 peole and 24 computers you could get 15 user licenses and save some money, per user of device works when you start having more then one server

more valid list of core upgrades in Vista Windows Vista is intended to be a technology-based release, to provide a solid base to include advanced technologies, many of which will be related to how the system functions, and hence not readily visible to the user. Completely rearchitected audio, print, display and networking stacks. Native IPv6 stack, which also works with IPv4, eliminating the need for dual stack network architecture. Improved resistance against all known TCP/IP-based denial of service and other types of network attacks. Enable more modular components that can be dynamically inserted and removed. Reconfigure without having to restart the computer. Automatically senses the network environment and adjusts key performance settings, such as the TCP receive window A number of new security measures including BitLocker Drive Encryption Improved memory manager and process scheduler. I/O has been enhanced with I/O asynchronous cancellation and I/O scheduling based on thread priority. Rewritten many kernel data structures and algorithms. System services are in a separated and isolated session. User processes are in another session. Address Space Layout Randomization (ASLR) to prevent Return-to-libc buffer overflow attacks. The new Kernel Transaction Manager enables atomic transaction operations across different types of objects, most significantly file system (Transactional NTFS) and registry operations. Deadlock Detection Technology is a new technology that will include checking for a deadlock condition for windows error reports

i can't imagine what could be better about it. xp has a bulletproof stack. i remember way back in the day an issue with fragmented igmp packets, but i think that was pre-xp. Both the sound and network stacks have been redone in Vista, hence whya number of network cards and sound cards do not have support yet. the new stacks are indeed faster (at least the network stack) and the sound stack will be very nice if sound companies finally get some drivers out for it, XPs network stack was good but lets not forget that it is around 10 years old, it was never designed to work with the amounts of data that some people push through it now, gig and 10-gig networks?? no one in their right mind would have though those would be around in 10 years, the XP stack works with this but not very inefficantly, the XP stack also doesn't have native support for IPv6, which will be a very real problem in the coming years. @saugatak, back porting this stack to XP probably won't work as again, this is a 10 year jump in technology. the way that XP work with the stack and the way that Vista works with it are very different and no, i doubt the stack is a slightly modified BSD stack.

Did you import the WIM image into WDS? it sounds like the WDS server doesn't know where your images are. Double check to make sure when you open WDS you can see your images

vounce your best bet to make sure that they support your device is get ahold of the company that made your Phone and see if they will support vista yet or if they will need to release a update of the firmware for the phone to work properly windows CE 5.0 was the OS that your phone started with but i bet it was heavily modified to work the way that they have it on your phone

no problems, sounds like an interesting issues anyway now pinging internet sites you say is fine? how about releasing and renewing your IP and DNS cache, i know they are simple things but with vista simple seems to fix alot of things, also see if you can find a more specific driver for your wireless card (what model is it by the way) you can try a wireless hotspot or a friend or neighbors house to rules out if it is just a connection issue or not.

i have had issue loading things from flashdrives, make sure it is plugged in before the PE begins to boot, that should help with errors, also you can try and find a floppy drive

No problem, another note as i looked at your specs more closely, there have been many reported issues with the Nforce series of boards working correctly with Vista, that could be part of the issue also

i don't belive that there header file has been released yet, just like the .lib files... maybe in another build they will become available

very cool looking for, but also very exotic, i noted it uses Windows CE 5.0 for the OS it runs, not sure if support is present in Vista for this or not, will have to look into it.

if you unplug the 2 Raid 0 drives, can you install to just the one 80 gig Seagate?

SLI is not an option in vista yet, Nvidia is writing the corrisponding drivers that you will need to run SLI under Vista, give it a little time be happy they even have drivers out that will let you run your card.

once you get that far, there is the option for you to install drivers, this is on the same screen where you can format partition, try and load drivers for your RAID card and see if that helps

which drive are you trying to install to? SATA has given many users a good deal of trouble trying to install to it, how far into the install do you get before it dies?

if you are booting Vista or any OS for that matter (XP 2003 for sure), you can change the letter of any other partition to what ever you would like, even if it also a boot partition, the currently used partition is the only one that cannot be change, once you try to boot the Other OS, it will boot up with C and assign the drive letters that it has setup

This is a known problem with NTFS. This problem I believe existed in Windows XP and Windows 2000. A workaround is to format the boot HDD with FAT32 then convert it to NTFS after the Windows installation process is complete or disconnect all other HDDs. This really isn't a big deal. as biohead said earlier, if you boot back into your XP configuration or other OS config, the drive letters will be what they should be, the only issue you may face is if the drives are dynamic volumes, you may have to reimport them. other then that everything will run normally. i do this with my Vista and XP drives, 1 hd for each and 2 120 drives, vista names them d and g while XP names them E and D, doesn't hurt then drives or info stored there.

shortie, i have the same issues on a machine i am working with, go into your distrobution folder that was created by the BDD (usually the HD that has the most Free space) there is a folder called control found there. in control, there will be a build number folder based on what you gave as a number for your build, also a build.xml, delete both of these but leave the application and Operating system xml files as they are. now you will be able to use the BDD again with it crashing