Disabling TRIM - on Windows PE 3.0?

[RU482]

I'm working with a menlow atom based computer that has a PATA-to-SATA bridge that is "pre-windows7", i.e it does not support TRIM. This means that you cannot load windows 7 directly from a DVD to an SSD...you first have to build an image on an HDD, disable TRIM in Win7 (elevated command prompt - cmd /k fsutil behavior set disabledeletenotify 1)

Anyway, ignore the fact that there are alternatives....I have to load an OS to an SSD in this computer using Microsoft System Center Configuration Manager 2007 R3 Operating System Deployment (OSD)....which utilizes a Windows 7 based Windows PE 3.0.

since it's based on Windows 7, I assume it also has TRIM enabled. When I go to load an image, it bombs out and loses the SSD.

Is there a way, in preparing the Windows PE boot disk, to disable TRIM?

 

[yinan]

I do not think PE is your problem, I think the drive is too fast for the controller and it is bombing out. And TRIM is in the drive not the OS and IIRC correctly PE does support TRIM.

 

[RU482]

I do not think PE is your problem, I think the drive is too fast for the controller and it is bombing out. And TRIM is in the drive not the OS and IIRC correctly PE does support TRIM.

I beg to differ. This is actually a product my company sells. We've shipped a few thousand units with SSDs and had no problem. In order to get the SSD to work with windows 7, we had to disable TRIM on the OS side.

We image the computers using Symantec Ghost, which boots into a DOS session (no TRIM there!).

I have a government customer that insists that they must use Microsoft System Center Configuration Manager 2007 R3 Operating System Deployment (OSD) to image the computers at their facility...thus the issue with Windows PE. Windows PE3.0 is based on Windows 7, thus the thought that it probably has the ability to TRIM SSDs.

 

[VexQuake]

I havent posted very many times here (lurking for 10 years +)
found this for you.
http://social.technet.microsoft.com.../thread/d5d2eb52-8d56-44ec-af0d-5cce3e1ba5e4/
in short you cannot deploy a ghost image with SCCM. You will need to image a machine with your ghost image and then capture it into a WIM file ( http://technet.microsoft.com/en-us/solutionaccelerators/dd407791 )
then you can use SCCM to deploy the image.