dhope

Hi, I installed Server 2008 a couple of months ago and the initial 60 day grace period expired when I was on holiday. I returned and it was asking me to activate, as expected. I chose 'activate later', went to the command prompt, entered 'slmgr -rearm' and carried on as usual. As this is the first time I've rearmed I expected the activation prompt to vanish for 60 days, but it's still prompting me to activate each time I log on. Using 'slmgr -dli' says License Status: Notification Notification Reason: 0xC004F056 Anything I should do to continue evaluation? Thanks in advance Duncan

Ugh, thought it might be that, thanks. The eOpen site always seems incredibly slow for me. Last time I tried downloading it was giving all of 30kb/sec on the ~3GB download. Ah well, here we go again (Don't suppose there's a torrent, or is that too much to ask?)

Hi, I've installed Server 2008 in VMWare but when trying to enter the product key I get the message: "The product key you have entered will not work with this edition of Windows Server" The key is valid and the ISO was downloaded from Microsoft http://www.microsoft.com/downloads/details...;displaylang=en It's not that I've entered the key incorrectly and if I put in an invalid key I get a different message: "The product key you have entered does not appear to be a valid Windows Server product key" I've tried Standard and Enterprise installations, so wondering what other edition there is. More likely to be that the volume license ISO is different from the one I downloaded? Thanks

Sorry I took a while to reply. Hope you all had a good Xmas and New Year So yeah, I'd uninstalled Alcohol, removed Starforce and reinstalled the latest (upgraded) version of Daemon Tools. Things carried on working fine, then I got curious about Vista, so upgraded once it was released to MSDN. When I installed it I tried with the 2x1GB matched RAM and it'd never finish the install or reach the desktop - it'd start rebooting during the 'Vista index' thing (where it scores your machine based on the hardware). After swapping to 2x512MB then the install completed and machine has been solid as a rock. So after all that I think it was the Shuttle not liking the memory (despite the memory passing all tests I could throw at it). Starforce was probably doing something funky, but Vista with Daemon Tools has just been fine for the last couple of weeks. Quite nice to get a rating of 3.7 on a system that's running an unsupported nForce2 motherboard. Anyway, I think things are solved now. Unless I go back to 2003 then hopefully no more problems. Many many many thanks for all your help, kept me sane knowing that not everyone was as stumped as me

I upgraded to Daemon Tools 4.06 and SPTD 1.35 but was still getting reboots. I next downloaded and installed the nForce 9.35 Unified Remix, a collection of the latest (some Vista, others tweaked inf) drivers - while having a couple of problems with the internal NIC disappearing I noticed that I had StarForce (copy protection software that can screw with Daemon/SPTD) installed, probably from some game I've since removed - I uninstalled StarForce and everything seems to be more stable since. I was noticing Civ4 Warlords had been playing up a lot, but that seems to be rock solid since, so I'm thinking it could be one of the Vista/Customised drivers works better with Win2003 R2, or maybe StarForce was causing problems, I know it's a hugely unpopular piece of software with a track record of screwing up people's machines... I'll keep an eye on things and update in a week or so, but things could well be that it's resolved. If so then many thanks for your help in tracking down the problems. Duncan

Hi there, I noticed I was running a slightly old version of Daemon Tools (4.03) and have updated to 4.06 Also updated from sptd 1.25 to 1.35. Also stopped Daemon Tools and Alcohol (since I'm guessing the drive emulation works the same way). I'll see if it makes the system more stable. Might be that Vista will cope better with my system/software - guess we'll find out in the next month or so when the final release arrives on msdn. Thanks again, will keep the board updated with any results.

Linked is the latest MEMORY.DMP (compressed from 92MB -> 14MB RAR file). Hopefully it'll help diagnose the problem http://w11.easy-share.com/671063.html Thanks in advance if you can have a look Duncan

Cluberti, many thanks for your advice, apologies for the slow reply. This weekend I picked up some old RAM from home that I know works fine with this machine (matched pair of 512s to relpace the matched pair of 1024s). It's still rebooting so I've made the changes you have suggested and will post the dump file when it next happens. Cheers again, Duncan

As mentioned in my first post, Event logs don't seem to know anything about it, the first they know is after a reboot when I see a "previous shutdown at xx was unexpected" message.

Attached and linked are 6 minidumps in a zip file from the last 3 days. If anyone's able to provide insight it'd be appreciated. If it appears it's the memory then I'll be grabbing a spare pair of matched 512MB's in a fortnight. http://d.turboupload.com/d/1086853/Mini101506-01.zip.html Cheers Mini101506_01.zip

Hi there, thanks for the quick response. Temp is fine I think - it's worked happily in the past with IDE drives running XP-Pro with the graphics card overclocked (so more heat). Just d/led MBM5 and it's showing Case 52C, CPU 44. Just after MBM I got my first BSOD though. MEMORY_MANAGEMENT STOP: 0x1A (0X401, 0XC00183CC, 0X18FDE067, 0XC0018319) Which leads me to believe it may be the RAM after all. I've owned Shuttles in the past and they seem to be notoriously picky about which RAM they choose to work with. This is a matched pair from Crucial though that passes all the tests I can throw at it... From http://www.ocforums.com/showthread.php?t=420646 0x1A, 0x4E, 0x50 These errors are all most likely caused by a device driver or other system program running amok. Antivirus software can actually cause these errors (NortonAV had an issue that would repeatedly generate a MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA, for instance) as well, since they're somewhat priveleged on the system. If you have recently installed a new driver, roll it back. That said, if you've shifted drivers around a lot, they may be indicative of a hardware problem. Drivers was also something I was wondering about - I've not installed any new drivers, but it is the first time Server 2003 R2 has been installed on this machine with this memory and these hard disks, so might be problems there? I don't know much about analysing memory dumps to find out if a specific driver is causing the problem, but if there's value in saving anything then let me know Cheers

Hi All, First question here, so apologies if I'm in the wrong forum etc. My home desktop is a Shuttle SN45Gv3 Athlon 3200+ (XP, Barton) 2GB PC3200 (Crucial) 2 x 320GB SATA2 (Quantum 6V320F0) nVidia GeForce 6800 The SN45Gv3 motherboard is an nforce2. I'm not using the onboard NVRaid. Running Windows Server 2003 R2 (v5.2.3790) as my desktop OS (though not used any of the 'conversion' tools, just turned off the bits I don't need manually). So, basics done, the machine reboots randomly. There doesn't seem to be any reason why. Event logs don't seem to know anything about it, the first they know is after a reboot when I see a "previous shutdown at xx was unexpected" message. I've just set the machine to not reboot automatically so I'll post BSOD when they appear. I've run memtest and MS' memory diag tool without any problems. Basically I'm at a bit of a loss where to look next. I've reinstalled Windows not too long ago and it's made no difference, so I don't think it's a corrupt dll or similar. Any help greatly appreciated, Cheers Duncan