Anyone learn anything from the ASUS web site?

[Pennywise]

Next I click on Download near the top of the page. Guess what? It goes
back to the previous page.

I tried this several times for Win2K and Win XP and it seems that I was
going around in circles, ending up with nothing.

What they said, but you will have three download choices don't let it
install it's P2P program!

I have a very new mother board and using very old stuff from Asus.
they seem to provide for the chipset then move on to the next,
never updating anything but the bios.

So I 've downloaded everything and have it on on hand - but you'll find nothing
extra that isn't on the CD that came with the Motherboard. (bios excluded).

 

[Pennywise]

What they said,

My bad

Date: Mon, 08 Aug 2011 17:20:34 +0300

My time has been fixed -0800, a dual boot I rarely
use on a system that's known to change time on hard crashes.
They all do, but this one's annoyingly consistant.

 

[Seum]

Hello again Experts

I bought the following motherboard: M4A88TD-V
and wanted to download the files for Win2K and WinXP.

http://support.asus.com/Download.aspx?SLanguage=en&m=M4A88TD-V+EVO/USB3&p=1&s=24

From the page listed above:

Support For
Motherboard M4A88TD-V EVO/USB3

Under the Download Tab:

OS: Win2K

23 Files found

Next I click on Download near the top of the page. Guess what? It goes
back to the previous page.

I tried this several times for Win2K and Win XP and it seems that I was
going around in circles, ending up with nothing.

TIA

 

[Mike Easter]

OS: Win2K

23 Files found

Next I click on Download near the top of the page.

That is not the correct action.

The 23 files for Win2k are of 5 different classes/groups; each group has
a + mark beside its name.

You must expand that nested + condition for each/any group which you
want to access -- the site doesn't intend for you to download all 23
files as a 'package'. The Download tab near the top of the page is for a
different function.

When you expand the + by clicking on it for one of the items such as
Manual, you will find 9 choices for manual 'inside', only one of which I
would want, and the interface which results allows you to download from
any one of several choices of download site.

Guess what? It goes back to the previous page.

That is the intended function of the upper Download link to which you refer.

 

[Paul]

Hello again Experts

I bought the following motherboard: M4A88TD-V
and wanted to download the files for Win2K and WinXP.

http://support.asus.com/Download.aspx?SLanguage=en&m=M4A88TD-V+EVO/USB3&p=1&s=24


From the page listed above:

Support For
Motherboard M4A88TD-V EVO/USB3

Under the Download Tab:

OS: Win2K

23 Files found

Next I click on Download near the top of the page. Guess what? It goes
back to the previous page.

I tried this several times for Win2K and Win XP and it seems that I was
going around in circles, ending up with nothing.

TIA

When you select "Win2K", you should see a loading icon for a short interval
and then:

23 files found

+ Qualified Vendor List (1)
+ BIOS (9)
+ BIOS-Utilities (3)
+ Utilities (1)
+ Manual (9)

If you click one of the five blue "+" signs, that level of menu will
open up. Or, you can click on the blue word next to the "+".

If I click on BIOS, I see "Version 1702". There is a blue "Global" button
in that entry, and clicking that should start the download of version
1702 of the BIOS. And so on.

If you select an OS version and there are no returned files, then
obviously the OS is too old to be supported. Normally, that would
not happen, because the OS list in the menu is context sensitive,
and unsupported OSes should not even be listed. But there was a time,
when that kind of thing could have happened - OS listed, but no files
to be seen.

You do not click the Download again at the top of the page, because
that takes you back to start the drill down process for a new download.

Instead, you want to use the blue items nearer the bottom of the page,
to get what you need.

Paul

 

[Seum]

My bad

Date: Mon, 08 Aug 2011 17:20:34 +0300

My time has been fixed -0800, a dual boot I rarely
use on a system that's known to change time on hard crashes.
They all do, but this one's annoyingly consistant.

Thaaaannnkkk You Mike, Paul, P.W. and P.W.

That ASUS web site is one of the most barren I have seen. They rarely
put a label on anything, especially the buttons. So, you have to keep
guessing all the time, unless you visit the web site regularly for some
kind of holiday=vacation. What effort would it take to insert a couple
of words here and there? Has anyone tried to fill out their application
forms? You have to nitpick down to the smallest thing, even if your
query is straightforward.

What would be a better web site and better motherboards?

Thanks again to you all

 

[Paul]

What would be a better web site and better motherboards?

You let their web site bother you ?

It's better in some ways, than it used to be

Count your blessings. At least some of the downloads,
run at full rate, rather than being throttled. In response
to complaints the downloads were slow, Asus eventually started
using Akamai for some portion of their hosting. And then your
download runs at full rate (i.e. limited on your end).

Paul

 

[Seum]

You let their web site bother you ?

It's better in some ways, than it used to be

Count your blessings. At least some of the downloads,
run at full rate, rather than being throttled. In response
to complaints the downloads were slow, Asus eventually started
using Akamai for some portion of their hosting. And then your
download runs at full rate (i.e. limited on your end).

Paul

Thanks again Paul.

Without you, ASUS would be nothing

 

[Flasherly]

What would be a better web site and better motherboards?

Some have live BIOS updates out of windows metaicons or something
clicky other than a DOS boot rescue DVD -- rest is just running a
program or doing a driver within the OS platfrom.

Works fine, although stick to the Chinese routes. Not much if any
on-the-fly tweaking for my severely limited and debilitated, older
FireFox - stops scripts, ulterior links and ties to java iceage cold
in their tracks.

When doing absolutely necessary things like online color cordinating
accessories at Sears or WallysMart, or putting up with Yahoo's crap, I
keep the latest Opera 11.5 for getting by confidence levels. Anyway,
both worked on the DOS BIOS FLASH section under your link for
utilities.

Ever tried the Farmer in the Dell, Hewlett Packard, IBM? They can be
"interesting".

 

[Seum]

Some have live BIOS updates out of windows metaicons or something
clicky other than a DOS boot rescue DVD -- rest is just running a
program or doing a driver within the OS platfrom.

Works fine, although stick to the Chinese routes. Not much if any
on-the-fly tweaking for my severely limited and debilitated, older
FireFox - stops scripts, ulterior links and ties to java iceage cold
in their tracks.

When doing absolutely necessary things like online color cordinating
accessories at Sears or WallysMart, or putting up with Yahoo's crap, I
keep the latest Opera 11.5 for getting by confidence levels. Anyway,
both worked on the DOS BIOS FLASH section under your link for
utilities.

Ever tried the Farmer in the Dell, Hewlett Packard, IBM? They can be
"interesting".

My thanks to everyone for your help. Yesterday I downloaded all I could
for my dear ole Win2K.

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

I was surprised that ASUS still has the Win2K progs. Now back to trying
to install Win2K on a "strange" box.

First I have to coax the ASUS BIOS etc., to accept my "new" offerings
- new venture fro me. Don't forget to pull me up, if you find me
in a rabbit hole.

 

[Paul]

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

 

[Seum]

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

 

[Seum]

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!!

 

[Paul]

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