nmX.Memnoch

I don't recall ever saying that. I work for a rather large "organization" and we're nearly 100% Windows. UNIX of some flavor (not Linux) is used only for very specialized applications that were designed by a 3rd party to run only on UNIX. And believe me when I say downtime is something we do not tolerate.

Access and SQL are two different database engines. If there are going to be a lot of users using the database at the same time then it should definitely be in SQL. Access databases aren't designed to handle a lot of users (more than about 5-8) accessing a single database at one time. This is going to be dependent on the other company migrating everything though. Access can still be used as a front end for a SQL database.Something else you should give some serious thought to is a server to handle SQL Server. I would not install SQL Server on your DCs. Since you're not talking about a lot of users then you don't need something as powerful as we've configured for your DC. You can probably get away with a PE1800. They'll need something though... That XP Home to XP Pro upgrades shouldn't take very long. This is going to be one nice feature of Windows Vista...you can purchase an upgrade without reinstalling. Just plug in the key and it'll add the necessary bits and bytes so you don't have to reinstall (at least that's the way I keep reading it's supposed to work). There will be a transition and adjustment period for them though with moving from local logons to domain logons. Since there isn't currently a domain there shouldn't be any downtime regarding that side of things. All you'll have to do is create the domain, create the users, join the workstations and give them their new logons. You'll probably have to go through profile migrations and such, but that's incidentals. There'd be a lot more work if it were a bunch of existing domains you were attempting to migrate into one. I wouldn't make the old box a domain controller at all (BTW, with Active Directory there is no such thing as PDCs and BDCs anymore). I would just make it a member server and use it for serving files, printers, backups and such. You may be able to get away with using it for SQL Server just to get things started. They can purchase a better server later (SQL databases aren't that hard to move).

I've had issues with Promise controllers on older PIII systems like that. Try moving the card to another PCI slot.

Agreed...try that before we press on with the recovery method. I'd recommend BartPE, but NTFSDOS is easier/quicker to setup. http://www.nu2.nu/pebuilder/ http://www.sysinternals.com/Utilities/NtfsDos.html As an aside from the problem you're having now, you can (and should) slipstream the service packs into your XP CD so that SP2 is installed from the get go. See the MSFN guide here (I personally prefer the manual method at the bottom of the page): http://unattended.msfn.org/unattended.xp/view/web/6/ Use the information on this page to burn your new CD image: http://unattended.msfn.org/unattended.xp/view/web/8/

Have you tried opening the BIN file with ISOBuster yet?

So the drive configuration you're trying to get running is an 80GB drive connected to the onboard controller and two 20GB drives connected to the add-in RAID controller? Sounds like you may just need to check your boot order in the BIOS. With a system that old make sure that "SCSI" isn't listed first in the boot order.

You need to manually run Excel one time as the user you're trying to run the automated script as. This will create the registry keys the even data refers to.

Another up and coming free forum is Simple Machines Forum. http://www.simplemachines.org/ vBulletin is the best IMO, but SMF is pretty good for a free forum. phpBB is the most common, but after having used vBulletin for years phpBB just lacks too many features.

Virtual Server 2005 Frequently Asked Questions This, of course, applies only to the Microsoft Virtual PC/Server technology. Basically, a physical server can run any number of virtual servers, within it's resource (CPU/RAM/etc) limits. Intel, AMD, Microsoft, and others are trying to push it for everyday usage, but I think it still has a long way to go for that. Sure, the server hardware is definitely powerful enough to run multiple virtual servers in certain instances, but you're putting everything down to one point of failure. Admittedly though, a virtual server is much easier to recover since all you have to do is restore the virtual hard drive files on another physicaly server and you're back in business. Peronally, I'm only confident enough in it at this point for testing and development environments. Give it another few years and it'll definitely be to a point where it can be used for live business applications.

Err...are you having the problem with IE7 or with Firefox?

