Strange hanging behavior

Toshiba Satellite P755, Intel core i3-2310M CPU@2.10GHz 64bit
6.0 Gb DDR3 ram, performance rating 5.6. Windows 7 Home Premium SP1.
Complaint was "running slow, almost freezing up".
I booted directly to Safe Mode with Networking. It took longer than I
thought it ought to to load the Safe Mode Help Window. Internet Explorer
came up OK and I downloaded MalwareBytes and was able to install it in
pretty decent time. However it ran up to 31542 files in 51 seconds and
stopped. Right clicking the task bar did nothing but I finally got task
manager to come up using control-alt-delete. It took about a full minute
for it to come up. When it finally did, CPU usage dropped to 0%.
Malwarebytes is still stuck on 51 second. In Task Manager it's taking 0%.
Under Applications it is listed as "not responding". End Now doesn't work
so I go under the processes tab and can't kill it there either.Finally I
get task manager to log me off (but not shut down). So next I am able to
download SAS and get it installed. Double click it and it starts running
in task manager but the windows doean't come up. An hour or so ago when I
was doing this I was finally able to get it up and start running it, but
it went in spurts and then at about 20 minutes it hung and stayed hung.
But Task Manager still says CPU Usage 0%. The hourglass is present in the
task manager window. Oops. Now I just looke over and another window has
covered everything up. Title of Window is Playing Audio. It was the audio
troubleshooter. One or more audio service isn't running. Of course not.
I'm in Safe Mode. It actualy let me get out of that so now the
SuperAntiSpyware window us up and ready to scan. Here goes "Scan Your
Computer" - Quick Scan. Wow it's flying up to 37 Threats Detected. Now
all systems have stopped except the clock. It'll stop off and on too as
it goes along. There's a little green globe that is still whirling aroun
in the upper left hand corner but nothing else is happening.
An hour or two ago I got it shut down and booted up a Hiren's Boot Disk
in it. It acted pretty good at first. I hooked up a portable hard drive
and picked out about 7 Gb of files to copy off onto that drive. It went
like hell for about 32% of it and then just stopped. So correct me if I'm
wrong, but when I'm running Hirens, I'm running a whole different
operating system, so it would appear that whatever is slowing everything
down is NOT anything to do with the operating system, However it is
hardware, like memory or the hard drive, shouldn't I be getting some kind
of errors?.
There's a recovery partition on there, but I'm beginning to wonder if
there's any reason to believe that it'll run any better with a full
recovery.
I think my next step will be to take the hard drive out and see if I can
copy the stuff off of it onto my shop computer. If that goes good, then
I'll know it isn't the hard drive, at least.SuperAntispyware has been
running all this time, and while it isn't frozen it is still at 37
detections and just a few more files scanned. I think it's been in the C:
\WINDOWS\SYSTEM32folder most all the time. Right now it's up to
CMNCLIM.DLL. In a minute or two, that filename will change... probably.

Sorry for the book but it gave me something to do. This is obviously not
the answer so I think I'll take this drive out and see if I can copy his
good stuff off and then go from there, If anyone has any ideas, please
feel free to express them!. The sun will be coming up soon and I need
some shuteye!
--
-- I'm out of white ink --

