Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Repair can't find file "asms"

29 views
Skip to first unread message

John Gemski

unread,
Jul 31, 2002, 3:15:36 PM7/31/02
to
I'm trying to repair my XP installation. I chose
the "repair" option from within setup (using the XP Home
Edition CD). It gets thru the first copy operation and
then re-boots. Upon reboot I get an error that says it
can't find the file "asms" and to enter the proper address.
The address panel is showing "GLOBALROOT\DEVICE\CDROM0
\I386". I assume this is the I386 directory on the setup
CD. I tried that directly - still nothing. Seems to be
looking for a file "asms" while "asms" is actually a
directory under i386.

Any ideas?

John

Spyder32

unread,
Jul 31, 2002, 4:14:48 PM7/31/02
to
Try this to fix your problem:

01. When you receive the error, start a CMD session by
pressing SHIFT+F10.

02. Type regedit.exe and press Enter.

03. Select HKEY_LOCAL_MACHINE.

04. On the File menu, press Load Hive.

05. Load %Windir%\System32\Config\System.sav.

06. Enter AAA when prompted for a name.

07. Navigate to:
HKEY_LOCAL_MACHINE\AAA\ControlSetn\Control\Class\{4D36E965-
E325-11CE-BFC1-08002BE10318}, where ControlSetn is the
lowest control set.

08. Delete both UPPERFILTERS and LOWERFILTERS.

09. Repeat step 07 and 08 for every control set.

10. Select HKEY_LOCAL_MACHINE and Unload Hive from the
File menu.

11. Close the CMD prompt and allow setup to try to read
the 'Asms' file.

I hope this helps you out, I have seen this problem before
on a friends computer and he called me over. I believe
this is exactly what I did to repair it.

-Spyder32

>.
>

Mike Truitt [Microsoft]

unread,
Jul 31, 2002, 4:29:41 PM7/31/02
to
John,

Just curious, was this installation done from MSDN media? If not, I have
included several possible fixes below. I would actually try Solution D
first if possible. Running regedit can be tricky and may make your system
unbootable after being used.

Solution A:
1. At the error message press SHIFT-F10 and bring up a command window.
2. Run REGEDIT.EXE
3. Load the %windir%\system32\config\system.SAV hive
4. Goto HKEY_LOCAL_MACHINE\SYSTEM\Select\current and check what the
current control set is.
5. Goto
HKLM\Test\ControlSet****\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318
} and delete the upperfilters and lowerfilters registry keys

Solution B:
If REGEDIT.EXE does not load at the SHIFT-F10 command prompt then you must
do a parallel install and then follow the same steps as above and then load
the system.SAV hive from the old install and remove the registry keys.

Solution C:
If the customer is not using hologramed media, IE they burned a CD, they
should try setup from a retail hologramed CD. To verify boot to recovery
console and check c:\$win_nt$.~ls directory and look for ASMS directory.
If it is missing or the files are zero bytes in size then CD-ROM was not
burned correctly.

Solution D:
Copy the I386 folder to the hard drive and run setup from there

Solution E:
Check to see if the drive letter has changed for the CD-ROM. You may have
try multiple drive letters to find it.

Solution F:
CD/ROM hardware is bad and needs to be replaced.

Best regards,

Mike Truitt
Microsoft Corporation

0 new messages