Copying Bootable Drive C: to Second Hard drive

On 3/11/2014 2:06 PM, philo wrote:
On 03/11/2014 10:15 AM, BillW50 wrote:
On 3/11/2014 9:56 AM, philo wrote:
O.

No matter what OS I used, a serial modem always worked with no problems.

I too had my share of WinModems problems as well back then. Then I
switched over to external RS-232 hard modems and they were solid as a
rock. I suppose my Gateway M465 machines has a WinModem in them.
Although those seem to work okay.

I am sure not all win-modems give poor performance with Win2k/XP

I heard stories some worked well while I also heard many don't worked
well. My experience is like 50/50. And any trouble at all, go external
RS-232 serial. Never tried those external USB ones, but they should be
okay I think.

but I sure ran across many that did.
Back then I ran so many different operating systems,
Windows, OS/2, Solaris. Linux, BSD etc that the external serial modem
was the only way to go.

Oh gosh yes! My memory is WinModems only work with Windows and that is
it. And most of them are flaky under Windows anyway. And if you do get
one working well under Windows, chances are it will only work well under
that version of Windows. Change Windows version and then it probably
won't work well or not at all.

--
Bill
Dell Latitude Slate Tablet 128GB SSD ('12 era) - Thunderbird v24.3.0
Intel Atom Z670 1.5GHz - 2GB RAM - Windows 8 Pro

wrote:
On Tue, 11 Mar 2014 05:25:04 -0400, Paul wrote:

I really think you should record all the AT strings with PortMon.
In my imagination, they would work like this (I have no working
account any more, to test dialup with).

AT_default_strings --- sets up things like hardware flow control
AT_extras --- now, the user has their string, pasted on the end
ATDT4025551212 --- now the number is dialed

OK, so you say you see the default string. Say you were
to craft an AT_extras, like this.

AT
(command that resets the modem)
(rest of string you really wanted to use)

If that command was to execute as an "extra", it would
override the default string that had been already sent.
And that's why a user's "extra" string, would be
sent after the default string. If the "extra" string
is empty, then nothing gets overridden.

The letter "Z" is a way to reset the modem, as in ATZ.
Did out your Hayes command set for the modem...

So you don't necessary have to edit the Registry,
to get a desired result. If you craft a crafty
Extras string, it'll just override the default one.
Because it comes after it, and you can issue a reset
with the letter Z.

AT Z S0=0 E0 V1 Q0 &C1 &D2 X4 --- Paul makes his own Extra.

*******

I have a US Robotics modem. WinXP has a driver for it,
but my modem consists of a modem number and a version
number, and my version number is too old to be compatible
with the driver.

Instead, I had to select a "generic" driver called Unimodem.
And that turned out to work great. Gives me 43K to Freenet.
(I.e. Any connection better than 33.6K means negotiation
of a 56K rate is taking place. The line quality may not be
the best, but at least everything is working.)

So you can have more than one driver available, to use
with a modem. If you have a working driver for your
external, there's probably no reason to go attack it now.

*******

I supposed I'm required to decode your INIT string :-)

http://support.usr.com/support/3453b...lphabetic.html

AT S0=0 E0 V1 Q0 &C1 &D2 X4

S0=0 Turn off AutoAnswer. Won't answer a Fax call.
E0 Turn off character echo
V1 Verbose status messages (English text)
Q0 Display result codes
&C1 Modem uses Carrier Detect signal - assert CD when connected
&D2 Computer must use DTR signal, before attempting transmit
X4 Controls level of detail in result codes.
The X4 value is the Microsoft default amount.

So there is nothing controversial about those commands.
But there could be another AT command sandwiched in there.
And that's what PortMon is for. To find them and list them.

If you happen to mention the model of modem you want
to get working, it's going to be easier to figure out
what the Hayes commands are doing. Some of the commands
on my US Robotics are proprietary. Just a few of them.

Paul

At least I now know what my W98 string is doing.....

My modem is a PCTEL PLATINUM V.92. (Internal).

---OTHER NUMBERS FROM ON THE MODEM ARE---

PCT789T-C1 on main chip

c216p34 on barcode tag

on a sticker:
replace with compaq spare 239887-004
MDM PCI V.90 PLATINUM
5F0214

another# on the circuit board - bp pll e186014

---------

I really prefer external modems, but that one was in the computer, and
like I said, I am tired of swapping my external one between computers.
I must say that in the past, I have had best of luck with USR modems,
but every year at least one modem gets fried by lightning (soemthing
those of us on farms have to cope with because of the long phone lines
ending in only one home). And, yes, I do try to unplug the phone cord
when I am not using the computer, but all it takes is for me to be
downloading something when I drive to town to get a loaf of bread, and a
freak storm comes along, and ZAP! So, I just buy whatever modem is
cheap on ebay these days. On W98, I can prretty much plug in any
external modem, install the drivers and it works right off the bat.
The USR modems seemed slightly faster, but they are always high priced.
I have fried 3 or 4 USR V-Everything modems, and they always seemed to
work the best, but also seemed to fry the easiest.

This external Creative modem was cheap. The power module was made for
some foreign weird plug with 240 volts. But the output from that module
was the same voltage as the modules from some of the dead USR modems, so
I just used that module from the old USR that had fried. I always save
those power modules for other uses, when the modems fry.



(Site uses a pop-under advertisement...)
http://www.modemsite.com/56k/pctel.asp

PCTel was bought by Conexant (former Rockwell, K56 modems etc).
I was hoping I could find an archived web page with drivers.

https://web.archive.org/web/20120708...ssistance.html

But it looks like access to the HSP driver isn't working.

*******

I don't know if I've interpreted what Philo said correctly,
but the PCI soft modems (HSP in this case), they do DSP on
the system processor, and the driver version you use makes
a different. I worked on one, where a later driver made
the thing stable. And in case you were thinking these soft modems
are "crap", the DSP method is so good when using a later
driver, it exceeds the performance of a US Robotics external modem
on the same phone line, by 1%. This may not seem like much,
but I was impressed. I'd always "assumed" the DSP method was
inferior to a controller/datapump. When I saw the results, I
had to repeat the two test cases again, and the answer still
came out to 1%. The test was done late at night, to try to
avoid modem pool usage issues. Naturally, every time you
phone the modem pool, a different port picks up, so at that
end of things, the test conditions are not identical. But
barring a duff port on the pool end, I was finding the DSP
consistent did slightly better.

(Note - this link has some suggestions for tuning a PCTel...
Basically, for turning down the negotiation rate, if it isn't
working too well. These are Hayes AT suggestions.)

http://www.modemhelp.net/newsletter/modem/pctel.shtml

OK, so the next chore, was assuming the PCTEL 789 driver
was already in WinXP SP3. And I found the file, by expanding
all the files in the i386 folder of the CD. I used the command
line version of 7z.exe, copied it to the i386 folder, so
I could expand all the files in one shot. That's to make the
text in the files, search-able.

7z x _*

That would expand all 5689 compressed files ending in an
underscore character. I did that with a copy of i386 on my
RAMDisk. Then, I searched for "7890", which is the DEV of
the PCI modem card. I got a hit in "mdmpctel.inf", so
WinXP does have a built-in driver. (But apparently
you've discovered it isn't very good.) If it isn't working,
then we need to find a better one. This one is for 7892.
This may be marginally later than the built-in WinXP driver,
but the VEN/DEV isn't exactly the same.

ftp://ftp.hp.com/pub/personal_comput...micromodem.exe

These are all the modem chips PCTel made.

134d PCTel Inc
2189 HSP56 MicroModem
2486 2304WT V.92 MDC Modem
7890 HSP MicroModem 56
134d 0001 PCT789 adapter
7891 HSP MicroModem 56
134d 0001 HSP MicroModem 56
7892 HSP MicroModem 56 --- HP driver
7893 HSP MicroModem 56
7894 HSP MicroModem 56
7895 HSP MicroModem 56
7896 HSP MicroModem 56
7897 HSP MicroModem 56

I've been trying to track down, via the Linux PCTel package,
what the differences might be between all those stupid chips.
If I had the PCTel PCI card in front of me, I would be tempted
to hack the INF of the HP download file and change 7892 to 7890
and see if it'll work. PCTel was bought by Conexant, so the odds
of finding a datasheet now are pretty slim.

So I don't have much to offer, to tune the built-in PCI card.
There are lots of Win98 or WinME drivers around. The WInXP
version would offer files like PTSerial.sys, rather than the
..vxd files of older OSes. So while there might appear to be
an overwhelming supply of drivers, they're really not all
that good. The MDMPCTEL.inf file, gives the names of some
789 hardware products, and that's how I zeroed in on the
name of the card that HP uses. Thinking that HP would not
have a toolbar hiding in their download :-)