Menno Hershberger wrote:
> Toshiba Satellite P755, Intel core i3-2310M CPU@2.10GHz 64bit
> 6.0 Gb DDR3 ram, performance rating 5.6. Windows 7 Home Premium SP1.
> Complaint was "running slow, almost freezing up".
> I booted directly to Safe Mode with Networking. It took longer than I
> thought it ought to to load the Safe Mode Help Window. Internet Explorer
> came up OK and I downloaded MalwareBytes and was able to install it in
> pretty decent time. However it ran up to 31542 files in 51 seconds and
> stopped. Right clicking the task bar did nothing but I finally got task
> manager to come up using control-alt-delete. It took about a full minute
> for it to come up. When it finally did, CPU usage dropped to 0%.
> Malwarebytes is still stuck on 51 second. In Task Manager it's taking 0%.
> Under Applications it is listed as "not responding". End Now doesn't work
> so I go under the processes tab and can't kill it there either.Finally I
> get task manager to log me off (but not shut down). So next I am able to
> download SAS and get it installed. Double click it and it starts running
> in task manager but the windows doean't come up. An hour or so ago when I
> was doing this I was finally able to get it up and start running it, but
> it went in spurts and then at about 20 minutes it hung and stayed hung.
> But Task Manager still says CPU Usage 0%. The hourglass is present in the
> task manager window. Oops. Now I just looke over and another window has
> covered everything up. Title of Window is Playing Audio. It was the audio
> troubleshooter. One or more audio service isn't running. Of course not.
> I'm in Safe Mode. It actualy let me get out of that so now the
> SuperAntiSpyware window us up and ready to scan. Here goes "Scan Your
> Computer" - Quick Scan. Wow it's flying up to 37 Threats Detected. Now
> all systems have stopped except the clock. It'll stop off and on too as
> it goes along. There's a little green globe that is still whirling aroun
> in the upper left hand corner but nothing else is happening.
> An hour or two ago I got it shut down and booted up a Hiren's Boot Disk
> in it. It acted pretty good at first. I hooked up a portable hard drive
> and picked out about 7 Gb of files to copy off onto that drive. It went
> like hell for about 32% of it and then just stopped. So correct me if I'm
> wrong, but when I'm running Hirens, I'm running a whole different
> operating system, so it would appear that whatever is slowing everything
> down is NOT anything to do with the operating system, However it is
> hardware, like memory or the hard drive, shouldn't I be getting some kind
> of errors?.
> There's a recovery partition on there, but I'm beginning to wonder if
> there's any reason to believe that it'll run any better with a full
> recovery.
> I think my next step will be to take the hard drive out and see if I can
> copy the stuff off of it onto my shop computer. If that goes good, then
> I'll know it isn't the hard drive, at least.SuperAntispyware has been
> running all this time, and while it isn't frozen it is still at 37
> detections and just a few more files scanned. I think it's been in the C:
> \WINDOWS\SYSTEM32folder most all the time. Right now it's up to
> CMNCLIM.DLL. In a minute or two, that filename will change... probably.
>
> Sorry for the book but it gave me something to do. This is obviously not
> the answer so I think I'll take this drive out and see if I can copy his
> good stuff off and then go from there, If anyone has any ideas, please
> feel free to express them!. The sun will be coming up soon and I need
> some shuteye!

If the sun is coming up, pop in the Kaspersky bootable CD and scan with that.
For your amusement of course, not a cure.

http://support.kaspersky.com/viruses...?qid=208286083 (237MB download)

Since Windows is not running, while that is booted, you get two tests
at the same time. (1) Can it run another (clean) OS ? (2) While doing
so, you get to do a scan for malware.

If that OS doesn't appear to be responsive, then it could be a hardware
problem.

Paul

On Thu, 31 May 2012 03:18:53 -0500, Menno Hershberger wrote:

>Sorry for the book but it gave me something to do. This is obviously not
>the answer so I think I'll take this drive out and see if I can copy his
>good stuff off and then go from there, If anyone has any ideas, please
>feel free to express them!. The sun will be coming up soon and I need
>some shuteye!

If it's the drive you may hear it ticking as it retries. I'd also run
memtest86 from a boot cd. Is there a heath page in the BIOS? Running
that for a while to watch the voltages and see if it hangs might throw
some light on the situation. It does sound more like hardware than
software at the moment.

--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail rpont (at) gmail (dot) com

"Rodney Pont" <> wrote in
news::

