Re: Anyone learn anything from the ASUS web site?

Seum wrote:
Paul wrote:
Seum wrote:
Paul wrote:
Seum wrote:


Question: Would the Fujitsu-Siemens XP CDs have some kind of hidden program that can sense the computer it is being installed in?


Have you tried it yet ? What happened ?

If it was me, I would only have a single (target) hard
drive connected, while fooling around. If something happens,
then you can connect up the other disk with its working OS.

Paul

No message was given Paul. It just would not load. However, that could
be because of my "new" computer and ASUS.

I setup the "new" box this morning with my Seagate HD (3 partitions, one
free 117 GB and the other two much larger). I put my Win2K CD in the
tray (foolishly) thinking that I might be able to NTFS that free partition. The Seagate was ignored and I was back in the old round and round circles.

Now I am trying to get the 750GB disk clear, as you suggested. I was trying to create partitions on a WD 370GB disk so that I could move the info on the Seagate to there. I started to reduce the partition on the WD by 50% and then I had a message about the disk being corrupted and that the drive needed the ChkDsk. I did a search for ChkDsk and it opened when I clicked it. It immediately disappeared into the desktop and was invisible afterwards. I finally nailed it down in System32. There I clicked it and it flew off again. Next I right clicked it and sent it to the desktop. There I clicked it again and it opened a black window and started writing lots of info. Then it closed the window and disappeared with it. What kind of idiot program is that, or what idiot produced it?

Now I'll have to look through the Win2K data that I downloaded from ASUS first and then try to apply it to the ASUS computer.

Thanks for reading this nonsense :-)


Chkdsk is a command line program. Yes, it runs in the OS, from a GUI window,
but the program doesn't dump its output directly to the GUI. Instead, chkdsk
hides in the weeds, and dumps to things like the Event Viewer. All it passes
back to the GUI is success or failure.

You can a command window (cmd.exe) first, then run chkdsk from there.

If you did

chkdsk C:

and C: was "busy", then chkdsk may set a registry setting, which causes
chkntfs to run on the next boot. So a quick exit of chkdsk, could
imply it was not able to obtain exclusive access to the partition
in question ("busy") and instead scheduled chkdsk to run on the
next boot of the OS.

If you have a real Windows installer CD, then it may have an option
to start the Recovery Console, which gives a command prompt just like
cmd.exe would from the regular OS. This is an example of instructions
for WinXP.

http://www.kellys-korner-xp.com/win_xp_rec.htm

Since you are "flush with software" and have many discs at your
disposal, if you have a real Windows 7 DVD, you can boot that
to a recovery console as well. And then run chkdsk from there
if you want. That would be the "command prompt" option here.
You'll get a black MSDOS window, just like in a regular OS.
You can use the Windows 7 DVD, to do maintenance on older OSes,
within reason. And chkdsk would be an example of something
that would work.

http://0.tqn.com/d/pcsupport/1/0/i/4/-/-/windows-7-startup-repair-7.jpg

Chkdsk options vary, from one environment to another. For example,
the chkdsk in Windows 7 may support a couple more options. Check
a website first to see what those options are.

http://www.w7forums.com/use-chkdsk-check-disk-t448.html

"Command Prompt Method:

Alternatively, you can use the command prompt to perform a scan on a
drive letter of your choice by running "chkdsk x:" where x is your
drive letter. The manual scan options are:

* /F Fixes errors on the disk.
* /V On FAT/FAT32: Displays the full path and name of every file on the disk.
On NTFS: Displays cleanup messages if any.
* /R Locates bad sectors and recovers readable information (implies /F).
* /L:size NTFS only: Changes the log file size to the specified number of
kilobytes. If size is not specified, displays current size.
* /X Forces the volume to dismount first if necessary. All opened handles
to the volume would then be invalid (implies /F).
* /I NTFS only: Performs a less vigorous check of index entries.
* /C NTFS only: Skips checking of cycles within the folder structure.
* /B NTFS only: Re-evaluates bad clusters on the volume (implies /R)

"CHKDSK x: /F /R" would perform a full scan (including bad sectors) and
attempt to fix them.
"

Etc,
Paul

Many thanks again Paul.

I wanted to move all the files files from the Seagate to the WD1600 and it did not succeed. I tried partitioning the WD1600 and had another failure. As you suggested I used the ChkDsk but with no success. The following, if you have a few days to spare, are the results.

=================================================================
Western Digital Drive WD1600

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

=================================================================
Disk Management

The volume you have selected to shrink may be corrupted.
Use ChkDsk to fix the corruption problem, and them try to shrink the volume again.
=================================================================
C:\Users\Administrator>chkdsk F:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
44480 file records processed.
File verification completed.
54 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
50534 index entries processed.
Index verification completed.

