Matt, You can make that header two ways. 1.) make it a Web User Control and then on any page you want that headret you simply insert your header user control. You also could implement the Application BeginRequest event in the global.asax file. Like this and emit a header without having to explicitly add it to each page. Sub Application_BeginRequest(sender As Object, e As EventArgs) ' emit page header Context.Response.Write("" + ControlChars.Lf + _ "" + ControlChars.Lf + " " + _ ControlChars.Lf) End Sub Good Luck, Martin Garins

Hello i had that problem when I first installed it on my win2k system. Did you install all the components like it makes you before you install it? If you did and did it by clicking on the server settings link on the button of the setup page and all you did was click install for each of the components, dont do that ;P follow the instructions for each component before you install it. Then reinstall VS.NET again and it should work....

(followed by one of those annoying bug reports to MS). Why is it annoying? Personally I think it is a bloddy good idea. ________________ David Wulff http://www.davidwulff.co.uk "I loathe people who keep dogs. They are cowards who haven't got the guts to bite people themselves" - August Strindberg

Hi! MS has tool addressed for this issue. It's called SysPrep. It is the part of the W2K distribution, and add-on for NT. Here is the abstract from the TechNet article "A Blueprint for Building Web Sites...". BTW, searching TechNet for the keyword "sysprep" I've found 188 issues. This is the first one. Regards, Gennady ------------------------------------------- SysPrep (Windows 2000) SysPrep is a tool (available in the Windows 2000 Resource Kit) designed to deploy fully installed Windows 2000 installations on multiple machines. After performing the initial setup steps on a single system, administrators can run SysPrep to prepare the sample machine for duplication. Web servers of a site farm are normally based on the same image with minor configuration differences like name and IP addresses. Additionally, the combination of SysPrep and a winnt.sif answer file provide the tools for making the minor configuration necessary for each respective machine. ----------------------------------------------

Purify is the memory leak, API validation package. I use Purify, PureCoverage, and Intel's performance package. (But I would have gotten the Rational one if I didn't already own the Intel one.) Tim Smith Descartes Systems Sciences, Inc.

I have to say I don't agree. I do think however that simple apps like notepad are very likely to benefit from the Open Source treatment. After all, anyone can write one (and many do - there are at least 2 notepad replacements available as samples on the Visual C++ CD-ROM for a start...). And yep, I know about the 64k limit. That was something that made me mad for a while... In other areas of the OS such as the UI, I don't believe that such collaborative development is going to produce results as well or quickly as the incentive of huge profits from ripping off the customer (don't get me started on that. We'll be here all week :mad: ) Whether we love them or hate them, Microsoft do know where they want to get and are good at getting there. Others (IBM and Sun spring to mind) are or have been equally aggressive. They just didn't stay the course (and I have to say I'm rather glad about that). Personally, I always liked Digital Research... ;) Andy Metcalfe - Sonardyne International Ltd (andy.metcalfe@lineone.net) http://www.resorg.co.uk "Be yourself, not what others want you to be."

begin design 2) abort design, code like mad (management priority change) 3) confront design (lack of) issues with elegant hack 4) while waiting for management approval of design, code minesweeper clone 5) arbitrarily roll to production without testing 6) code like mad to fix testing (lack of) issues (that would not have been a problem were a design properly done) 7) take comp day, drink beer, code at home for the fun of it -John

I have some utility libraries I have written that are used in several applications. Some of these applications are in FDA-certified medical devices, which means that any change needs to be thoroughly checked and documented before being committed on that branch (we can't afford a minor bugfix or performance enhancement that causes new bugs to emerge). Other applications are more research-oriented, so I can be more risk-acceptant with those. If I discover a problem (or potential enhancement) on the research branch, I may want to propagate it to the medical-device branch. He was allying himself to science, for what was science but the absence of prejudice backed by the presence of money? --- Henry James, The Golden Bowl

I am not sure on whether what you propose is legal or not. You will have to have a look at the EULA (End User License Agreement) that XP will come with. As for whether it is technologically possible, I have not tried. My understanding is that each installation of the operating system does require activation. Personally I think what you propose is unlikely to be legal or technologically possible with serious (illegal) tampering, but I am no expert. Take a look at the MS product activation FAQ. http://www.microsoft.com/windowsxp/pro/evaluation/overviews/activation.asp :) Matt ------ Accept that some days you are the pigeon and some days the statue.