> On Thu, 31 May 2012 03:18:53 -0500, Menno Hershberger wrote:
>
>>Sorry for the book but it gave me something to do. This is obviously not
>>the answer so I think I'll take this drive out and see if I can copy his
>>good stuff off and then go from there, If anyone has any ideas, please
>>feel free to express them!. The sun will be coming up soon and I need
>>some shuteye!
>
> If it's the drive you may hear it ticking as it retries. I'd also run
> memtest86 from a boot cd. Is there a heath page in the BIOS? Running
> that for a while to watch the voltages and see if it hangs might throw
> some light on the situation. It does sound more like hardware than
> software at the moment.

It appears that it's the hard drive. I've got it slaved now and I'm having
a hard time getting the documents off of it. There's lots of bad,
uncopyable files.

--
-- I'm out of white ink --

Paul <> wrote in news:jq79ur$7jq$:

> Menno Hershberger wrote:
>> Toshiba Satellite P755, Intel core i3-2310M CPU@2.10GHz 64bit
>> 6.0 Gb DDR3 ram, performance rating 5.6. Windows 7 Home Premium SP1.
>> Complaint was "running slow, almost freezing up".
>> I booted directly to Safe Mode with Networking. It took longer than I
>> thought it ought to to load the Safe Mode Help Window. Internet
>> Explorer came up OK and I downloaded MalwareBytes and was able to
>> install it in pretty decent time. However it ran up to 31542 files in
>> 51 seconds and stopped. Right clicking the task bar did nothing but I
>> finally got task manager to come up using control-alt-delete. It took
>> about a full minute for it to come up. When it finally did, CPU usage
>> dropped to 0%. Malwarebytes is still stuck on 51 second. In Task
>> Manager it's taking 0%. Under Applications it is listed as "not
>> responding". End Now doesn't work so I go under the processes tab and
>> can't kill it there either.Finally I get task manager to log me off
>> (but not shut down). So next I am able to download SAS and get it
>> installed. Double click it and it starts running in task manager but
>> the windows doean't come up. An hour or so ago when I was doing this
>> I was finally able to get it up and start running it, but it went in
>> spurts and then at about 20 minutes it hung and stayed hung. But Task
>> Manager still says CPU Usage 0%. The hourglass is present in the task
>> manager window. Oops. Now I just looke over and another window has
>> covered everything up. Title of Window is Playing Audio. It was the
>> audio troubleshooter. One or more audio service isn't running. Of
>> course not. I'm in Safe Mode. It actualy let me get out of that so
>> now the SuperAntiSpyware window us up and ready to scan. Here goes
>> "Scan Your Computer" - Quick Scan. Wow it's flying up to 37 Threats
>> Detected. Now all systems have stopped except the clock. It'll stop
>> off and on too as it goes along. There's a little green globe that is
>> still whirling aroun in the upper left hand corner but nothing else
>> is happening. An hour or two ago I got it shut down and booted up a
>> Hiren's Boot Disk in it. It acted pretty good at first. I hooked up a
>> portable hard drive and picked out about 7 Gb of files to copy off
>> onto that drive. It went like hell for about 32% of it and then just
>> stopped. So correct me if I'm wrong, but when I'm running Hirens, I'm
>> running a whole different operating system, so it would appear that
>> whatever is slowing everything down is NOT anything to do with the
>> operating system, However it is hardware, like memory or the hard
>> drive, shouldn't I be getting some kind of errors?.
>> There's a recovery partition on there, but I'm beginning to wonder if
>> there's any reason to believe that it'll run any better with a full
>> recovery.
>> I think my next step will be to take the hard drive out and see if I
>> can copy the stuff off of it onto my shop computer. If that goes
>> good, then I'll know it isn't the hard drive, at
>> least.SuperAntispyware has been running all this time, and while it
>> isn't frozen it is still at 37 detections and just a few more files
>> scanned. I think it's been in the C: \WINDOWS\SYSTEM32folder most all
>> the time. Right now it's up to CMNCLIM.DLL. In a minute or two, that
>> filename will change... probably.
>>
>> Sorry for the book but it gave me something to do. This is obviously
>> not the answer so I think I'll take this drive out and see if I can
>> copy his good stuff off and then go from there, If anyone has any
>> ideas, please feel free to express them!. The sun will be coming up
>> soon and I need some shuteye!
>
> If the sun is coming up, pop in the Kaspersky bootable CD and scan
> with that. For your amusement of course, not a cure.
>
> http://support.kaspersky.com/viruses...?qid=208286083
> (237MB download)
>
> Since Windows is not running, while that is booted, you get two tests
> at the same time. (1) Can it run another (clean) OS ? (2) While doing
> so, you get to do a scan for malware.
>
> If that OS doesn't appear to be responsive, then it could be a
> hardware problem.

