#1
|
||||
|
||||
![]() أخوتي الكرام iastor.sys شريت جهاز جديد مواصفاته منيحه معالج كور تو ديو 4 جيجا رام ومذر جيجا بايت المهم بدي انزل وندوز 7 نسخه 64 بت والسبب انه فيه برامج لازمني ما بتشتغل الا على 64 بت للأسف نزلت من الأنترنت 3 نسخ حجم كل واحده فيهم 3 جيجا وكل مره بتطلع الي مشكله جديده ورساله خطأ جديده وبرضو شريت نسختين من محل كمبيوتر عنا وبرضو نفس رسايل الخطأ وبرضو رساله خطأ ntoskrnl.exe وغيرها من رسايل الخطأ وعدم استكمال التنصيب في بعض النسخ بحث في الأنترنت لعلني اجد الحل لاقيت كثير بتكلموا عن هالمشكله لكن الموقع لغة انجليزيه وانا لغتي مش كثير بالانجيلزيه طبعا نزلت نسخه 32 بت حاليا حتى امشي اموري عليها مع العلم جهازي بدعم 64 بت وهذه الشئ واثق منه مثل ما انا واثق في منتدى زيزوم واعضائه لا استطيع ان ارفق ملف هايجك لأنه ما قدرت انصب وندوز 64 بت حجم الصوره كبيره هذه رابطها http://www4.0zz0.com/2010/12/01/09/783936533.jpg بتوضح انه بدعم 64 بت http://www4.0zz0.com/2010/12/01/09/657562382.jpg هذا كلام من موقع اجنبي عن جزء من مشكلتي اقتباس: اقتباس: The can occur if this mass storage drive driver is corrupt or not compatible with the system. Please contact the mass storage drive’s manufacturer to obtain the latest driver. Or you may skip adding the driver during the deployment to check the result. اقتباس: You were right. I went ahead and downloaded the latest version of the Intel(R) Matrix Storage Manager Driver 8.9.0.1023 and for testing purposes, only added the x64 bit version of the driver to the MDT Out-of-Box Drivers node. Plus, I only allowed that one driver to be available during the Inject Drivers task by creating a Selection Profile (MDT 2010) and only included that one driver. Both Vista SP2 (x64) and Windows 7 (x64) worked great!!! Thanks for pointing me in the right direction. اقتباس: The below problem has been resolved, the problem was a driver folder was listed in the registry as a source to get drivers. once the C:\drivers and C:\dell was deleted then the problem went away. I have the same issue with the iastor.sys, but with the USMT refresh only. I have tried using the latest driver from intel, but that does not work. I have this problem on the several WDS/MDT sites I have running, so it's not a bad MDT, it happens on a real machine or a hyperV VM it does not matter the harware type. I can use the same TS from a PXE boot and I can drop the preconfigured windows 7 .wim image fine. If I go to do a USMT refresh from XP to win 7 64bit I select the same TS and I get the iastor.sys error on the second reboot which is where it would boot to the desktop and finish up the TS. I have tried setting a selection profile for just that driver in the TS, still same issue. I have set the inject driver to nothing and I still get the error. I even setup a new MDT deployment share with just the Win 7 .wim file, the win 7 source files, and the working iastor.sys driver so there was nothing else for it to grab, this fails with the same error. I've even tried mounting the win 7 image and placed the correct driver in the c:\windows\system32\drivers, but this did not work. the problem is it is injecting a 2010 version of the Driver 8.9.0.1023 and I found the 6/4/2009 version works. I am using MDT 2010, server 2008 enterprise with WDS enabled. any help would be appreciated أكثر... |
مواقع النشر (المفضلة) |
|
|
![]() |
||||
الموضوع | كاتب الموضوع | المنتدى | مشاركات | آخر مشاركة |
رسايل رومانسية | RSS | Arabic Rss | 0 | 11-03-2010 11:23 PM |
كيف اعرب جهازي وندوز7؟ | RSS | Arabic Rss | 0 | 11-03-2010 06:31 PM |
ابعت رسايل زي ما تحب | RSS | Arabic Rss | 0 | 09-08-2010 04:48 PM |
شوفوا لي حل في وندوز7 | RSS | Arabic Rss | 0 | 05-28-2010 11:32 AM |
|