BladeRunner

I was just passing through so I thought I would just post an answer on this one. Basically there is no way of getting these files back. You've got to remember that you've used a high level of encryption and it would be a complete waste of time if there were any back-doors or easy ways around it. The only option you would have would be a brute-force method. I don't know where to point you with regards that - however it will take you a few years to brute force your way in. You will need to write these files off I'm afraid. For future reference, make sure you backup your keys if you ever encrypt anything. I personally have mine written to a floppy disk which sits in our fire safe at work - just in case everything goes wrong.

Originally posted by tool_462: Quote: Have a quick question here. My PC was originally an eMachines T2879 but basically all that is left of the original is the motherboard and HDD. I have two HDD's but the one running XP is the original that came with the PC. I had a post earlier that we couldnt resolve with replacing a mobo, and I finally determined it as DOA with lots of help and ideas from members. (Thanks!) But here is my main question, if I were to format my HDD (The one with the OS on it) and replace the motherboard, and basically set-up my PC as if it is all new parts, would the Three restore disks and/or 6 disk floppy boot setup be everything I needed to completely reinstall XP? I have the CD key and I have a CD key that eMachines tech support told me to use if the old one didn't work. But I need to know if the disks I have (restore and floppys) will be able to reinstall windows. I have only done repair installs and never tried to install it on a freshly formatted HDD. If not, is there anywhere to get the disks for XP and use my own CD key for very cheap (or free download and burn to CD or something)? Thanks! tool As you are no longer using the original motherboard then no - there is a good chance your recovery media will not work. Recovery media is usually tied to the BIOS on the motherboard. Even using unofficial BIOS updates can be enough to stop recovery disks from working. You were only ever licensed to run WinXP on your EMachines PC. You are no longer running that machine and if you check through your license agreement you'll see that you cannot transfer recovery or OEM Windows licenses. Your cheapest option would be to buy a copy of OEM WindowsXP Home. WinXP Home will offer you around 95% of the features of Pro - however it is highly unlikely you would need the extra features, well unless you're running a full Windows Domain class network at home with Windows Servers which is unlikely.

That is worth knowing. We are actually buying Exchange 2003 for the US offices however actually installing Exchange 2000 so that it is the same as the UK offices. I'll convince the bean counters that upgrading the UK to Exchange 2003 is a good idea and then we can play.

Thank you kindly for the response. I've not had the opportunity to test domain replication over a VPN tunnel but knowing how anybody using a tunnel into our network is in effect "part of the network" I just felt it would work. Onto the next stage.....time to spend some money at Dell

I've done some research into this however I just thought I'd get the opinions of some people "in the know" here before we deploy anything. Here at work we have a Windows 2000 AD Domain. We are also using Exchange Server 2000 We will soon be opening a small US operation, initially about five people however this will slowly grow over time. We decided that possibly the best way of connecting the offices would be over a VPN. We have a CISCO router at both offices that supports VPN tunnels. So the plan was that all "internal network" traffic would be routed through the "permanent" VPN tunnel between the two offices. There would be a Windows 2000 DC sat in the US offices that will be part of the AD and will receive replication information over the VPN. At the same time we want to have an Exchange 2000 server sat in the US office which in effect will be a "local" copy of the Exchange Server we currently have in the UK. The added advantage here is if either Exchange server were to fail then both the UK & US offices would be able to use the remaining Exchange Server. So, the basics are as follows: UK Office - Win2k AD Domain with Exchange 2000 Server US Office - Part of the same Win2k AD Domain with a local Exchange 2000 server. Full replication will take place over a "permanent" VPN tunnel formed between the two CISCO routers (one in the UK, one in the US). My "theory" is that the DC & Exchange Server in the US offices will be seen as being part of the main network. Replication will simply work (albeit slower, 4MB connection here in the UK and a 4MB connection in the US). Can anybody see any potential problems with my theory? Also can anybody point me in the direction of some documents on how to add a Second Exchange server as a "replication partner" to our existing Exchange 2000 server, or is that quite self explanitory during the installation? Thanks.

If I may just tell you of the method I used when I upgraded from a 2.53Ghz P4 to a 3.06Ghz one a few months ago: 1. Install new CPU 2. Go into BIOS and make sure HT is enabled. It should be by default but it is worth checking. 3. Boot into Windows XP. 4. Wait approx. 10-15 seconds 5. When the "Your new hardware is installed, please reboot" message appears do as you are told 6. After reboot your new CPU will be recognised as 2 - HT is now working. No reinstallation of OS required, no user intervention required at all. Let WinXP do the job for you!

The warranty only lasting until 5/4/04 is quite correct. When you have an RMA the warranty is for your original purchase and not for the replacement unit - so no new 1/3 year warranty just because you've got an RMA. If that happened everyone would return their drives about a month before the warranty was due to run out just to get a new one. Hitachi have only got about another year to go and then finally the IBM HD's everyone seemed to have problems with will be out of warranty too. With all of the problems with the IBM units, Hotachi would be replacing them indefinitely if new warranties were issued with RMA units.