CHKDSK is scanning unindexed files for reconnect to their original directory.
Detected orphaned file AnimationAttributes-xref.html (34288), should be recovere
d into directory file 19564.
Detected orphaned file ContentResultSetCapability.idl (43664), should be recover
ed into directory file 29467.
Detected orphaned file InteractiveFileIOException.idl (43745), should be recover
ed into directory file 29467.
Detected orphaned file TestComponentB.java (44191), should be recovered into dir
ectory file 30103.
5 unindexed files scanned.
Detected orphaned file ChangeOrderDemo.java (44383), should be recovered into di
rectory file 30316.
0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
Examining an index entry with id 871 in index $SDH of file 9.
Examining an index entry with id 871 in index $SDH of file 9.
44480 file SDs/SIDs processed.
Security descriptor verification completed.
3027 data files processed.
The Volume Bitmap is incorrect. <-----<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Windows found problems with the file system.

========================================================================
========================================================================
Run CHKDSK with the /F (fix) option to correct these.

155645720 KB total disk space.
7884200 KB in 34671 files.
13284 KB in 3029 indexes.
0 KB in bad sectors.
115444 KB in use by the system.
65536 KB occupied by the log file.
147632792 KB available on disk.

4096 bytes in each allocation unit.
38911430 total allocation units on disk.
36908198 allocation units available on disk.
Unable to obtain a handle to the event log.

=================================================================
C:\Users\Administrator>chkdsk F: /F
The type of the file system is NTFS.

CHKDSK is verifying files (stage 1 of 3)...
44480 file records processed.
File verification completed.
54 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
50534 index entries processed.
Index verification completed.

CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file AnimationAttributes-xref.html (34288) into directory file 19564.
Recovering orphaned file ContentResultSetCapability.idl (43664) into directory file 29467.
Recovering orphaned file InteractiveFileIOException.idl (43745) into directory file 29467.
Recovering orphaned file TestComponentB.java (44191) into directory file 30103.
5 unindexed files scanned.
Recovering orphaned file ChangeOrderDemo.java (44383) into directory file 30316.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
Inserting an index entry with Id 871 into index $SDH of file 9.
Repairing the security file record segment.
Deleting an index entry with Id 871 from index $SDH of file 9.
44480 file SDs/SIDs processed.
Cleaning up 16 unused index entries from index $SII of file 9.
Cleaning up 16 unused index entries from index $SDH of file 9.
Cleaning up 16 unused security descriptors.
Security descriptor verification completed.
3027 data files processed.

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.

CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

155645720 KB total disk space.
4812200 KB in 34670 files.
13284 KB in 3029 indexes.
0 KB in bad sectors.
115444 KB in use by the system.
65536 KB occupied by the log file.
150704792 KB available on disk.

4096 bytes in each allocation unit.
38911430 total allocation units on disk.
37676198 allocation units available on disk.
Unable to obtain a handle to the event log.

C:\Users\Administrator>

After several hours, here is the result :-(
=================================================================
Disk Management

The volume you have selected to shrink may be corrupted.
Use ChkDsk to fix the corruption problem, and them try to shrink the volume again.
=================================================================

If you get this far Paul, THANK YOU!!

So the question for you would be, have you managed to run CHKDSK
and have it come back clean ? Or is it reporting different problems
on every run, and claiming to fix them ? If it is corrupting
over and over again, that could be a hardware problem. Especially
if you're doing the CHKDSK runs one after another, in the same
session, without rebooting.

You've run it twice, now I'd run it a third time. Try without /F
and see if a "read-only" scan is clean or not. You'd use the
"fix" option, if it needed to be fixed again.

If it comes back clean on your next try, then you can try
shrinking if you want. Because, when the shrink does a disk
check first, that check will then be clean. (Note that, by default,
Windows 7 won't allow shrinking by more than around 49%. That was
my experience. And that happens, because Windows 7 is too stupid
to move some metadata out of the way - even though a third party
tool knows how to do that!)

And think about, when the system reboots, is it rebooting cleanly ?
Or are you turning off the power, because it got stuck or something ?
If you do "dirty" shutdowns on it, killing it with the power
switch, then... expect trouble.

Paul
.

Relevant Pages

  • XP Media Center, runs slow, has glitches
    ... Windows Explorer) to be opened. ... select a folder to choose files from, ... The latest chkdsk results ... 75967340kb available on the disk ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Check disk has been canceled?
    ... In My Computer or Windows Explorer, right-click the drive you want to ... Runs Chkdsk by using the /f parameter. ... the disk checking for the next time you restart your computer. ... The /d switch restores the machine to the default behavior; all drives are ...
    (microsoft.public.windowsxp.general)
  • Re: WINDOWS EXPLORER
    ... System File Checker tool in Windows XP Home Edition ... anything, chkdsk already did it. ... The type of the file system is NTFS. ... A disk check has been scheduled. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: WINDOWS EXPLORER
    ... Or right click the Internet Explorer icon on your Desktop ... MS-MVP Windows Shell/User ... to do anything, chkdsk already did it. ... A disk check has been scheduled. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: HELP!! What a mess I got!!
    ... needing chkdsk, then onto the desktop. ... recovering, it said "Recovering KEY files" and then the hard drive ... what would happen, and the computer now says "DISK BOOT FAILURE, ...
    (comp.os.os2.misc)