It appears that it's the hard drive. I've got it slaved now and I'm
having a hard time getting the documents off of it. There's lots of bad,
uncopyable files.

I've got new drives but now I'm going to have to order a recovery CD.

--
-- I'm out of white ink --

Menno Hershberger wrote:
> "Rodney Pont" <> wrote in
> news::
>
>> On Thu, 31 May 2012 03:18:53 -0500, Menno Hershberger wrote:
>>
>>> Sorry for the book but it gave me something to do. This is obviously not
>>> the answer so I think I'll take this drive out and see if I can copy his
>>> good stuff off and then go from there, If anyone has any ideas, please
>>> feel free to express them!. The sun will be coming up soon and I need
>>> some shuteye!
>> If it's the drive you may hear it ticking as it retries. I'd also run
>> memtest86 from a boot cd. Is there a heath page in the BIOS? Running
>> that for a while to watch the voltages and see if it hangs might throw
>> some light on the situation. It does sound more like hardware than
>> software at the moment.
>
> It appears that it's the hard drive. I've got it slaved now and I'm having
> a hard time getting the documents off of it. There's lots of bad,
> uncopyable files.
>

This is a possible method, to copy the drive. The purpose of doing this,
is so you get as many good sectors off the old drive as possible. Then,
using the *copy* of the drive, you can run CHKDSK, a file scavenger or whatever.

http://www.cgsecurity.org/wiki/Damaged_Hard_Disk

The best method: Antonio Diaz's GNU 'ddrescue'

The best solution - both faster and more efficient - seems
to be Antonio Diaz's 'ddrescue' (ddrescue)

# download ddrescue
wget http://download.savannah.gnu.org/rel...ue-1.8.tar.bz2
# extract the source code
tar xjf ddrescue-1.8.tar.bz2
# compile ddrescue
cd ddrescue-1.8
./configure && make

# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log

You could do that whole process from a Linux LiveCD. Seeing as
Ubuntu sucks now, you could try Linux Mint or something. Any
distro with working GUI would be a candidate.

The "rescued.log" file is presumably tracking how many sectors
got copied or didn't get copied. Sectors not providing data
would likely get replaced by a sector of all zeros.
But you could tell for sure, by reviewing the source of ddrescue.

The syntax "/dev/old_disk" and "/dev/new_disk" are place holders
for experienced Linux users. Real Linux disks show up as
/dev/hda, /dev/hdb, ... or as /dev/sda, /dev/sdb and so on.
You can use "ls /dev" command to list the contents of the
dev tree, and get some idea what hd* and sd* entries exist.
hda1 is the first partition of hda. Whereas hda alone is the
"whole raw drive". So an actual command to ddrescue would likely
look like this. And the "rescued.log" will likely end up in
the current working directory.

../ddrescue -n /dev/sda /dev/sdb rescued.log

HTH,
Paul

Paul <> wrote in news:jq8eqq$3ii$:

> Menno Hershberger wrote:
>> "Rodney Pont" <> wrote in
>> news::
>>
>>> On Thu, 31 May 2012 03:18:53 -0500, Menno Hershberger wrote:
>>>
>>>> Sorry for the book but it gave me something to do. This is
>>>> obviously not the answer so I think I'll take this drive out and
>>>> see if I can copy his good stuff off and then go from there, If
>>>> anyone has any ideas, please feel free to express them!. The sun
>>>> will be coming up soon and I need some shuteye!
>>> If it's the drive you may hear it ticking as it retries. I'd also
>>> run memtest86 from a boot cd. Is there a heath page in the BIOS?
>>> Running that for a while to watch the voltages and see if it hangs
>>> might throw some light on the situation. It does sound more like
>>> hardware than software at the moment.
>>
>> It appears that it's the hard drive. I've got it slaved now and I'm
>> having a hard time getting the documents off of it. There's lots of
>> bad, uncopyable files.
>>
>
> This is a possible method, to copy the drive. The purpose of doing
> this, is so you get as many good sectors off the old drive as
> possible. Then, using the *copy* of the drive, you can run CHKDSK, a
> file scavenger or whatever.
>
> http://www.cgsecurity.org/wiki/Damaged_Hard_Disk
>
> The best method: Antonio Diaz's GNU 'ddrescue'
>
> The best solution - both faster and more efficient - seems
> to be Antonio Diaz's 'ddrescue' (ddrescue)
>
> # download ddrescue
> wget
> http://download.savannah.gnu.org/rel...rescue-1.8.tar
> .bz2 # extract the source code
> tar xjf ddrescue-1.8.tar.bz2
> # compile ddrescue
> cd ddrescue-1.8
> ./configure && make
>
> # first, grab most of the error-free areas in a hurry:
> ./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
> # then try to recover as much of the dicy areas as possible:
> ./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log
>
> You could do that whole process from a Linux LiveCD. Seeing as
> Ubuntu sucks now, you could try Linux Mint or something. Any
> distro with working GUI would be a candidate.
>
> The "rescued.log" file is presumably tracking how many sectors
> got copied or didn't get copied. Sectors not providing data
> would likely get replaced by a sector of all zeros.
> But you could tell for sure, by reviewing the source of ddrescue.
>
> The syntax "/dev/old_disk" and "/dev/new_disk" are place holders
> for experienced Linux users. Real Linux disks show up as
> /dev/hda, /dev/hdb, ... or as /dev/sda, /dev/sdb and so on.
> You can use "ls /dev" command to list the contents of the
> dev tree, and get some idea what hd* and sd* entries exist.
> hda1 is the first partition of hda. Whereas hda alone is the
> "whole raw drive". So an actual command to ddrescue would likely
> look like this. And the "rescued.log" will likely end up in
> the current working directory.

The owner is happy with what I was able to retrieve.
So I have put in a new drive and installed a retail copy of Windows 7. I
was able to get *most* of the drivers from the Toshiba site. The proper
driver seems to be listed. It's one of those compressed files that
extracts and the runs. The problem is that is just extracts and *doesn't*
run.
Screenshot at http://mewnlite.com/screen.gif shows the device listed as
"Other device"
Note above I showed another wireless device that DID install OK and
wireless does work OK.
The exact model is a Toshiba Sattelite P755-S5215.
I found what looks like the right driver at
http://www.csd.toshiba.com/cgi-bin/t...elContent.jsp?
ct=DL&os=&category=&moid=3025542&rpn=PSAY1U&modelFilter=&selCategory=
2756709&selFamily=1073768663
or http://tinyurl.com/c6xovgt (if you trust me).
On that page you have to select "driver" where it says "all catagories".
The one I downloaded is Intel PROSet/Wireless WiMAX Software(v6.5.0.64;
07-14-2011; 10.49M) It downloads tc10112100a.exe which is the one that
extracts and then does nothing.
I'm not exactly sure what that device is good for unless it just adds
wireless-N capability to the one that's already there.
I've Googled and got a few hits but I didn't find any solutions. And of
course if you scroll down too far you start running into those "driver
detective" type scams.

Everything I am doing on this new installation is humming right along so
it was definitely the hard drive that was the culprit.

I will keep searching for an answer to that driver thing but I'll check
back here often. Oftentimes Paul and others of you have Google beat all
to hell!

