Before you go off and format your box again, ask yourself this -- Have
you waited long enough? Upon building a new XP x64 rig (Asus A8N SLI,
4000+, etc.), I ran into this same aciptabl.dat hanging issues... but it
wasn't hung! I waited about 5-10 minutes and it finally booted. It seems
this is a one-time configuration/bug. Subsequent reboots take less than
30 seconds.

Just food for thought.

Rafael Rivera
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/Rafael

RE: READ THIS: acpitabl.dat issues? by Spido

Spido
Mon Jun 06 14:52:01 CDT 2005

Unfortunately for me this problem has never "fixed" itself.
I suspect that it is the BIOS [Asus A8V Deluxe v1009]. There
are newer revisions [v1013.007 latest] but these appear to be
problematic [mem dividers etc] - so I will wait until Asus can
fix that problem and then try the latest rev..

Interesting problem however - I've searched everwhere for an
answer and so far nothing has even come close - nothing on the
support pages and about 10 items from google...

Andrew H.

"Rafael Rivera [Extended64.com]" wrote:

> Before you go off and format your box again, ask yourself this -- Have
> you waited long enough? Upon building a new XP x64 rig (Asus A8N SLI,
> 4000+, etc.), I ran into this same aciptabl.dat hanging issues... but it
> wasn't hung! I waited about 5-10 minutes and it finally booted. It seems
> this is a one-time configuration/bug. Subsequent reboots take less than
> 30 seconds.
>
> Just food for thought.
>
> Rafael Rivera
> Extended64 | http://www.extended64.com
> Blog | http://www.extended64.com/blogs/Rafael
>

RE: READ THIS: acpitabl.dat issues? by Spido

Spido
Sat Jun 18 14:06:02 CDT 2005

Finally found the problem - it was not the BIOS as first thought, but the disk
with 10 mounted volumes on it[D0] which is my XP32 install. Disabling this
disk fixes the problem... although I need to investigate this a bit more as I
would like to use some of the mounted volumes on it = games etc...

Long post following.... :)

Anyway in case anybody is interested, here's a bit of history first....
I have 2 disks[D0-200GB and D1-80GB] connected to the Promise controller as
RAID0 - each disk is on a separate FT array[FT1 and FT2]. XP32 on the 200GB
and XP64 on the 80.. I choose which OS to boot from the boot selection option
on the Asus A8V - TAB + F8...

After the installation X64 booted up fine[no 3-5 min delay] and picked up
the 10
volumes mounted on DO - that was to be expected. After installing drivers
etc for
vid and rebooting I noticed the delay - so naturally I thought it was the
vid drivers
so I removed those = no change.

So I ignored this annoyance for the time-being hoping that it might go away
or at
least when I finished installing all the drivers etc I could search forums
etc for
some help.

After a couple of weeks of trying to find a solution, I finally remembered
that on
the first boot after installation, the boot was quick and then remembered
that the
first disk D0 with all the mounted volumes was picked up... and then the penny
dropped.. So I disabled that disk in the hardware profile and now the boot
time
is back to normal..

Hope this might help some others... I will investigate why it takes such a
long time
to boot with that disk enabled. Didn't see any problems with it when it was
enabled
however....

AH

"Spido" wrote:

> Unfortunately for me this problem has never "fixed" itself.
> I suspect that it is the BIOS [Asus A8V Deluxe v1009]. There
> are newer revisions [v1013.007 latest] but these appear to be
> problematic [mem dividers etc] - so I will wait until Asus can
> fix that problem and then try the latest rev..
>
> Interesting problem however - I've searched everwhere for an
> answer and so far nothing has even come close - nothing on the
> support pages and about 10 items from google...
>
> Andrew H.
>
> "Rafael Rivera [Extended64.com]" wrote:
>
> > Before you go off and format your box again, ask yourself this -- Have
> > you waited long enough? Upon building a new XP x64 rig (Asus A8N SLI,
> > 4000+, etc.), I ran into this same aciptabl.dat hanging issues... but it
> > wasn't hung! I waited about 5-10 minutes and it finally booted. It seems
> > this is a one-time configuration/bug. Subsequent reboots take less than
> > 30 seconds.
> >
> > Just food for thought.
> >
> > Rafael Rivera
> > Extended64 | http://www.extended64.com
> > Blog | http://www.extended64.com/blogs/Rafael
> >