Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Hardware / August 2006

Tip: Looking for answers? Try searching our database.

Stop Message: The ACPI BIOS in this system is not fully ACPI compl

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
kcnal - 14 Aug 2006 03:30 GMT
Ran across this originally in a Windows 2000 Professional installation.  The
Microsoft Article has you pressing the F7 key (if a compliant BIOS is not
currently available) to disable this for setup at the time you would normally
press F6 to load additional storage drivers.  This work fine, except I
actually also need to load a SCSI driver at this point in order to load the
O/S.  Is there a workaround for this?
anon - 14 Aug 2006 04:57 GMT
what about integrating the SCSI driver into a build CD?
this is fairly easy & relatively quick.
kcnal - 14 Aug 2006 05:16 GMT
That's what I was toying with tonight, although I've never tried the SCSI
driver for booting.  I'm going to play with it some, but any tips on where
the driver goes into this (or how)?

> what about integrating the SCSI driver into a build CD?
> this is fairly easy & relatively quick.
anon - 14 Aug 2006 05:33 GMT
edit txtsetup.sif.  There are 4 sections where you'll need
to add the driver.

[SourceDiskFiles] -- make the entry the same as another
driver like cpqarray.sys
[HardwareIdsDatabase]
[SCSI.Load]
[SCSI]

just make them like existing entries but you pull the
contents from your driver's txtsetup.oem file.  Then toss
the .sys into \i386.

you then have create an $OEM$\$1\DRIVERS directory off the
root of your CD and put the driver, its cab & inf files,
etc. in there.

then create a basic winnt.sif file that goes in \i386.

it should have at a minimum this added to the [Unattended]
section of winnt.sif (beyond the mandatory [Data] stuff &
some other:

[Unattended]
OemPnPDriversPath="DRIVERS;"
OemPreinstall=Yes

look at the help for the support deployment tools for info
on this file and a tool for creating a basic one... ignore
the crap about a MassStorageDrivers (or something similar)
directive.  It doesn't work very well, & you may find it
doesn't work at all with some drivers.  I know it won't
with some SATA drivers.  Do it the way i've outlined
above... i've been doing this since 2000 and added
countless drivers.  If Dell or Compaq made it, i've added
their server adapters (along with updating existing ones
by adding the new hardware IDs & replacing the driver).
kcnal - 14 Aug 2006 06:38 GMT
Great, I really appreciate it.  I'll give it a run tomorrow.

> edit txtsetup.sif.  There are 4 sections where you'll need
> to add the driver.
[quoted text clipped - 33 lines]
> their server adapters (along with updating existing ones
> by adding the new hardware IDs & replacing the driver).
paulmd@efn.org - 14 Aug 2006 07:23 GMT
> Ran across this originally in a Windows 2000 Professional installation.  The
> Microsoft Article has you pressing the F7 key (if a compliant BIOS is not
> currently available) to disable this for setup at the time you would normally
> press F6 to load additional storage drivers.  This work fine, except I
> actually also need to load a SCSI driver at this point in order to load the
> O/S.  Is there a workaround for this?

f7, then f6 while there's still time. f7 SILENTLY disables acpi. It
should work.
frodo@theshire.net - 14 Aug 2006 19:26 GMT
the F6 option allows you to select multiple items, one at a time; look
carefully and don't choose "done/continue" 'til you've added each item
that you need from the scrolling list.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.