Windows XP on a netbook "Packard Bell Dot S"?

Happy Oyster

unread,

Oct 23, 2012, 6:52:01 PM10/23/12

to

Hi, all,

Windows XP on a netbook "Packard Bell Dot S"?
=============================================

It is possible to install Win XP. But it turns out that drivers are
missing - leading to no contact with the USB and the network chips.

How are the experiences with these things? I am a bit puzzled.

The bad thing is: Because USB does not work, an external CD-ROM drive
(with service pack 3 CD) cannot be accessed.

Packard Bell Dot S is, so I guess, dated somewhen autumn 2011. What kind
of news chips might be involved?

Merci,

Aribert Deckers
--

http://www.twitter.com/aribertdeckers http://www.Journalist.is
http://www.kindersprechstunde.at http://www.pharmamafia.com
http://www.medulla.at http://www.ariplex.com/folia
http://www.ariplex.com/pixaloid http://www.ariplex.com/lyme/lymeblog

mike

unread,

Oct 24, 2012, 4:11:49 AM10/24/12

to

On 10/23/2012 3:52 PM, Happy Oyster wrote:
> Hi, all,
>
> Windows XP on a netbook "Packard Bell Dot S"?
> =============================================
>
> It is possible to install Win XP. But it turns out that drivers are
> missing - leading to no contact with the USB and the network chips.
>
> How are the experiences with these things? I am a bit puzzled.
>
> The bad thing is: Because USB does not work, an external CD-ROM drive
> (with service pack 3 CD) cannot be accessed.
>
> Packard Bell Dot S is, so I guess, dated somewhen autumn 2011. What kind
> of news chips might be involved?
>
> Merci,
>
> Aribert Deckers

Not at all clear your starting point.
Or how you got there.
Or what tools still exist on the machine.
Is it working now?
What OS?
Do you have ANY working I/O?
Without working I/O, your only choice is to pull the drive
and attach it to another system.

I had a similar situation with win2K. Had to copy the install disk
to the drive, install windows 3.1, put it back and make 3.1 work
well enough to do an in-place update to 2K.
Very messy.
And M$ copy protection makes that more difficult with every new
version.
There are tools to identify the chipset, depending on which OS
you now have and whether it works.

Happy Oyster

unread,

Oct 24, 2012, 8:57:16 PM10/24/12

to

On Wed, 24 Oct 2012 01:11:49 -0700, mike <spa...@gmail.com> wrote:

>On 10/23/2012 3:52 PM, Happy Oyster wrote:
>> Hi, all,
>>
>> Windows XP on a netbook "Packard Bell Dot S"?
>> =============================================
>>
>> It is possible to install Win XP. But it turns out that drivers are
>> missing - leading to no contact with the USB and the network chips.
>>
>> How are the experiences with these things? I am a bit puzzled.
>>
>> The bad thing is: Because USB does not work, an external CD-ROM drive
>> (with service pack 3 CD) cannot be accessed.
>>
>> Packard Bell Dot S is, so I guess, dated somewhen autumn 2011. What kind
>> of news chips might be involved?
>>
>> Merci,
>>
>> Aribert Deckers

>Not at all clear your starting point.

Sarting point: HDD with several partitions.

>Or how you got there.

Used USB-CD-ROM, attached to USB-Port. Booted from BIOS into
USB-attached CD.

>Or what tools still exist on the machine.

Linux in an other partition.

>Is it working now?

I shot it.

>What OS?

It was Windows XP.

Win XP with SP1 was not installable. Reason unknown

Win XP with SP2 was installable, but failed to handle the networking
chips.

>Do you have ANY working I/O?

Machine boots. 1 working Linux is okay. The other went insane.

>Without working I/O, your only choice is to pull the drive
>and attach it to another system.

The question is: ARE THERE DRIVERS? To handle the network chips, drivers
are needed.

>I had a similar situation with win2K. Had to copy the install disk
>to the drive, install windows 3.1, put it back and make 3.1 work
>well enough to do an in-place update to 2K.
>Very messy.

Win 2k I damned stupid.

1. use a working system to boot, partition the HDD

2. format the partition for Win 2K with FAT.

3. Install Win 2K

Win 2K is too stupid to handle a bare HDD. M$ used a boot diskette.

>And M$ copy protection makes that more difficult with every new
>version.

Today I was told that since 3 months ago the installation of Windows XP
is blocked by M$. How much truth is in that information?

>There are tools to identify the chipset, depending on which OS
>you now have and whether it works.

Sure. But that does not give me the drivers.

Another problem which affects SEVERAL Linuxes: shutting down does not
work: netbook does not swith itself off. The power-cable plug has to be
pulled out to shut down the machine.

Whatever they guys at Packard Bell did, they messed up.

mike

unread,

Oct 25, 2012, 7:44:20 AM10/25/12

to

OK, I think I understand.
When I looked up the machine, it said it came with win7?
Not clear why you'd remove win7 and want to put xp on it.
Maybe you deleted the system backup partiton?