For which I thank you all!

--
-- I'm out of white ink --

Menno Hershberger wrote:

> The owner is happy with what I was able to retrieve.
> So I have put in a new drive and installed a retail copy of Windows 7. I
> was able to get *most* of the drivers from the Toshiba site. The proper
> driver seems to be listed. It's one of those compressed files that
> extracts and the runs. The problem is that is just extracts and *doesn't*
> run.
> Screenshot at http://mewnlite.com/screen.gif shows the device listed as
> "Other device"
> Note above I showed another wireless device that DID install OK and
> wireless does work OK.
> The exact model is a Toshiba Sattelite P755-S5215.
> I found what looks like the right driver at
> http://www.csd.toshiba.com/cgi-bin/t...elContent.jsp?
> ct=DL&os=&category=&moid=3025542&rpn=PSAY1U&modelFilter=&selCategory=
> 2756709&selFamily=1073768663
> or http://tinyurl.com/c6xovgt (if you trust me).
> On that page you have to select "driver" where it says "all catagories".
> The one I downloaded is Intel PROSet/Wireless WiMAX Software(v6.5.0.64;
> 07-14-2011; 10.49M) It downloads tc10112100a.exe which is the one that
> extracts and then does nothing.
> I'm not exactly sure what that device is good for unless it just adds
> wireless-N capability to the one that's already there.
> I've Googled and got a few hits but I didn't find any solutions. And of
> course if you scroll down too far you start running into those "driver
> detective" type scams.
>
> Everything I am doing on this new installation is humming right along so
> it was definitely the hard drive that was the culprit.
>
> I will keep searching for an answer to that driver thing but I'll check
> back here often. Oftentimes Paul and others of you have Google beat all
> to hell!
>
> For which I thank you all!
>

I had a look at this file. I used 7ZIP to look through the archive inside it.

tc10112100a.exe

It has a "setup.exe" file. You could try clicking that one.

There is a "bpusb.inf" file. This suggests the MAC (main chip)
on the card, interfaces via USB2. And that could define an
upper limit for transfer rate.

; Intel Baxter Peak USB Device
;
; Copyright (c) 2007 Intel Corporation All Rights Reserved.

[Intel.NTAMD64]
%bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0183
%bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0186
%bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0187
%bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0188
%bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D6
%bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D7
%bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D9

And those devices aren't listed here. The closest entry
is "0182 WiMAX Connection 2400m". So they're too new for
the unofficial listing.

http://www.linux-usb.org/usb.ids

On an information page, Intel claims there are limited providers, for
which that WiMax would work. So even if you get the driver installed,
there might be nothing to test it with.

http://www.intel.com/support/wireles...S-033046.htm#3

http://en.wikipedia.org/wiki/Wimax

If you still can't get the Toshiba stuff to install, you
can go to Intel and get a driver from there.

http://downloadcenter.intel.com/Sear...6150+Series%22

Paul

Paul <> wrote in news:jq996m$q8s$:

> Menno Hershberger wrote:
>
>> The owner is happy with what I was able to retrieve.
>> So I have put in a new drive and installed a retail copy of Windows
>> 7. I was able to get *most* of the drivers from the Toshiba site. The
>> proper driver seems to be listed. It's one of those compressed files
>> that extracts and the runs. The problem is that is just extracts and
>> *doesn't* run.
>> Screenshot at http://mewnlite.com/screen.gif shows the device listed
>> as "Other device"
>> Note above I showed another wireless device that DID install OK and
>> wireless does work OK.
>> The exact model is a Toshiba Sattelite P755-S5215.
>> I found what looks like the right driver at
>> http://www.csd.toshiba.com/cgi-bin/t...elContent.jsp?
>> ct=DL&os=&category=&moid=3025542&rpn=PSAY1U&modelFilter=&selCategory=
>> 2756709&selFamily=1073768663
>> or http://tinyurl.com/c6xovgt (if you trust me).
>> On that page you have to select "driver" where it says "all
>> catagories". The one I downloaded is Intel PROSet/Wireless WiMAX
>> Software(v6.5.0.64; 07-14-2011; 10.49M) It downloads tc10112100a.exe
>> which is the one that extracts and then does nothing.
>> I'm not exactly sure what that device is good for unless it just adds
>> wireless-N capability to the one that's already there.
>> I've Googled and got a few hits but I didn't find any solutions. And
>> of course if you scroll down too far you start running into those
>> "driver detective" type scams.
>>
>> Everything I am doing on this new installation is humming right along
>> so it was definitely the hard drive that was the culprit.
>>
>> I will keep searching for an answer to that driver thing but I'll
>> check back here often. Oftentimes Paul and others of you have Google
>> beat all to hell!
>>
>> For which I thank you all!
>>
>
> I had a look at this file. I used 7ZIP to look through the archive
> inside it.
>
> tc10112100a.exe
>
> It has a "setup.exe" file. You could try clicking that one.