Paul

On Tue, 11 Mar 2014 09:56:26 -0500, philo* wrote:

On 03/11/2014 08:58 AM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
It really does look like Partition Magic failed but I did think of one
more thing.

On 3/11/2014 8:43 AM, philo wrote:
I already gave you the solution on your previous thread but you
ignored it.

Looks like Casey did follow your advice to me. As Casey didn't use
Partition Magic with the next attempt.




I was (not so clearly) mentioning the problem he is having with dial-up.


Back when I used dial-up I had the same problem with many win-modems in
that under Win2k they could not connect at anywhere near the speed as
they could under Win98.


The sure-fire solution was to use an external serial modem.

No matter what OS I used, a serial modem always worked with no problems.

I *did* connect my ext. (Serial) Creative modem (which I am using right
now on W98), to the XP computer. I physically removed the internal
modem, disabled it in the settings, and installed the drivers for the
ext modem. The results were identical. I also mentioned that on my W98
computer, I have Win2000 installed to dual boot. Using the same
computer (dual booted). same Ext. modem, same phone line, and same ISP.
I have had the exact same problem. I've tried repeatedly during the
last 5 years or so, to connect properly under W2K. It just has not
worked, ever! I finally just gave up on it, and always rebooted to W98
to go online.

I always thought it was just W2K, but it now appears that ALL NT based
OSs cause the same problems. I get a damn good connection in W98,
faster than most dialup systems, most of the time (except during peak
usage hours). Actually, I thought that XP was supposed to be all
plug-n-play and ready to go, and superior to W98 and W2K. Apparently
not.

