w10 upgrade fail: ACPI bios error

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer. (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

ACPI bios error 0x1900101-0x0017 The installation
failed in the SAFE_OS phase with an error during
Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue. Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again. Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

"T" wrote in message ...

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer. (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

ACPI bios error 0x1900101-0x0017 The installation
failed in the SAFE_OS phase with an error during
Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue. Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again. Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

T.

I'm sure you found plenty of listings for this error and I've had it myself
when upgrading older hardware. Here's what I've done in the past and it's
worked:

1. Update the BIOS

2. Update the graphics card from Intel, NVidia, AMD or wherever to insure an
easier upgrade to Win10 if it has a separate graphics card. If it's on-board
Intel it will be updated during install.

The BIOS and graphics updates will most likely solve the problem but if not,
then step 3.

3. Open Device Manager and open the tree for every entry and right-click
*each and every*entry and select Update Driver and then Search
Automatically. Yes - even do the duplicates.

You will be surprised at the number of driver updates it will find and
install even on a recently Windows Updated system. It's a long process to
click on every item but consider the alternative: Go to each vendors site
and download and install the drivers. If you go that route, install the
chipset drivers first.

The Win10 failure errors are all over the place and most error codes really
don't even get you close when going from Win7/8 to Win10.

Shortcut:
If you want to do a quick compatibility test, remove the existing hard drive
(disconnect any others), slap a spare SSD (or hdd) in as the C: drive,
download and install the Win10 version you want from MS and install it on a
USB stick. Do a fresh, clean install and it will install all of it's own
(generic) drivers initially then after the system is up and running, it will
download vendor specific drivers (from MS servers) as needed. If it doesn't
have a specific older driver and runs the generic Win10 driver, you will
most likely find that it runs very well. Then if it has a graphics card,
you can go to the vendors site and download the full driver set that has
additional features.


--
Bob S

On 2019-12-06 18:27, n/a wrote:
"T"Â* wrote in message ...

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer.Â* (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

Â*Â*Â*Â* ACPI bios error 0x1900101-0x0017 The installation
Â*Â*Â*Â* failed in the SAFE_OS phase with an error during
Â*Â*Â*Â* Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue.Â* Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again.Â* Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

T.

I'm sure you found plenty of listings for this error and I've had it
myself when upgrading older hardware.Â* Here's what I've done in the past
and it's worked:

1. Update the BIOS

2. Update the graphics card from Intel, NVidia, AMD or wherever to
insure an easier upgrade to Win10 if it has a separate graphics card. If
it's on-board Intel it will be updated during install.

The BIOS and graphics updates will most likely solve the problem but if
not, then step 3.

3. Open Device Manager and open the tree for every entry and right-click
*each and every*entry and select Update Driver and then Search
Automatically.Â* Yes - even do the duplicates.

You will be surprised at the number of driver updates it will find and
install even on a recently Windows Updated system.Â* It's a long process
to click on every item but consider the alternative:Â* Go to each vendors
site and download and install the drivers.Â* If you go that route,
install the chipset drivers first.

The Win10 failure errors are all over the place and most error codes
really don't even get you close when going from Win7/8 to Win10.

Shortcut:
If you want to do a quick compatibility test, remove the existing hard
drive (disconnect any others), slap a spare SSD (or hdd) in as the C:
drive, download and install the Win10 version you want from MS and
install it on a USB stick.Â* Do a fresh, clean install and it will
install all of it's own (generic) drivers initially then after the
system is up and running, it will download vendor specific drivers (from
MS servers) as needed.Â* If it doesn't have a specific older driver and
runs the generic Win10 driver, you will most likely find that it runs
very well.Â* Then if it has a graphics card, you can go to the vendors
site and download the full driver set that has additional features.



Hi Bob,

Thank you!

Considering the age of the computer and the cost of labor,
the customer decided to just get a new one, which I concurred
with him over.

This is a great list, which I will keep in case anyone else
decides to upgrade an older computer.

Interesting, I booted him into Fedora 31 off a flash drive
to test his SSD drive. He had me replace his mechanical
drive years ago. Drive was fine. Fedora worked better off
his USB2 port than did Windows 7 off his SSD drive (not all
that unusual). But Fedora has all its drivers in the kernel.

His motherboard was an ASUS P8B-M

https://www.asus.com/us/Commercial-S...pecifications/

which is an Intel C204 Chipset. So it may have just
been a little too weird for W10's upgrade. There
is no explaining ASUS designs at times. Sometimes they
are stellar and sometimes they are crap.

They are on PCI (Payment Card Industry) too, so all
their updates are installed weekly.

And the machine was just old. It was time.

Thank you again for the wonderful tips!

-T

T wrote:
On 2019-12-06 18:27, n/a wrote:
"T" wrote in message ...

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer. (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

ACPI bios error 0x1900101-0x0017 The installation
failed in the SAFE_OS phase with an error during
Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue. Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again. Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

T.

I'm sure you found plenty of listings for this error and I've had it
myself when upgrading older hardware. Here's what I've done in the
past and it's worked:

1. Update the BIOS

2. Update the graphics card from Intel, NVidia, AMD or wherever to
insure an easier upgrade to Win10 if it has a separate graphics card.
If it's on-board Intel it will be updated during install.

The BIOS and graphics updates will most likely solve the problem but
if not, then step 3.

3. Open Device Manager and open the tree for every entry and
right-click *each and every*entry and select Update Driver and then
Search Automatically. Yes - even do the duplicates.

You will be surprised at the number of driver updates it will find and
install even on a recently Windows Updated system. It's a long
process to click on every item but consider the alternative: Go to
each vendors site and download and install the drivers. If you go
that route, install the chipset drivers first.

The Win10 failure errors are all over the place and most error codes
really don't even get you close when going from Win7/8 to Win10.

Shortcut:
If you want to do a quick compatibility test, remove the existing hard
drive (disconnect any others), slap a spare SSD (or hdd) in as the C:
drive, download and install the Win10 version you want from MS and
install it on a USB stick. Do a fresh, clean install and it will
install all of it's own (generic) drivers initially then after the
system is up and running, it will download vendor specific drivers
(from MS servers) as needed. If it doesn't have a specific older
driver and runs the generic Win10 driver, you will most likely find
that it runs very well. Then if it has a graphics card, you can go to
the vendors site and download the full driver set that has additional
features.



Hi Bob,

Thank you!

Considering the age of the computer and the cost of labor,
the customer decided to just get a new one, which I concurred
with him over.

This is a great list, which I will keep in case anyone else
decides to upgrade an older computer.

Interesting, I booted him into Fedora 31 off a flash drive
to test his SSD drive. He had me replace his mechanical
drive years ago. Drive was fine. Fedora worked better off
his USB2 port than did Windows 7 off his SSD drive (not all
that unusual). But Fedora has all its drivers in the kernel.

His motherboard was an ASUS P8B-M

https://www.asus.com/us/Commercial-S...pecifications/


which is an Intel C204 Chipset. So it may have just
been a little too weird for W10's upgrade. There
is no explaining ASUS designs at times. Sometimes they
are stellar and sometimes they are crap.

They are on PCI (Payment Card Industry) too, so all
their updates are installed weekly.

And the machine was just old. It was time.

Thank you again for the wonderful tips!

-T


https://social.technet.microsoft.com...inserver8setup

It's possible that BIOS fixed it. But no confirmation
in the thread at all.

Paul

"T" wrote in message ...

On 2019-12-06 18:27, n/a wrote:
"T" wrote in message ...

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer. (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

ACPI bios error 0x1900101-0x0017 The installation
failed in the SAFE_OS phase with an error during
Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue. Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again. Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

T.

I'm sure you found plenty of listings for this error and I've had it
myself when upgrading older hardware. Here's what I've done in the past
and it's worked:

1. Update the BIOS

2. Update the graphics card from Intel, NVidia, AMD or wherever to insure
an easier upgrade to Win10 if it has a separate graphics card. If it's
on-board Intel it will be updated during install.

The BIOS and graphics updates will most likely solve the problem but if
not, then step 3.

3. Open Device Manager and open the tree for every entry and right-click
*each and every*entry and select Update Driver and then Search
Automatically. Yes - even do the duplicates.

You will be surprised at the number of driver updates it will find and
install even on a recently Windows Updated system. It's a long process
to click on every item but consider the alternative: Go to each vendors
site and download and install the drivers. If you go that route, install
the chipset drivers first.

The Win10 failure errors are all over the place and most error codes
really don't even get you close when going from Win7/8 to Win10.

Shortcut:
If you want to do a quick compatibility test, remove the existing hard
drive (disconnect any others), slap a spare SSD (or hdd) in as the C:
drive, download and install the Win10 version you want from MS and
install it on a USB stick. Do a fresh, clean install and it will install
all of it's own (generic) drivers initially then after the system is up
and running, it will download vendor specific drivers (from MS servers)
as needed. If it doesn't have a specific older driver and runs the
generic Win10 driver, you will most likely find that it runs very well.
Then if it has a graphics card, you can go to the vendors site and
download the full driver set that has additional features.



Hi Bob,

Thank you!

Considering the age of the computer and the cost of labor,
the customer decided to just get a new one, which I concurred
with him over.

This is a great list, which I will keep in case anyone else
decides to upgrade an older computer.

Interesting, I booted him into Fedora 31 off a flash drive
to test his SSD drive. He had me replace his mechanical
drive years ago. Drive was fine. Fedora worked better off
his USB2 port than did Windows 7 off his SSD drive (not all
that unusual). But Fedora has all its drivers in the kernel.

His motherboard was an ASUS P8B-M

https://www.asus.com/us/Commercial-S...pecifications/

which is an Intel C204 Chipset. So it may have just
been a little too weird for W10's upgrade. There
is no explaining ASUS designs at times. Sometimes they
are stellar and sometimes they are crap.

They are on PCI (Payment Card Industry) too, so all
their updates are installed weekly.

And the machine was just old. It was time.

Thank you again for the wonderful tips!

-T


T,

Don't write that motherboard off just yet. That's still a viable (but
older) server board and still fetches $140 on Newegg.

I was thinking that maybe he left the system with you. NewEgg is showing a
Win2019 package with it so it certainly should run Win10.

If you don't want it, I'll pay the shipping... I'm sure I have a Xeon chip
laying around here someplace if it doesn't have one in it. Can always put a
server board to good use. No matter what CPU is in it, it would make a
great pfSense / OpenSense (name your poison) firewall/router since it has
two NICs.

--
Bob S

On 2019-12-09 21:18, n/a wrote:
T,

Don't write that motherboard off just yet.Â* That's still a viable (but
older)Â*serverÂ*boardÂ*andÂ*stillÂ*fetchesÂ*$140Â* onÂ*Newegg.

I was thinking that maybe he left the system with you.Â* NewEgg is
showing a Win2019Â*packageÂ*withÂ*itÂ*soÂ*itÂ*certainlyÂ*sho uldÂ*runÂ*Win10.

If you don't want it, I'll pay the shipping... I'm sure I have a Xeon
chip laying around here someplace if it doesn't have one in it.Â* Can
always put a server board to good use.Â* No matter what CPU is in it, it
would make a great pfSense / OpenSense (name your poison)
firewall/router since it has twoÂ*NICs.

No, he will probably sell it to an employee. It
would run Fedora great. And if wiped, would probably
run Windows 10 too, but that would mean having to
buy a license. Fedora is more tolerant of funky
hardware.

There are certain parts of the current W7 that act weird,
so my guess is that W10's upgrade could ot cope with it/them.

APCI error. Give me a break!

On 2019-12-07 05:24, Paul wrote:
T wrote:
On 2019-12-06 18:27, n/a wrote:
"T"Â* wrote in message ...

Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer.Â* (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

Â*Â*Â*Â* ACPI bios error 0x1900101-0x0017 The installation
Â*Â*Â*Â* failed in the SAFE_OS phase with an error during
Â*Â*Â*Â* Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue.Â* Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again.Â* Same
issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T

T.

I'm sure you found plenty of listings for this error and I've had it
myself when upgrading older hardware.Â* Here's what I've done in the
past and it's worked:

1. Update the BIOS

2. Update the graphics card from Intel, NVidia, AMD or wherever to
insure an easier upgrade to Win10 if it has a separate graphics card.
If it's on-board Intel it will be updated during install.

The BIOS and graphics updates will most likely solve the problem but
if not, then step 3.

3. Open Device Manager and open the tree for every entry and
right-click *each and every*entry and select Update Driver and then
Search Automatically.Â* Yes - even do the duplicates.

You will be surprised at the number of driver updates it will find
and install even on a recently Windows Updated system.Â* It's a long
process to click on every item but consider the alternative:Â* Go to
each vendors site and download and install the drivers.Â* If you go
that route, install the chipset drivers first.

The Win10 failure errors are all over the place and most error codes
really don't even get you close when going from Win7/8 to Win10.

Shortcut:
If you want to do a quick compatibility test, remove the existing
hard drive (disconnect any others), slap a spare SSD (or hdd) in as
the C: drive, download and install the Win10 version you want from MS
and install it on a USB stick.Â* Do a fresh, clean install and it will
install all of it's own (generic) drivers initially then after the
system is up and running, it will download vendor specific drivers
(from MS servers) as needed.Â* If it doesn't have a specific older
driver and runs the generic Win10 driver, you will most likely find
that it runs very well.Â* Then if it has a graphics card, you can go
to the vendors site and download the full driver set that has
additional features.



Hi Bob,

Thank you!

Considering the age of the computer and the cost of labor,
the customer decided to just get a new one, which I concurred
with him over.

This is a great list, which I will keep in case anyone else
decides to upgrade an older computer.

Interesting, I booted him into Fedora 31 off a flash drive
to test his SSD drive.Â* He had me replace his mechanical
drive years ago.Â* Drive was fine.Â* Fedora worked better off
his USB2 port than did Windows 7 off his SSD drive (not all
that unusual). But Fedora has all its drivers in the kernel.

His motherboard was an ASUS P8B-M

https://www.asus.com/us/Commercial-S...pecifications/


which is an Intel C204 Chipset.Â* So it may have just
been a little too weird for W10's upgrade.Â* There
is no explaining ASUS designs at times.Â* Sometimes they
are stellar and sometimes they are crap.

They are on PCI (Payment Card Industry) too, so all
their updates are installed weekly.

And the machine was just old.Â* It was time.

Thank you again for the wonderful tips!

-T


https://social.technet.microsoft.com...inserver8setup


It's possible that BIOS fixed it. But no confirmation
in the thread at all.

Â*Â* Paul

Hi Paul,

Thank you!

I have had bios updates go very, very badly. So
when it comes to upgrading the bios, well lets
say, "Can youy hear the chicken clucking all the
way to Canada?"

-T

T wrote:
On 2019-12-09 21:18, n/a wrote:
T,

Don't write that motherboard off just yet. That's still a viable (but
older) server board and still fetches $140 on Newegg.

I was thinking that maybe he left the system with you. NewEgg is
showing a Win2019 package with it so it certainly should run Win10.

If you don't want it, I'll pay the shipping... I'm sure I have a Xeon
chip laying around here someplace if it doesn't have one in it. Can
always put a server board to good use. No matter what CPU is in it,
it would make a great pfSense / OpenSense (name your poison)
firewall/router since it has two NICs.

No, he will probably sell it to an employee. It
would run Fedora great. And if wiped, would probably
run Windows 10 too, but that would mean having to
buy a license. Fedora is more tolerant of funky
hardware.

There are certain parts of the current W7 that act weird,
so my guess is that W10's upgrade could ot cope with it/them.

APCI error. Give me a break!

It's possible the motherboard maker has acknowledged
the issue, by the issuance of a new BIOS.

The previous BIOS could cause problems for *any* OS
while in that state. You can't just blame a single OS
for this. A malformed ACPI table can give other OSes
indigestion too.

When ACPI first came out, the beta code for it was
pretty creaky, and stuff was failing even though
nominally all the pieces were there. It was rushed
a bit at launch (to take the place of APM). Maybe Win2K
didn't like my first motherboard and its prototype ACPI
stuff.

Learning a bit about Coreboot, might make you
more familiar with whatever language is used
in that stuff. The BIOS not only has tables,
but there is code of a sort in there. I've not
been able to make any sense of that code - it's
more obtuse than LISP. At least LISP makes
a bit of sense.

Paul

On Tue, 10 Dec 2019 00:18:07 -0500, "n/a" wrote:

Don't write that motherboard off just yet. That's still a viable (but
older) server board and still fetches $140 on Newegg.

I was thinking that maybe he left the system with you. NewEgg is showing a
Win2019 package with it so it certainly should run Win10.

If you don't want it, I'll pay the shipping... I'm sure I have a Xeon chip
laying around here someplace if it doesn't have one in it. Can always put a
server board to good use. No matter what CPU is in it, it would make a
great pfSense / OpenSense (name your poison) firewall/router since it has
two NICs.

Just curious, why do you think the presence of two NICs makes it more
suitable as a firewall/router?

On 2019-12-10 09:34, Paul wrote:
T wrote:
On 2019-12-09 21:18, n/a wrote:
T,

Don't write that motherboard off just yet.Â* That's still a viable
(but older) server board and still fetches $140 on Newegg.

I was thinking that maybe he left the system with you.Â* NewEgg is
showing a Win2019 package with it so it certainly should run Win10.

If you don't want it, I'll pay the shipping... I'm sure I have a Xeon
chip laying around here someplace if it doesn't have one in it.Â* Can
always put a server board to good use.Â* No matter what CPU is in it,
it would make a great pfSense / OpenSense (name your poison)
firewall/router since it has two NICs.

No, he will probably sell it to an employee.Â* It
would run Fedora great.Â* And if wiped, would probably
run Windows 10 too, but that would mean having to
buy a license.Â* Fedora is more tolerant of funky
hardware.

There are certain parts of the current W7 that act weird,
so my guess is that W10's upgrade could ot cope with it/them.

APCI error.Â* Give me a break!

It's possible the motherboard maker has acknowledged
the issue, by the issuance of a new BIOS.

The previous BIOS could cause problems for *any* OS
while in that state. You can't just blame a single OS
for this. A malformed ACPI table can give other OSes
indigestion too.

When ACPI first came out, the beta code for it was
pretty creaky, and stuff was failing even though
nominally all the pieces were there. It was rushed
a bit at launch (to take the place of APM). Maybe Win2K
didn't like my first motherboard and its prototype ACPI
stuff.

Learning a bit about Coreboot, might make you
more familiar with whatever language is used
in that stuff. The BIOS not only has tables,
but there is code of a sort in there. I've not
been able to make any sense of that code - it's
more obtuse than LISP. At least LISP makes
a bit of sense.

Â*Â* Paul

Hi Paul,

It got jerked from me, so I can't investigate it further.
But I am tasked with customizing the new computer
they go, so I can still make a living. I just
get a bit obsessive when I get a mystery pulled on
me.

My take so far is that the ACPI error is one of the
legendary M$ Errors where Dog actually means Cat.
Looking up the error code, a lot of folks found
it to be a RAID error and the motherboard does
have RSTe RAID on it, but it is turned off.

-T

On 2019-12-06 16:53, T wrote:
Hi All,

There is nothing I can do about this now as the customer
decided to buy a new computer.Â* (It was a good choice.)

Anyway, I as trying to upgrade a W7-Pro-sp1,x64 to
Windows 10 and got the following:

Â*Â*Â*Â* ACPI bios error 0x1900101-0x0017 The installation
Â*Â*Â*Â* failed in the SAFE_OS phase with an error during
Â*Â*Â*Â* Boot operation

Looking up the error code, it seems like it refers
to an unrecognized RAID controller.

And ACPI is a power controller issue.Â* Hmmmm.

The BIOS was set to Legacy and AHCI.

And google tells me a lot of folks are also getting
this error.

I tried removing all the security software and tried again.Â* Same issue.

On the bright side, W7 still worked afterwards.

Any thoughts on the matter?

-T


Follow up: Had another customer with the same motherboard
and the same problem. This time I talked to ASUS tech
support and they verified that the P8B-M won't operate
with Windows 10

T wrote:
Follow up:Â* Had another customer with the same motherboard
and the same problem. This time I talked to ASUS tech
support and they verified that the P8B-M won't operate
with Windows 10

Another Linux conversion candidate ;-)

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 2019-12-12 06:53, Jonathan N. Little wrote:
T wrote:
Follow up:Â* Had another customer with the same motherboard
and the same problem. This time I talked to ASUS tech
support and they verified that the P8B-M won't operate
with Windows 10

Another Linux conversion candidate ;-)


Unfortunately, no. He is stuck with QuickBooks.
Which goes back to why Linux is not taking over
the Desktop. It is the Common Applications problem,
yet again. It does not matter how crappy the Windows
platform is, if your apps don't run in Linux.

Other than servers, I have found virtually no
small business that can run Linux. And that sucks.

Fedora 31 runs better off a USB flash drive
on that motherboard than does Windows 7 natively.

T wrote:
On 2019-12-12 06:53, Jonathan N. Little wrote:
T wrote:
Follow up:Â* Had another customer with the same motherboard
and the same problem. This time I talked to ASUS tech
support and they verified that the P8B-M won't operate
with Windows 10

Another Linux conversion candidate ;-)


Unfortunately, no.Â* He is stuck with QuickBooks.
Which goes back to why Linux is not taking over
the Desktop.Â* It is the Common Applications problem,
yet again.Â* It does not matter how crappy the Windows
platform is, if your apps don't run in Linux.

Arrgh! The ultimate POS software, their client-server is just garbage.
Have a client that drunk that Kool-Aid and host of constant
issues...Been trying to get her to migrate to an online service that
would be OS agnostic and save both $$ and aggravation.


Other than servers, I have found virtually no
small business that can run Linux.Â* And that sucks.

Converted my public library and and saved $Ks a year...


Fedora 31 runs better off a USB flash drive
on that motherboard than does Windows 7 natively.


And networking works without the Windows BS...


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 2019-12-12 07:30, Jonathan N. Little wrote:
T wrote:
On 2019-12-12 06:53, Jonathan N. Little wrote:
T wrote:
Follow up:Â* Had another customer with the same motherboard
and the same problem. This time I talked to ASUS tech
support and they verified that the P8B-M won't operate
with Windows 10

Another Linux conversion candidate ;-)


Unfortunately, no.Â* He is stuck with QuickBooks.
Which goes back to why Linux is not taking over
the Desktop.Â* It is the Common Applications problem,
yet again.Â* It does not matter how crappy the Windows
platform is, if your apps don't run in Linux.

Arrgh! The ultimate POS software, their client-server is just garbage.
Have a client that drunk that Kool-Aid and host of constant
issues...Been trying to get her to migrate to an online service that
would be OS agnostic and save both $$ and aggravation.


Other than servers, I have found virtually no
small business that can run Linux.Â* And that sucks.

Converted my public library and and saved $Ks a year...


Fedora 31 runs better off a USB flash drive
on that motherboard than does Windows 7 natively.


And networking works without the Windows BS...




Oh ya. Technologocally speaking Linux is superior
and not by a little, but by a lot.

That conversion project you speak of must have
been a blast!

Oh and Quickbooks, what a piece of crap, especially
their server! But EVERYONE gots to have it. There
really is no alternative until Gnu Cash starts
doing payroll and inventory.

I personally use Gnu Cash and love it. But I have
to say, my brain almost melted trying the get
past the initial learning curve.