If I can find the temporary folder it got extracted to!


>
> There is a "bpusb.inf" file. This suggests the MAC (main chip)
> on the card, interfaces via USB2. And that could define an
> upper limit for transfer rate.
>
> ; Intel Baxter Peak USB Device
> ;
> ; Copyright (c) 2007 Intel Corporation All Rights Reserved.
>
> [Intel.NTAMD64]
> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0183
> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0186
> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0187
> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0188
> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D6
> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D7
> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D9
>
> And those devices aren't listed here. The closest entry
> is "0182 WiMAX Connection 2400m". So they're too new for
> the unofficial listing.
>
> http://www.linux-usb.org/usb.ids
>
> On an information page, Intel claims there are limited providers, for
> which that WiMax would work. So even if you get the driver installed,
> there might be nothing to test it with.
>
> http://www.intel.com/support/wireles...S-033046.htm#3
>
> http://en.wikipedia.org/wiki/Wimax
>
> If you still can't get the Toshiba stuff to install, you
> can go to Intel and get a driver from there.
>
> http://downloadcenter.intel.com/Sear...g&keyword=%22I
> ntel+Centrino+Wireless-N+%2b+WiMAX+6150+Series%22

On that page I see
"9 results matching:
"Intel Centrino Wireless-N + WiMAX 6150 Series" + Windows 7 (64-bit)* +
Software Applications sorted by relevance

But in all 9 of them I don't see the word "Centrino" or "WiMax"
What am I missing here?

--
-- I'm out of white ink --