Yes, this internal modem IS a winmodem, but my Ext. Creative brand is
not. I only switched back to the int. modem because I am tired of
swapping the cable, and I can stay online on the W98 machine, while
trying to find diagnostic articles on the web, to try on the XP machine.
But I've run out of ideas and things to try.

I mentioned in another post, that every year i lose at least one modem
from lightning. I buy another Ext. one, and they are never the same
brand. I just plug them into W98, install the drivers, and I'm
connected. I've never had to manually change settings or anything like
that.

wrote:
On Tue, 11 Mar 2014 09:56:26 -0500, philo wrote:

On 03/11/2014 08:58 AM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
It really does look like Partition Magic failed but I did think of one
more thing.
On 3/11/2014 8:43 AM, philo wrote:
I already gave you the solution on your previous thread but you
ignored it.
Looks like Casey did follow your advice to me. As Casey didn't use
Partition Magic with the next attempt.



I was (not so clearly) mentioning the problem he is having with dial-up.


Back when I used dial-up I had the same problem with many win-modems in
that under Win2k they could not connect at anywhere near the speed as
they could under Win98.


The sure-fire solution was to use an external serial modem.

No matter what OS I used, a serial modem always worked with no problems.

I *did* connect my ext. (Serial) Creative modem (which I am using right
now on W98), to the XP computer. I physically removed the internal
modem, disabled it in the settings, and installed the drivers for the
ext modem. The results were identical. I also mentioned that on my W98
computer, I have Win2000 installed to dual boot. Using the same
computer (dual booted). same Ext. modem, same phone line, and same ISP.
I have had the exact same problem. I've tried repeatedly during the
last 5 years or so, to connect properly under W2K. It just has not
worked, ever! I finally just gave up on it, and always rebooted to W98
to go online.

I always thought it was just W2K, but it now appears that ALL NT based
OSs cause the same problems. I get a damn good connection in W98,
faster than most dialup systems, most of the time (except during peak
usage hours). Actually, I thought that XP was supposed to be all
plug-n-play and ready to go, and superior to W98 and W2K. Apparently
not.

Yes, this internal modem IS a winmodem, but my Ext. Creative brand is
not. I only switched back to the int. modem because I am tired of
swapping the cable, and I can stay online on the W98 machine, while
trying to find diagnostic articles on the web, to try on the XP machine.
But I've run out of ideas and things to try.

I mentioned in another post, that every year i lose at least one modem
from lightning. I buy another Ext. one, and they are never the same
brand. I just plug them into W98, install the drivers, and I'm
connected. I've never had to manually change settings or anything like
that.

Since you know that lightning is eventually going to
kill the PCTell and kill the Creative, why not buy another
external modem and connect it to your WinXP machine ?

And talk to your phone company, about lightning protection.
Maybe they can suggest a device to place at the demarc. (Might
even be old fashioned gas tube or carbon block, plus grounding rod.)
The following is a poor substitute, but just to illustrate another
way of getting MOV protection on a phone line. This would require
three-prong plugs on the house wiring, and grounding of that safety
ground in the wall.

"Telephone surge suppressor"
http://www.amazon.com/Belkin-MasterC.../dp/B0000668YX