Quote: I find it totally reprehensible that m$ only allows raid 1 with their server products. At least XP PRO should have software mirroring. after all, it is PRO.... What is the message? PRo users do not deserve a good hard drive mirror? Despicable. They should save raid 5 for the servers and raid 0 and 1 for the Pro. I''ve not tested yet(i will shortly) but i BEt you any money, 2003 standard server won't even support raid 5. I would not be surprised. If anyone knows if server 2003 standard can do raid 5, let me know! What do you mean by "support RAID 5"? If you are on about a software solution then you'd be crazy. There is no way in hell I'd trust a software RAID solution to keep an eye on any of the servers that I run - it has to be a hardware solution all the way. I expect this is why MS (Oh saying m$...why?) only have software support for RAID 1. Windows 2000 of course supports any RAID array configuration you like so long as you've got the hardware to go with it. We run a hardware RAID 5 solution (Some IDE, some SCSI) on all of our Windows 2000 servers.

Well all Neo asked for in return for stopping Smith was "peace". Now unless you wanted him to stand there and say: I want peace. It must last forever, no waiting until I've killed Smith and then going back on the deal. I do not class you hunting humans like pigs peace, so you must not kill them. Maiming them is also not allowed, so let me clarify. You are not to kill or maim humans, in fact lets get a blanket ban on harming humans in general. I mean on both a mental and physical level you understand, just because you've promised to not physically hurt them I don't want you making loud noises all night and depriving them of sleep so they all go mad. Also you are not to scare them, don't creep up on humans and then go all "squid like" and make them run away, I class that as a form of mental torture too and as said above that isn't allowed. Now you must also stop using the humans as fuel. I don't just mean close down the fields where you have them all plugged in like batteries and you simply suck up a few to recharge. I mean fuel in general. So no rounding them up and throwing them into large generators and using them in fuel that way - that too is not allowed. Finally you must allow anybody who wants to leave the matrix to do just that. That doesn't mean dropping them from one matrix into another one where they think they are in reality but are really still hooked up to some super computer. If you are found doing this you certainly shouldn't then drop them into a third matrix and convince them that is reality just because humans would never suspect a double, double-twist. Now I've got all this in writing and I've signed here. I've got it witnessed by two humans, a ghost and something from the matrix. If you could just form yourselves into a pen or other writing impliment and sign your name here, an x will do if you don't have a name. Right, I'll just go away and copy that. The humans will keep one copy and you keep the other and then there can be no arguments. Right, hook me in baby and I'll go kick Smith's arse!! I feel that saying all that towards the end of the film quite possibly would have had people walking out

Quote: [spoilersif u have not seen it!!![/b] not to mention the deal that neo made - the machines could take over when ever they want to and neo could not stop them if they wanted to! However you are missing a major point. Yes the machiens could have taken over whenever they liked, they had more or less taken Zion and the last of "humanity" was about to be wiped out. However, and I'm assuming you did listen to Neo when he talked to the machines They were unable to stop Smith. Smith was not only going to be the end of humanity, he was also going to be the end of the machines. Only Neo could stop Smith and that is why the deal was struck. The survival of humanity in return for the survival of the machines. If the machines had not agreed to the "deal" Neo was proposing then first humanity would have falled, Neo et all. Then Smith would have destroyed the machines - once again humans needed the machines and the machines needed the humans.

Yer that's the one I downloaded. We do have some evaluation CD's for Windows Server 2003 however as I was online I decided to grab the one from the MS Website. It has installed all of the tools with the exception of the RAS & Remote Access Services snap-in. Maybe I'll give the one from the Win2k3 Server CD a go.

We are running a Windows 2000 Active Directory domain here at work. Until two days ago I was using a Windows 2000 Workstation. I had the adminpak.msi package installed from the Windows 2000 server CD which gives me loads of "Administrative" options from my workstation for the domain. All was well, until I upgraded my workstation to WinXP Professional. The adminpak.msi from the Win2k Server CD wont install under WinXP. This wasn't a major issue as I could download the package directly from Microsoft. This I did, it was installed and all was working fine. However.... The option "Administrative Tool>Remote Access & RAS" doesn't appear in my list of tools. A check on the Win2k server reveals that this should launch "rrasmgmt.mmc" but for some reason the new Domain tools don't install this option. Can I simply copy rrasmgmt.mmc from a Win2k machine to my WinXP machine or is there another way of getting this administrative option? Ta

Sorry, but I disagree with everything you've said. I'm a NAV 2004 users as I was a NAV 2003, NAV2001 - you get the idea. It sits in a tony amount of memory even when utilising full system security. Programs do not take longer to load up - well actually I must admit that I don't sit there with a stop-watch, but even with NAV running all of my Office applications load just as quick as when NAV is disabled. Benchamrks show no difference if NAV is enabled or disabled. Boot up is still instant on my WinXP boxes - even after entering my password and letting the very final part of WinXP load there is no waiting around for NAV to load or other applications waiting for NAV to load. Sure NAV is the last icon to appear in the Systray but there is no waiting for it. As I said before, I'm actually using the product and I'm using it on a daily basis. It is not a resource hog, it does not take ages to load - in fact there is nothing at all wrong with it. Add in the fact that for the last x number of years I've been using a NAV product of some description and I have not been infected by a single virus I think that is pretty conclusive evidence of how good it is.

Well as a user of NAV at home since the 2000 version and currently a user of NAV2004 I have to say that all claims of "resource hog" are BS. It doesn't slow the machine down, it doesn't take lots of resources. It sits in the background giving you maximum protection, scanning files as they are executed and in no way slow the machine down. If this program was the "resource hog" some people seem to claim then I'd expect the program to be using a lot of memory, which it isn't. I'd also expect benchmarks be they synthetic, system or game to show a difference when NAV is either enabled or disabled - they do not.

Sorry, been away from the forums for a while. Exactly what I was looking for. Thank you kindly - another link for my "Favourites" list