full-disclosure - Virus Problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <41100554.24436.4A87DB4@localhost>
From: stuart at cyberdelix.net (lsi)
Subject: Virus Problem

> 1) Error message coming after login - "No Paging file found or paging file
> too small" 

To quote from the M$ KB article here:

http://support.microsoft.com/default.aspx?scid=http://support.microsof
t.com:80/support/kb/articles/Q249/3/21.ASP&NoWebContent=1

Unable to Log on if the Boot Partition Drive Letter Has Changed

SYMPTOMS
After you try to log on to your Windows 2000-based computer by using a
valid user name and password, the Loading your personal settings dialog
box is displayed, followed by the Saving your settings dialog box.
However, the desktop does not appear, and the Welcome to Windows logon
screen is displayed again.

NOTE: If the paging file is located on the system or boot partition, you
may also receive the following warning message before returning to the
"Welcome to Windows" logon screen: 

[Limited Virtual Memory]
Your system has no paging file, or the paging file is too small. 

CAUSE
This problem can occur if your Windows 2000 boot partition drive 
letter does not match the drive letter assigned during the initial 
Windows 2000 Setup. Windows 2000 maintains a record of drive letters in a
registry based database and re-assigns drive letters based on Globally
Unique Identifiers (GUID) recorded for each volume. Should the volume GUID
change or be duplicated (by hard drive cloning software), the original
drive letter may not be re-assigned to the boot volume.

This may also occur if you break a system/boot mirror, and then 
attempt to boot to the old shadow drive if the original primary drive is
missing or inaccessible. This is because the volume GUID for the shadow
drive is different than that of the original primary drive and does not
get the same drive letter assigned.

RESOLUTION
... [continues at length] ...

5. With only the system/boot drive in the system, or powered on, boot to a
DOS or Windows 9X Start-up diskette that contains fdisk.exe and run the
following command: 

FDISK /MBR

This re-writes the Master Boot Record and erase the disk signature 
associated with volume GUID. Windows 2000 should assign default drive
letters and allow you logon. Click the article number below for more
information about FDISK: 

69013 FDISK /MBR Rewrites the Master Boot Record

---
Stuart Udall
stuart at@...erdelix.dot net - http://www.cyberdelix.net/

--- 
 * Origin: lsi: revolution through evolution (192.168.0.2)