Menno Hershberger wrote:
> Paul <> wrote in news:jq996m$q8s$:
>
>> Menno Hershberger wrote:
>>
>>> The owner is happy with what I was able to retrieve.
>>> So I have put in a new drive and installed a retail copy of Windows
>>> 7. I was able to get *most* of the drivers from the Toshiba site. The
>>> proper driver seems to be listed. It's one of those compressed files
>>> that extracts and the runs. The problem is that is just extracts and
>>> *doesn't* run.
>>> Screenshot at http://mewnlite.com/screen.gif shows the device listed
>>> as "Other device"
>>> Note above I showed another wireless device that DID install OK and
>>> wireless does work OK.
>>> The exact model is a Toshiba Sattelite P755-S5215.
>>> I found what looks like the right driver at
>>> http://www.csd.toshiba.com/cgi-bin/t...elContent.jsp?
>>> ct=DL&os=&category=&moid=3025542&rpn=PSAY1U&modelFilter=&selCategory=
>>> 2756709&selFamily=1073768663
>>> or http://tinyurl.com/c6xovgt (if you trust me).
>>> On that page you have to select "driver" where it says "all
>>> catagories". The one I downloaded is Intel PROSet/Wireless WiMAX
>>> Software(v6.5.0.64; 07-14-2011; 10.49M) It downloads tc10112100a.exe
>>> which is the one that extracts and then does nothing.
>>> I'm not exactly sure what that device is good for unless it just adds
>>> wireless-N capability to the one that's already there.
>>> I've Googled and got a few hits but I didn't find any solutions. And
>>> of course if you scroll down too far you start running into those
>>> "driver detective" type scams.
>>>
>>> Everything I am doing on this new installation is humming right along
>>> so it was definitely the hard drive that was the culprit.
>>>
>>> I will keep searching for an answer to that driver thing but I'll
>>> check back here often. Oftentimes Paul and others of you have Google
>>> beat all to hell!
>>>
>>> For which I thank you all!
>>>
>> I had a look at this file. I used 7ZIP to look through the archive
>> inside it.
>>
>> tc10112100a.exe
>>
>> It has a "setup.exe" file. You could try clicking that one.
>
>
> If I can find the temporary folder it got extracted to!
>
>
>> There is a "bpusb.inf" file. This suggests the MAC (main chip)
>> on the card, interfaces via USB2. And that could define an
>> upper limit for transfer rate.
>>
>> ; Intel Baxter Peak USB Device
>> ;
>> ; Copyright (c) 2007 Intel Corporation All Rights Reserved.
>>
>> [Intel.NTAMD64]
>> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0183
>> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0186
>> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0187
>> %bpusb.KP2DeviceDesc% = bpusb, USB\VID_8086&PID_0188
>> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D6
>> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D7
>> %bpusb.KSPDeviceDesc% = bpusb, USB\VID_8087&PID_07D9
>>
>> And those devices aren't listed here. The closest entry
>> is "0182 WiMAX Connection 2400m". So they're too new for
>> the unofficial listing.
>>
>> http://www.linux-usb.org/usb.ids
>>
>> On an information page, Intel claims there are limited providers, for
>> which that WiMax would work. So even if you get the driver installed,
>> there might be nothing to test it with.
>>
>> http://www.intel.com/support/wireles...S-033046.htm#3
>>
>> http://en.wikipedia.org/wiki/Wimax
>>
>> If you still can't get the Toshiba stuff to install, you
>> can go to Intel and get a driver from there.
>>
>> http://downloadcenter.intel.com/Sear...g&keyword=%22I
>> ntel+Centrino+Wireless-N+%2b+WiMAX+6150+Series%22
>
> On that page I see
> "9 results matching:
> "Intel Centrino Wireless-N + WiMAX 6150 Series" + Windows 7 (64-bit)* +
> Software Applications sorted by relevance
>
> But in all 9 of them I don't see the word "Centrino" or "WiMax"
> What am I missing here?
>

Do you know how to use 7ZIP ?

http://en.wikipedia.org/wiki/7zip

http://www.7-zip.org/

When 7ZIP is installed, you get another context menu entry item.
You can right click on tc10112100a.exe and extract the contents.
For safety, you can make a new folder in your download area,
drop tc10112100a.exe into it, right-click on it, and open with 7ZIP.
Just clicking the "Extract" button without doing anything else, should
extract everything in the .exe.

Not all compressed archives work that way. There are plenty of
compression formats which aren't contained in 7ZIP. There are
twenty to thirty compression formats just for executable files
for example. And 7ZIP doesn't know any of them. (The more unscrupulous
the company making the executable, the more obscure the compression
format. They pretend it's to save on download bytes, when in fact
it's to prevent people like me from seeing what they're doing...)

But if you're ever in a situation where you can't find the
folder created by a decompressing .exe, then 7ZIP is a tool
to try.

As for a location to check, you can try %temp% . Type that
into a file explorer window, and it will be expanded to a
Windows path. Sometimes, naive installers open there. But
you'll find there are absolutely crazy choices for some
installers (even Microsoft does stuff like that). Like the
jumble_of_numbers folder on your data partition from a
..NET install. Or the folder choice used by the MicrosoftStore
DVD application. Some companies create their own folder, like
C:\Dell and put folders in there. I have a "Dell" and an "intel"
on my C: drive. There are as many bad habits, as there are companies.

Paul