That's exactly what I meant...I hope he didn't delete them, either! 149.05 is correct because the hard drive manufacturers count "1GB" wrong (that's a whole other discussion). Again, this is an unnecessary step. It's something you can do during Windows XP Setup. I just hope you really were on the 80GB drive and not mistakenly on one of the other drives.There is a way to get your data back, but you'll need another hard drive of at least 160GB (or the maximum amount of data you had stored on one of the drives). If you're interested and have another drive let me know and I'll outline the steps for you.

You guys really need to read the rules and stop double posting.... http://www.msfn.org/board/index.php?showtopic=70938

Not necessarily. Sometimes you can mitigate the vulnerability by blocking specific ports at the firewall. Other things can be mitigated by local policy (i.e. no web browsing on the servers, no email checking on the servers, etc, etc). The only way that Linux/Unix gets higher uptimes between reboots is that you can usually patch them without having to reboot. The patching systems are completely different. Windows has certain services that can't be restarted with the system being rebooted. The hotfix installation routine can't replace files while they're in use so they're staged and then replaced at the next reboot. Besides that, rebooting for a patch doesn't really count as "downtime". A patch reboot usually takes 10-15 minutes depending on hardware (mainly the SCSI/RAID controllers enumerating devices). If you schedule the patch installations after hours then how is that considered downtime for your business? If you have a 24/7 operation then you should be using clusters as jftuga mentioned. When you put it into the context you're talking about, you don't judge it on how long the server is up between reboots. You judge it on how long the server is up during normal business hours, even if it's rebooted at 3am every morning when no one is using it.

Attached is a PDF of the way I'd configure the server. It comes in at roughly $8.5K, but I included a few more things (like 2003 R2 X64 Enterprise Edition instead of Standard). Basically: - Dual Xeon 3.8GHz w/ Hyperthreading -- it's actually a little cheaper than doing the 2x2.8GHz Dual-Core Xeons and will likely be faster. Either one is going to be plenty fast. - 4GB RAM -- no change - 2x36GB 15K RPM RAID1 for OS -- no change - 4x73GB 15K RPM RAID5 for data -- added one drive for slight speed increase as well as extra storage. This still leaves you with two built in slots and the option to get the media bay drive cage to add another two drives. You could even add one more and set it up as a hot spare (or just get the 4 I configured, set three up in RAID5 and one as a hot spare...extra redundancy). - Server 2003 R2 X64 Enterprise Edition -- only because it comes with 25 CALs and it's obvious they'll need them later. This is where the major difference in our price comes from as Enterprise Edition adds almost $1650. - 2x4 Split Backplane -- better for I/O operations - PowerVault 100T DAT drive w/ controller -- same - Onboard NICs vs. the default option of Intel PRO/1000MT add-in adapters -- if I'm not mistaken, the onboard NICs in the server are already Intel PRO/1000MT adapters so there's no need to add anymore. If they aren't the Intel adapters then they're Broadcom GigE adapters, which are pretty decent as well. - Redundant PSUs - APC 1500VA UPS Battery Backup - 24X CD-RW/DVD Combo Drive - 3 Years, 4Hr Response Silver Support You'll notice that I have the 36GB drives as the last two drives in the configuration. This isn't the way I'd normally configure it, but it was the only way to get the price for the two drives. For some reason Dell's site doesn't have the 36GB drive as an option for the "Primary Drive". You can obviously move the drives around so that the 36GB drives are first when you get the server. Anyway, that's just my take on how I'd configure it. If you take the OS from Enterprise Edition down to Standard Edition, the price changes to $6.9K with all of the other options remaining the same. Personally, I'd leave it with Enterprise Edition. Dell_PE2800.zip

Ahh...it's a bootable CD. There are several ways to do this but the easiest is just to make the .CUE file as Gouki suggested.

This part is kind of confusing...Are you installing to a hard drive attached to the onboard IDE controller, but also have the add-in RAID controller with drives on it? Or did you just remove them from the RAID controller and attach them to the onboard controller for testing? Basically, what I'm asking is...what is your full hard drive configuration with all drives attached where you want them pre-installation?

Ok...cache was the wrong term because they really are two different things. Cache holds recent/common processes/instructions so they can be called again quickly, where a buffer holds data that is waiting to be sent somewhere (either into the GPU to be processed, or has been processed and is waiting to be sent to the display). I just used to term "L2 Cache" as an example to try to give people an idea of where the memory is in relation to the GPU itself. It's embedded into the GPU die like today's L2 caches are on CPUs. On desktop video cards the memory is located on the card with the GPU, but not within the GPU die itself. As you mentioned, it is very expensive to implement..which is why we haven't seen it on desktop GPUs yet. I know that both major players in the 3D GPU market have been working on a cost effective way to implement it though. The following is from an XBox 360 artical on The Tech Report from last year:

Check out products from GFI as well. http://www.gfi.com/ They aren't free, but they're some of the best.

This is the only point that needs a little correction/clarification. The GPU in the XBox360 has 10MB of integrated memory. What this means is that the GPU chip has 10MB of memory built into it...unlike current desktop GPUs. It's basically like a Level 2 cache for the GPU. Supposedly desktop GPUs will get there in the next generation (the XBox360 GPU is heavily based on the current line of ATI desktop GPUs, or rather it's the other way around).

That's the answer there... If the application makes customized settings that only apply to the current user (Adobe Reader and WinZip come to mind) then it should be installed during the GUI part of setup from CMDLINES.TXT. That way the customizations apply to all users who logon to the system. Oh, and.... Why yes I can....

That's where I put my stuff.

By "refresh update" I assume you mean the updated build that was released last week? Did you have the prior IE7 beta installed? If so...did you uninstall it, per the instructions, before installing the updated build?

You don't need to edit setupreg.hiv to do those items. All you need are .reg files that get loaded during the GUI part of setup using CMDLINES.TXT. It's a much safer method and easier to manage.

AutoIt gets my vote.