Precision M4500 Owner's Lounge

My condolences. I have thought about this also but not tried it. When I am faced with this sorta problem the first things I do is a complete wipe of the disk including a rewrite before installing.

 

I have seen the same thing. Has anyone solved this?

 

I know this is offtopic, kinda but you should probably get something different to McAfee. It's a bit of a false positive maniac.
Here's what I wrote in another post earlier.

 

Interesting. Well, I don't really know what exactly your problem might be, but I have this suspicion there might be some issue with that machine's BIOS. I can't really put my finger on it, but there's a number of minor and not-so-minor issues here and there that give me the feeling that something is fishy somewhere. The machine works well enough under the OS it was meant for, but I am not surprised that people run into trouble in off-design scenarios. I know this is not much help, so take it for what it's worth...

 

I have just got my M4500 fully operational, but I am still waiting for my E/Port Plus. Hence a question I cannot answer myself and I am loathe to actually use the trial and error method on this one anyway.

There is one eSATA port on the M4500, there is also an eSATA port on the docking station. Can they both be used at the same time? (As opposed to being two mechanical sockets leading to the same controller port)

 

A story that couldn't be simpler. I just moved my existing SSD with Windows 7 and Ubuntu 10.04 installations from my Latitude D830 to the new M4500. Ubuntu just booted up, everything worked right away. I am using Ubuntu 10.04 64bit with a newer kernel version (2.6.35) and 260.19.29 NVidia drivers.

Windows 7, on the other hand, took a couple of hours to be usable again - still not too bad, because I saved the trouble of a completely new install.

 

Just a quick idea, but doesn't the 2008 DVD have a tool to check for hardware compatibility? Or alternatively, doesn't Microsoft offer tools for that online?

Might be a good start to troubleshoot.

 

like i said before, when i increased the SHADER CLOCK significantly FIRST, i am able to increase the core clock and mem clock...

use GPUtools to do so. Again, you need to increase the shader clock FIRST, by like 100mhz+ or so, and you will be able to see that now you can oc others.

i oced mine without any problems. 1800m

 

Most likely the latter is the case, but it doesn't make a difference. eSata can be daisy-chained, so one controller is enough. Performance should not be a bottleneck for you.

 

Well, that's obvious, since you generally cannot boot Windows on hardware that is different from the one it was installed on. Most imaging programs these days, however, allow you to create disk images that are modified to instruct Windows to re-initialize the HAL to work on new hardware. This is generally the only proper way to transfer an installation to different hardware. If you had done that, you'd probably still have to update a few drivers, but otherwise you'd be fine.

Linux may sometimes be easier to transfer to different hardware because of its completely different kernel architecture.