Don't know anything about the microsoft xp issue.
I haven't activated xp in a while, but I can't imagine they'd
do that. The backlash would be tremendous. I believe there were
issues because M$ revived XP for small devices to try to block
the proliferation of linux netbooks. That program may have ended??

On a linux machine, there should be some kind of hardware information
utility that discloses the chips. If not,
run lspci to get a list of devices by vendor and device numbers.
driverlookup.com can take those numbers and point you toward drivers.
If that doesn't work, google the device and vendor numbers.

Or you could just google the question you asked.
I assumed that was the first thing you did.
First page of hits has

http://www.driverstools.com/packard-bell-drivers/driver-packard-bell-dot-s-netbook-for-windows-xp-vista-7/
or
http://www.packardbell.co.uk/pb/en/GB/content/download
ot
http://driverscollection.com/?H=dot%20s&By=Packard%20Bell
or
or
or.
Didn't any of those work?

I had a linux machine that wouldn't power off. It would shutdown, but just
hang with the power on.

'sudo poweroff --force'

fixed it.
OS updates seemed to cause the problem to come back, but
issuing the above command fixed it until the next time.

Happy Oyster

unread,

Oct 25, 2012, 1:21:58 PM10/25/12

to

On Thu, 25 Oct 2012 04:44:20 -0700, mike <spa...@gmail.com> wrote:

>When I looked up the machine, it said it came with win7?
>Not clear why you'd remove win7 and want to put xp on it.
>Maybe you deleted the system backup partiton?

No.

I WANT a Windows XP.

Because Windows 7 is utmost shit.

>Don't know anything about the microsoft xp issue.
>I haven't activated xp in a while, but I can't imagine they'd
>do that. The backlash would be tremendous. I believe there were
>issues because M$ revived XP for small devices to try to block
>the proliferation of linux netbooks. That program may have ended??

No matter if they end support (i.e. writing code), the INSTALLATION must
NEVER be blocked.

>On a linux machine, there should be some kind of hardware information
>utility that discloses the chips. If not,
>run lspci to get a list of devices by vendor and device numbers.
>driverlookup.com can take those numbers and point you toward drivers.
>If that doesn't work, google the device and vendor numbers.

I do need the stuff for WINDOWS XP. The chipsets are of no interest.

>Or you could just google the question you asked.
>I assumed that was the first thing you did.

No. Endless gossig in endless forums is useless.

>First page of hits has
>
>http://www.driverstools.com/packard-bell-drivers/driver-packard-bell-dot-s-netbook-for-windows-xp-vista-7/

Is that site reliable???

>or
>http://www.packardbell.co.uk/pb/en/GB/content/download

error 404

>ot
>http://driverscollection.com/?H=dot%20s&By=Packard%20Bell

wrong system: 64 bit

mike

unread,

Oct 25, 2012, 11:20:41 PM10/25/12

to

On 10/25/2012 10:21 AM, Happy Oyster wrote:
> On Thu, 25 Oct 2012 04:44:20 -0700, mike<spa...@gmail.com> wrote:
>
>> When I looked up the machine, it said it came with win7?
>> Not clear why you'd remove win7 and want to put xp on it.
>> Maybe you deleted the system backup partiton?
>
> No.
>
> I WANT a Windows XP.
>
> Because Windows 7 is utmost shit.
>
>
>> Don't know anything about the microsoft xp issue.
>> I haven't activated xp in a while, but I can't imagine they'd
>> do that. The backlash would be tremendous. I believe there were
>> issues because M$ revived XP for small devices to try to block
>> the proliferation of linux netbooks. That program may have ended??
>
> No matter if they end support (i.e. writing code), the INSTALLATION must
> NEVER be blocked.
>
>
>> On a linux machine, there should be some kind of hardware information
>> utility that discloses the chips. If not,
>> run lspci to get a list of devices by vendor and device numbers.
>> driverlookup.com can take those numbers and point you toward drivers.
>> If that doesn't work, google the device and vendor numbers.
>
> I do need the stuff for WINDOWS XP. The chipsets are of no interest.

Chipsets are what the drivers drive. That's a way to locate proper drivers.

>
>
>> Or you could just google the question you asked.
>> I assumed that was the first thing you did.
>
> No. Endless gossig in endless forums is useless.

Trying to help you seems to be just as useless.

>

>> First page of hits has
>>
>> http://www.driverstools.com/packard-bell-drivers/driver-packard-bell-dot-s-netbook-for-windows-xp-vista-7/
>
> Is that site reliable???

Download the drivers, don't download the drivers, I don't GAF!

>
>
>> or
>> http://www.packardbell.co.uk/pb/en/GB/content/download
>
> error 404

works for me

>
>> ot
>> http://driverscollection.com/?H=dot%20s&By=Packard%20Bell
>
> wrong system: 64 bit

site seems to be down now
>
Good luck, I give up.