These forms of protection, are not for direct hits to a house.
They're to reduce the damage from local hits (more than a couple
hundred feet from the dwelling). No MOV could absorb a direct hit.

I haven't lost any modems here, but if I'm around when a violent
storm is passing, I disconnect at the wall jack.

Paul

On 03/12/2014 12:36 AM, wrote:
On Tue, 11 Mar 2014 09:56:26 -0500, philo wrote:

On 03/11/2014 08:58 AM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
It really does look like Partition Magic failed but I did think of one
more thing.

On 3/11/2014 8:43 AM, philo wrote:
I already gave you the solution on your previous thread but you
ignored it.

Looks like Casey did follow your advice to me. As Casey didn't use
Partition Magic with the next attempt.




I was (not so clearly) mentioning the problem he is having with dial-up.


Back when I used dial-up I had the same problem with many win-modems in
that under Win2k they could not connect at anywhere near the speed as
they could under Win98.


The sure-fire solution was to use an external serial modem.

No matter what OS I used, a serial modem always worked with no problems.

I *did* connect my ext. (Serial) Creative modem (which I am using right
now on W98), to the XP computer. I physically removed the internal
modem, disabled it in the settings, and installed the drivers for the
ext modem.



The only thing I see as odd here is that whenever I've used a serial
modem in Win2k I just let it auto-install using the Windows drivers.
I wonder if possibly, the manufacturers drivers are causing the problem...
but that does seem pretty unlikely.

philo wrote:
On 03/12/2014 12:36 AM, wrote:
On Tue, 11 Mar 2014 09:56:26 -0500, philo wrote:

On 03/11/2014 08:58 AM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
It really does look like Partition Magic failed but I did think of one
more thing.

On 3/11/2014 8:43 AM, philo wrote:
I already gave you the solution on your previous thread but you
ignored it.

Looks like Casey did follow your advice to me. As Casey didn't use
Partition Magic with the next attempt.




I was (not so clearly) mentioning the problem he is having with dial-up.


Back when I used dial-up I had the same problem with many win-modems in
that under Win2k they could not connect at anywhere near the speed as
they could under Win98.


The sure-fire solution was to use an external serial modem.

No matter what OS I used, a serial modem always worked with no problems.

I *did* connect my ext. (Serial) Creative modem (which I am using right
now on W98), to the XP computer. I physically removed the internal
modem, disabled it in the settings, and installed the drivers for the
ext modem.



The only thing I see as odd here is that whenever I've used a serial
modem in Win2k I just let it auto-install using the Windows drivers.
I wonder if possibly, the manufacturers drivers are causing the problem...
but that does seem pretty unlikely.

This may be a long shot, but what about tweaking the modem init string
parameters? I recall doing that at one point when I was using 98SE, to try
and get a better connection speed by it not allowing the modem to connect at
a low kbps (below 28kbps), but rather instead, forcing it to redial (to try
again for a better landline connection (33 kbps, preferably).

In message ,
writes:
[]
I *did* connect my ext. (Serial) Creative modem (which I am using right
now on W98), to the XP computer. I physically removed the internal
modem, disabled it in the settings, and installed the drivers for the

What drivers? An external serial MoDem, unless it's a _very_ weird
model, shouldn't need _any_ drivers.

ext modem. The results were identical. I also mentioned that on my W98
computer, I have Win2000 installed to dual boot. Using the same
computer (dual booted). same Ext. modem, same phone line, and same ISP.
I have had the exact same problem. I've tried repeatedly during the
last 5 years or so, to connect properly under W2K. It just has not
worked, ever! I finally just gave up on it, and always rebooted to W98
to go online.

I always thought it was just W2K, but it now appears that ALL NT based
OSs cause the same problems. I get a damn good connection in W98,
faster than most dialup systems, most of the time (except during peak
usage hours). Actually, I thought that XP was supposed to be all
plug-n-play and ready to go, and superior to W98 and W2K. Apparently
not.

Well, I've seen Vista using dialup OK (with an internal, so probably
software, MoDem).

Yes, this internal modem IS a winmodem, but my Ext. Creative brand is
not. I only switched back to the int. modem because I am tired of
swapping the cable, and I can stay online on the W98 machine, while
trying to find diagnostic articles on the web, to try on the XP machine.
But I've run out of ideas and things to try.

I mentioned in another post, that every year i lose at least one modem
from lightning. I buy another Ext. one, and they are never the same
brand. I just plug them into W98, install the drivers, and I'm

See above re drivers?

connected. I've never had to manually change settings or anything like
that.


--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

age. fac ut gaudeam.