Thread View: comp.os.os2.setup.misc
22 messages
22 total messages
Started by idiotxxx
Sun, 27 Jul 1997 00:00
Plug and Pray problems in Warp 4
Author: idiotxxx
Date: Sun, 27 Jul 1997 00:00
Date: Sun, 27 Jul 1997 00:00
27 lines
1688 bytes
1688 bytes
I have a problem with a SoundBlaster 16 Plug & Pray.
I am unable to use it on my OS2 Warp 4 system. I have an ethernet
adaptor (NE2000 clone) which has software programmable IRQ etc and
when my system boots up, as soon as the network drivers search for the
card I get a trap as below.
=======
07-27-1997 15:30:00 SYS3175 PID 0001 TID 0006 Slot 0006
sysinit
=======
I am using an old 8bit card with jumpers that let me set the IRQ etc but I'd love
to be able to use my 16 bit card.
If I take eitehr the network card or the SB16 card out of the machine the other
will work correctly.
Has anyone else overcome this problem ?
Specific system info can be provided if required.
Any suggestions ??
Nev..
*** anti-spam email address ***
*** remove the "xxx" from reply-to address before replying ***
Re: Plug and Pray problems in Warp 4
Author: Sam Detweiler
Date: Sun, 27 Jul 1997 00:00
Date: Sun, 27 Jul 1997 00:00
59 lines
2551 bytes
2551 bytes
If you know what the NE2000 port/IRQ are, then add basedev=reserve.sys /P:port,32 /IRQ:?? to the config.sys then reboot, Alt-F1 at the white blob, and select Enable Hardware Detection.. this 'MAY' force the SB to be configured at some other address than it was during install, so if the SB driver fails to load, then rmview /dc >somefile from the commandline after boot, figure out where the SB was configured and chage the parms to the SB driver in config.sys Warp 4 PnP configurator author.. (the NE2000 SHOULD have been detected by the DETNE2.SNP during install, but we have seem some that go undetected for some reason..) idiotxxx@mindless.com wrote: > I have a problem with a SoundBlaster 16 Plug & Pray. > > I am unable to use it on my OS2 Warp 4 system. I have an ethernet > adaptor (NE2000 clone) which has software programmable IRQ etc and > when my system boots up, as soon as the network drivers search for the > card I get a trap as below. > ======= > 07-27-1997 15:30:00 SYS3175 PID 0001 TID 0006 Slot 0006 > sysinit > ======= > > I am using an old 8bit card with jumpers that let me set the IRQ etc but I'd > love > to be able to use my 16 bit card. > If I take eitehr the network card or the SB16 card out of the machine the > other > will work correctly. > > Has anyone else overcome this problem ? > > Specific system info can be provided if required. > > Any suggestions ?? > > Nev.. > > *** anti-spam email address *** > *** remove the "xxx" from reply-to address before replying *** -- Sam Detweiler OS/2 Device Driver Development OS/2 Advisor IBM
Re: Plug and Pray problems in Warp 4
Author: Ken Hildabolt
Date: Sun, 27 Jul 1997 00:00
Date: Sun, 27 Jul 1997 00:00
23 lines
1600 bytes
1600 bytes
In <c1.01.2GzH8q$03A@warped.connexus.apana.org.au>, on 07/27/97 at 05:51 AM, idiotxxx@mindless.com said: If nothing else works, the /p parm on the device driver will. Here is the statement for my awe32 pnp: DEVICE=D:\MMOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /M:330 /N:SBAUD1$ /P /G DEVICE=D:\MMOS2\AUDIOVDD.SYS SBAUD1$ }Has anyone else overcome this problem ? }Specific system info can be provided if required. }Any suggestions ?? }Nev.. ----------------------------------------------------------- "Ken Hildabolt" <hildajk1@aplcomm.jhuapl.edu> Applied Physics Laboratory / The Johns Hopkins University -----------------------------------------------------------
Re: Plug and Pray problems in Warp 4
Author: Simon South
Date: Tue, 29 Jul 1997 00:00
Date: Tue, 29 Jul 1997 00:00
26 lines
2093 bytes
2093 bytes
In article <c1.01.2GzH8q$03A@warped.connexus.apana.org.au>, <idiotxxx@mindless.com> wrote: >I have a problem with a SoundBlaster 16 Plug & Pray. >Any suggestions ?? Not sure if this will help, but if you can determine exactly what the conflict is -- i.e., narrow it down to a specific IRQ or DMA channel that's overlapping -- you might be able to get around the problem by forcing the Sound Blaster drivers to use a particular configuration for the soundcard. Appending "/O" to the line in your CONFIG.SYS which loads the SB16 driver will make it use the settings you specify -- DMA channel and IRQ number, for instance. I can't remember just what the format is for these parameters, but they should be listed in the documentation that came with driver. This way you can force the Sound Blaster to use an IRQ/DMA combination that won't conflict with the network card. Good luck! -- Simon South CS Undergraduate, University of Waterloo E-mail: ssouth@orc.ca Web page: http://www.orc.ca/~ssouth Coming Soon: Blue Notes, the Alternative OS/2 MIDI Sequencer Visit http://www.orc.ca/~ssouth/BlueNotes.html for more info
Re: Plug and Pray problems in Warp 4
Author: msinger
Date: Fri, 01 Aug 1997 00:00
Date: Fri, 01 Aug 1997 00:00
38 lines
2212 bytes
2212 bytes
In <c1.01.2GzH8q$03A@warped.connexus.apana.org.au>, on 07/27/97 at 05:51 AM, idiotxxx@mindless.com said: >I have a problem with a SoundBlaster 16 Plug & Pray. >I am unable to use it on my OS2 Warp 4 system. I have an ethernet >adaptor (NE2000 clone) which has software programmable IRQ etc and when >my system boots up, as soon as the network drivers search for the card I >get a trap as below. >======= >07-27-1997 15:30:00 SYS3175 PID 0001 TID 0006 Slot 0006 sysinit >======= >I am using an old 8bit card with jumpers that let me set the IRQ etc but >I'd love to be able to use my 16 bit card. >If I take eitehr the network card or the SB16 card out of the machine the >other will work correctly. >Has anyone else overcome this problem ? >Specific system info can be provided if required. >Any suggestions ?? >Nev.. > *** anti-spam email address *** > *** remove the "xxx" from reply-to address before replying *** -- ----------------------------------------------------------- msinger@toward.com ----------------------------------------------------------- Try turning the plug n play off in your ne 2000 card. Manually set IRQ to 15 and Address to 300. Then allow sound card to search for open IRQ and ADDRESS. Watchout sometimes CD-ROM likes Address 300. Good luck Jeffrey
Re: Plug and Pray problems in Warp 4
Author: Trev Peterson
Date: Mon, 29 Sep 1997 00:00
Date: Mon, 29 Sep 1997 00:00
12 lines
1407 bytes
1407 bytes
I am having problems with a Boca Office Communicator FDV34SVD PNP fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I checked this using Win95 to verify that it worked there and it did. I can't lock the config on the modem and don't want to reconfig the mouse port (don't want to impact Linux, etc). Checking IBM's database of incidents didn't find anything. Any suggestions? Trev Please respond via email
Re: Plug and Pray problems in Warp 4
Author: Stan Koper
Date: Tue, 21 Oct 1997 00:00
Date: Tue, 21 Oct 1997 00:00
24 lines
2009 bytes
2009 bytes
I just picked up an internal Philips k56flex modem. I have a dual boot system, Win95 and OS/2 4.0. The modem set up under Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and they don't recognize the modem *unless* I stop the boot at the white square and select full hardware detection. When it does work under OS/2 it's still com3 (since the motherboard has two serial ports), but the Irq is 7. I haven't tried it under WinOS/2. What I'd like to know is, is it possible to establish full hardware detection *without* interrupting boot up? Is there some line I can add to config.sys or is there some other process (like selective install) that I can use to get the modem recognized by OS/2? In article <342F3E86.4012@focus.winternet.com>, Trev Peterson <tpeterso@focus.winternet.com> wrote: >I am having problems with a Boca Office Communicator FDV34SVD PNP >fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I >checked this using Win95 to verify that it worked there and it did. >
Re: Plug and Pray problems in Warp 4
Author: Sam_Detweiler
Date: Tue, 21 Oct 1997 00:00
Date: Tue, 21 Oct 1997 00:00
59 lines
2978 bytes
2978 bytes
Well, Assuming this is a decent PnP device, and you've run hardware detection after its installation, then rmview /dc from the commandline SHOULD show you where the modem was configured. It should NOT be needed to redo detection on EACH boot however (if this is a good PnP device) as we (my code) will reconfigure it to the SAME place as last time detection was run.. Now.. I have a tweak to the ISAPNP configurator I'd like you to try, and will send you an offline note with code and instructions.. In answer to your 'specific' question, Os/2 System->System Setup->Hardware Manager-Properties, Default Detection level, full Hardware Detection.. (only time I've seen this is on a Crystal based sound card where the .SNP programs the adapter) Stan Koper wrote: > > I just picked up an internal Philips k56flex modem. I have a > dual boot system, Win95 and OS/2 4.0. The modem set up under > Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and > they don't recognize the modem *unless* I stop the boot at the > white square and select full hardware detection. > > When it does work under OS/2 it's still com3 (since the > motherboard has two serial ports), but the Irq is 7. I haven't > tried it under WinOS/2. > > What I'd like to know is, is it possible to establish full > hardware detection *without* interrupting boot up? Is there > some line I can add to config.sys or is there some other process > (like selective install) that I can use to get the modem > recognized by OS/2? > > In article <342F3E86.4012@focus.winternet.com>, > Trev Peterson <tpeterso@focus.winternet.com> wrote: > >I am having problems with a Boca Office Communicator FDV34SVD PNP > >fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I > >checked this using Win95 to verify that it worked there and it did. > > -- Sam Detweiler IBM OS/2 Development Device Driver development and Support OS/2 Advisor
Plug and Pray problems in Warp 4-request configurator
Author: harry travis
Date: Wed, 22 Oct 1997 00:00
Date: Wed, 22 Oct 1997 00:00
13 lines
1556 bytes
1556 bytes
Can someone provide references to an FAQ on disabling the plug and play features of my motherboard so I can assign the IRQ's I want to sound cards and ISA scsi cards for use in OS/2? Some cards offer WIN users greater flexibility in overrideing the plug and play setting s with software, (undoubtedly because they catch more complaints from more numerous users with those OSs) -- ----------------------------------------------------------- "harry travis" <htravis@ibm.net> DemostiX -----------------------------------------------------------
Re: Plug and Pray problems in Warp 4-request configurator
Author: Sam_Detweiler
Date: Wed, 22 Oct 1997 00:00
Date: Wed, 22 Oct 1997 00:00
24 lines
1858 bytes
1858 bytes
Sorry, no mechanism to disable PnP adapters or functions. harry travis wrote: > > Can someone provide references to an FAQ on disabling the plug and play > features of my motherboard so I can assign the IRQ's I want to sound > cards and ISA scsi cards for use in OS/2? Some cards offer WIN users > greater flexibility in overrideing the plug and play setting s with > software, (undoubtedly because they catch more complaints from more > numerous users with those OSs) > > -- > ----------------------------------------------------------- > "harry travis" <htravis@ibm.net> > DemostiX > ----------------------------------------------------------- -- Sam Detweiler IBM OS/2 Development Device Driver development and Support OS/2 Advisor
Re: Plug and Pray problems in Warp 4
Author: Stan Koper
Date: Wed, 22 Oct 1997 00:00
Date: Wed, 22 Oct 1997 00:00
76 lines
3825 bytes
3825 bytes
In article <344D18AF.2412@ibm.net>, "Sam_Detweiler@ibm.net" <Sam_Detweiler@ibm.net> wrote: >Well, > >Assuming this is a decent PnP device, and you've >run hardware detection after its installation, >then rmview /dc from the commandline SHOULD >show you where the modem was configured. > As I said in response to an e-mail message from Sam, I didn't know that you could set up the hardware manager to detect newly-installed hardware on the next boot, and then set it to remember what it found, after that. After I posted the original message, I got to thinking about how helpful troubleshooting had been in guiding me through the setup of a sound card in WinOS/2. And although using online documentation is often like using the Yellow Pages--no matter what category you look in first, you'll find a message directing you somewhere else--I decided to give it a whirl, and looked up plug and play. And it was there that I found that if you click the right mouse button on the hardware manager icon, and select "properties", you will get a menu of choices ranging from no hardware detection to full hardware detection, with detect new hardware and remember what you found last time in between. And that did the trick. Now if I can only figure out how to get the Jazz 16 sound card in my other OS/2 machine to work...(it works fine in Win95, and it's not PnP). >It should NOT be needed to redo detection on >EACH boot however (if this is a good PnP >device) as we (my code) will reconfigure >it to the SAME place as last time detection >was run.. Right. One of the hardware manager choices is to retain the previous results, in effect "remembering what it found the last time detection was enabled". I mean, I had a ton of aggravation getting the modem to work in Win95, until I figured out that you had to run hardware detection twice--once with the card out of the machine (to establish a baseline) and then again with the card in. Until then, Win95 kept assigning it the same com port number as the built-in port. If anyone in the Boston MA area is interested, this is a simple K56flex card from MicroCenter, $59.95 while they last. It has a flash bios, so whenever a standard for 56k is decided on, it should be automatically upgradeable. Right now I'm getting downloads of about 3250 cps (is it cps or bps?), not 56k for sure, but 25% faster than my old 28.8 card. > >Now.. I have a tweak to the ISAPNP configurator >I'd like you to try, and will send you an offline >note with code and instructions.. Received and installed. > >In answer to your 'specific' question, > >Os/2 System->System Setup->Hardware Manager-Properties, >Default Detection level, full Hardware Detection.. > Right. And thanks again.
Re: Plug and Pray problems in Warp 4
Author: Sam_Detweiler
Date: Wed, 22 Oct 1997 00:00
Date: Wed, 22 Oct 1997 00:00
99 lines
4530 bytes
4530 bytes
Sorry. want to add one thing.. When the WPS comes up, the CURRENT BOOT PnP data is saved, PERIOD. You do NOT need to request that the data be saved..it just will be. Unless specifically requested (alt-F1/F5 at boot, or changing the Hardware Manager defaults) the saved current config will be restored on next boot to insure that all PnP hardware is placed at the same location as last boot. Stan Koper wrote: > > In article <344D18AF.2412@ibm.net>, > "Sam_Detweiler@ibm.net" <Sam_Detweiler@ibm.net> wrote: > >Well, > > > >Assuming this is a decent PnP device, and you've > >run hardware detection after its installation, > >then rmview /dc from the commandline SHOULD > >show you where the modem was configured. > > > > As I said in response to an e-mail message from Sam, I didn't > know that you could set up the hardware manager to detect > newly-installed hardware on the next boot, and then set it to > remember what it found, after that. > > After I posted the original message, I got to thinking about > how helpful troubleshooting had been in guiding me through the > setup of a sound card in WinOS/2. And although using online > documentation is often like using the Yellow Pages--no matter > what category you look in first, you'll find a message directing > you somewhere else--I decided to give it a whirl, and looked up > plug and play. > > And it was there that I found that if you click the right > mouse button on the hardware manager icon, and select "properties", > you will get a menu of choices ranging from no hardware detection > to full hardware detection, with detect new hardware and remember > what you found last time in between. > > And that did the trick. > > Now if I can only figure out how to get the Jazz 16 sound card in > my other OS/2 machine to work...(it works fine in Win95, and it's > not PnP). > > >It should NOT be needed to redo detection on > >EACH boot however (if this is a good PnP > >device) as we (my code) will reconfigure > >it to the SAME place as last time detection > >was run.. > > Right. One of the hardware manager choices is to retain the > previous results, in effect "remembering what it found the > last time detection was enabled". > > I mean, I had a ton of aggravation getting the modem to work > in Win95, until I figured out that you had to run hardware > detection twice--once with the card out of the machine (to > establish a baseline) and then again with the card in. Until > then, Win95 kept assigning it the same com port number as > the built-in port. > > If anyone in the Boston MA area is interested, this is a > simple K56flex card from MicroCenter, $59.95 while they > last. It has a flash bios, so whenever a standard for 56k > is decided on, it should be automatically upgradeable. > > Right now I'm getting downloads of about 3250 cps (is it > cps or bps?), not 56k for sure, but 25% faster than my > old 28.8 card. > > > > >Now.. I have a tweak to the ISAPNP configurator > >I'd like you to try, and will send you an offline > >note with code and instructions.. > > Received and installed. > > > > >In answer to your 'specific' question, > > > >Os/2 System->System Setup->Hardware Manager-Properties, > >Default Detection level, full Hardware Detection.. > > > Right. And thanks again. -- Sam Detweiler IBM OS/2 Development Device Driver development and Support OS/2 Advisor
Re: Plug and Pray problems in Warp 4
Author: Richard Steiner
Date: Thu, 23 Oct 1997 00:00
Date: Thu, 23 Oct 1997 00:00
38 lines
2791 bytes
2791 bytes
Here in comp.os.os2.setup, David Moorhouse
<davidm{spamfence}@ariel.ucs.unimelb.edu.au> spake unto us, saying:
>Stan Koper wrote:
>>
>> Right now I'm getting downloads of about 3250 cps (is it
>> cps or bps?), not 56k for sure, but 25% faster than my
>> old 28.8 card.
>>
>It's cps - Characters Per Second. A 56K modem running at
>its theoretical maximum of 56x1024 bps - Bits Per Second -
>should be able to deliver 56x1024/10 = 5734 cps, assuming
>1 start bit, 8 bit data, 1 stop bit, and no compression.
Keep in mind, however, that most error-correction protocols (at least
MNP4 and LAP-M, the two common ones in our own asynch modem context)
actually reframe the data, essentially removing the start and stop bits
which otherwise would accompany each data byte and replacing them with
a smallish header every hundred or so bytes (I admit I don't remember
precise numbers and it varies a little with the specific implementation,
but that's ballpark IIRC).
In a nutshell, a typical connection using EC will approach 8 bits/data
byte, and not 10 bits/data byte.
>Bps is not the same as 'baud', which strictly is transitions
>per second. In the old days, a 300baud modem was 300bps,
>since each transition was 1 bit. Nowadays, the modems
>encode 4 bits or more for each transition.
You bet. I've lost track since the release of Rockwell's V.FastClass,
but I remember that even the old 14.4kbps HST protocol was 6 bits/baud.
--
-Rich Steiner >>>---> rsteiner@skypoint.com >>>---> Bloomington, MN
OS/2 Warp 4 + Linux + Executor = PC Hobbyist Heaven!
CIRCUMVENT: The result of a botched circumcision!
Re: Plug and Pray problems in Warp 4
Author: donm
Date: Fri, 24 Oct 1997 00:00
Date: Fri, 24 Oct 1997 00:00
39 lines
2287 bytes
2287 bytes
In <345082C9.7A5B@ariel.ucs.unimelb.edu.au>, on 10/24/97
at 11:13 AM, David Moorhouse
<davidm{spamfence}@ariel.ucs.unimelb.edu.au> said:
>>Stan Koper wrote:
>>>
>>> Right now I'm getting downloads of about 3250 cps (is it
>>> cps or bps?), not 56k for sure, but 25% faster than my
>>> old 28.8 card.
>>>
>>It's cps - Characters Per Second. A 56K modem running at
>>its theoretical maximum of 56x1024 bps - Bits Per Second -
>>should be able to deliver 56x1024/10 = 5734 cps, assuming
>>1 start bit, 8 bit data, 1 stop bit, and no compression.
>>Bps is not the same as 'baud', which strictly is transitions per second.
>>In the old days, a 300baud modem was 300bps,
>>since each transition was 1 bit. Nowadays, the modems
>>encode 4 bits or more for each transition.
>>DM
PS....
My 28.8 running with SIO and a DTE rate of 115K got download speeds of
3100-3300cps.....
Most internet providers think the 56K modem is one of the bigger jokes of
the computer history...
don.m
Old Age and Treachery
Will Always Overcome
Youthfulness and Skill
-----------------------------------------------------------
donm@ftel.net using Merlin and MR/2 ICE reg#114
-----------------------------------------------------------
Re: Plug and Pray problems in Warp 4
Author: donm
Date: Fri, 24 Oct 1997 00:00
Date: Fri, 24 Oct 1997 00:00
37 lines
2401 bytes
2401 bytes
In <345082C9.7A5B@ariel.ucs.unimelb.edu.au>, on 10/24/97
at 11:13 AM, David Moorhouse
<davidm{spamfence}@ariel.ucs.unimelb.edu.au> said:
>>Stan Koper wrote:
>>>
>>> Right now I'm getting downloads of about 3250 cps (is it
>>> cps or bps?), not 56k for sure, but 25% faster than my
>>> old 28.8 card.
>>>
>>It's cps - Characters Per Second. A 56K modem running at
>>its theoretical maximum of 56x1024 bps - Bits Per Second -
>>should be able to deliver 56x1024/10 = 5734 cps, assuming
>>1 start bit, 8 bit data, 1 stop bit, and no compression.
>>Bps is not the same as 'baud', which strictly is transitions per second.
>>In the old days, a 300baud modem was 300bps,
>>since each transition was 1 bit. Nowadays, the modems
>>encode 4 bits or more for each transition.
>>DM
Slight mod to the equation.... neither of the 56K modems can
actually run 56K. 53K is the legal "speed limit" due to FCC
regs... that plus the "56K" standard is based on a series of assumtions,
such as only one AtoD conversion in the connection. Any more than that and
you have an expensive 33.6K modem... :))
don.m
Old Age and Treachery
Will Always Overcome
Youthfulness and Skill
-----------------------------------------------------------
donm@ftel.net using Merlin and MR/2 ICE reg#114
-----------------------------------------------------------
Re: Plug and Pray problems in Warp 4
Author: David Moorhouse
Date: Fri, 24 Oct 1997 00:00
Date: Fri, 24 Oct 1997 00:00
17 lines
1774 bytes
1774 bytes
Stan Koper wrote: > > Right now I'm getting downloads of about 3250 cps (is it > cps or bps?), not 56k for sure, but 25% faster than my > old 28.8 card. > It's cps - Characters Per Second. A 56K modem running at its theoretical maximum of 56x1024 bps - Bits Per Second - should be able to deliver 56x1024/10 = 5734 cps, assuming 1 start bit, 8 bit data, 1 stop bit, and no compression. Bps is not the same as 'baud', which strictly is transitions per second. In the old days, a 300baud modem was 300bps, since each transition was 1 bit. Nowadays, the modems encode 4 bits or more for each transition. DM
Modem dl speeds was (Plug and Pray problems in Warp 4)
Author: mchasson
Date: Sun, 26 Oct 1997 00:00
Date: Sun, 26 Oct 1997 00:00
56 lines
3349 bytes
3349 bytes
In <3450ec89$3$qbaz$mr2ice@nntp.ftel.net>, on 10/24/97 at 11:44 AM, donm@ftel.net said: >>>Stan Koper wrote: >>>> >>>> Right now I'm getting downloads of about 3250 cps (is it >>>> cps or bps?), not 56k for sure, but 25% faster than my >>>> old 28.8 card. >>>> >>>It's cps - Characters Per Second. A 56K modem running at >>>its theoretical maximum of 56x1024 bps - Bits Per Second - >>>should be able to deliver 56x1024/10 = 5734 cps, assuming >>>1 start bit, 8 bit data, 1 stop bit, and no compression. >>>Bps is not the same as 'baud', which strictly is transitions per second. >>>In the old days, a 300baud modem was 300bps, >>>since each transition was 1 bit. Nowadays, the modems >>>encode 4 bits or more for each transition. >>>DM >PS.... >My 28.8 running with SIO and a DTE rate of 115K got download speeds of >3100-3300cps..... >Most internet providers think the 56K modem is one of the bigger jokes of >the computer history... >don.m >----------------------------------------------------------- >donm@ftel.net using Merlin and MR/2 ICE reg#114 >----------------------------------------------------------- Yeah. I have been reading this thread with some amazement. I know that local phone lines are not much in most places, and that I am truly fortunate to live in a building that has just been rewired in fiber, but if you guys think that the modem is doing great at the above speeds, permit me to disagree. No modem will overcome a poor connection. I am running a Zoom 28800 from an oem box (very cheap) and my carrier speed on ibm.net (granted they are superior to most) is consistently 28800, with the connect speed at 115200 ( also all the time). Downloads are shown by the ibm dialer at up to 3300 (average) when everything is humming. I did run the test on the USR bbs and it came in at a perfect connection so I am not surprised. but you should get at least 5000 dl speed to justify the cost of the modem. -- ---------------------------------------------------- ------ Monroe Chasson mchasson@ibm.net "...apres moi le deluge." - Louis XIV (every dog has its day -tr.) ----------------------------------------------------------- MR2ICE reg#51 and OS2
Re: Modem dl speeds was (Plug and Pray problems in Warp 4)
Author: John Brush
Date: Sun, 26 Oct 1997 00:00
Date: Sun, 26 Oct 1997 00:00
70 lines
4206 bytes
4206 bytes
In <3453c247$1$zpunffba$mr2ice@news-s01.ny.us.ibm.net>, on 10/26/97 at 05:12 PM, mchasson@ibm.net said: **In <3450ec89$3$qbaz$mr2ice@nntp.ftel.net>, on 10/24/97 at 11:44 AM, ** donm@ftel.net said: **>>>Stan Koper wrote: **>>>> **>>>> Right now I'm getting downloads of about 3250 cps (is it **>>>> cps or bps?), not 56k for sure, but 25% faster than my **>>>> old 28.8 card. **>>>> **>>>It's cps - Characters Per Second. A 56K modem running at **>>>its theoretical maximum of 56x1024 bps - Bits Per Second - **>>>should be able to deliver 56x1024/10 = 5734 cps, assuming **>>>1 start bit, 8 bit data, 1 stop bit, and no compression. **>>>Bps is not the same as 'baud', which strictly is transitions per second. **>>>In the old days, a 300baud modem was 300bps, **>>>since each transition was 1 bit. Nowadays, the modems **>>>encode 4 bits or more for each transition. **>>>DM **>PS.... **>My 28.8 running with SIO and a DTE rate of 115K got download speeds of **>3100-3300cps..... **>Most internet providers think the 56K modem is one of the bigger jokes of **>the computer history... **>don.m **>----------------------------------------------------------- **>donm@ftel.net using Merlin and MR/2 ICE reg#114 **>----------------------------------------------------------- **Yeah. I have been reading this thread with some amazement. I know **that local phone lines are not much in most places, and that I am **truly fortunate to live in a building that has just been rewired in **fiber, but if you guys think that the modem is doing great at the **above speeds, permit me to disagree. No modem will overcome a poor **connection. **I am running a Zoom 28800 from an oem box (very cheap) and my **carrier speed on ibm.net (granted they are superior to most) is **consistently 28800, with the connect speed at 115200 ( also all the **time). Downloads are shown by the ibm dialer at up to 3300 **(average) when everything is humming. I did run the test on the USR **bbs and it came in at a perfect connection so I am not surprised. **but you should get at least 5000 dl speed to justify the cost of **the modem. I get 3300cps downloads pretty consistently with the crappy old phone lines that we have, using a 28.8K USR external. My other modem is upgraded to 33.6K and it gets 3600cps most of the time. I can't do 53K because of too many analog switches, but to tell you the truth, 53K is not that great an improvement over 33K considering the cost to me for the modem, to me for the detrimental effect on my ISP having to support two stupid standards, and the aggravation of having to put up with the world claiming we all should be celebrating this tiny increase in speed. On top of all of that, its only one way, so if you upload files and the like, no change at all. If I didn't know better, I would swear that that criminal Gates is behind this hype. :) Nah, not worth it, if you ask me (I know, no one did <g>) John
Re: Modem dl speeds was (Plug and Pray problems in Warp 4)
Author: Esmond Pitt
Date: Tue, 28 Oct 1997 00:00
Date: Tue, 28 Oct 1997 00:00
30 lines
2231 bytes
2231 bytes
This is a multi-part message in MIME format. --------------220DE7D543017814E0ECF705 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here in Australia I'm using a 33.6K modem with VJ and MP5 on. I get peak rates of 6.3K as shown on the IBM dialer. --------------220DE7D543017814E0ECF705 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Esmond Pitt Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Esmond Pitt n: Pitt;Esmond org: CP Telemedia Software Laboratories adr: 493 St Kilda Rd;;;Melbourne;Victoria;3004;Australia email;internet: pitte@cpgen.cpg.com.au title: Consultant tel;work: 61 3 9243 2285 tel;fax: 61 3 9243 2233 tel;home: 61 3 9534 5704 x-mozilla-cpt: ;0 x-mozilla-html: FALSE end: vcard --------------220DE7D543017814E0ECF705--
Re: Plug and Pray problems in Warp 4
Author: zeus
Date: Wed, 29 Oct 1997 00:00
Date: Wed, 29 Oct 1997 00:00
26 lines
2102 bytes
2102 bytes
In <DtMT0UjRQE7f092yn@netcom.com>, skoper@netcom.com (Stan Koper) writes: >I just picked up an internal Philips k56flex modem. I have a >dual boot system, Win95 and OS/2 4.0. The modem set up under >Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and >they don't recognize the modem *unless* I stop the boot at the >white square and select full hardware detection. > >When it does work under OS/2 it's still com3 (since the >motherboard has two serial ports), but the Irq is 7. I haven't >tried it under WinOS/2. > >What I'd like to know is, is it possible to establish full >hardware detection *without* interrupting boot up? Is there >some line I can add to config.sys or is there some other process >(like selective install) that I can use to get the modem >recognized by OS/2? > > >In article <342F3E86.4012@focus.winternet.com>, >Trev Peterson <tpeterso@focus.winternet.com> wrote: >>I am having problems with a Boca Office Communicator FDV34SVD PNP >>fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I >>checked this using Win95 to verify that it worked there and it did. >> >disable one of your comports if it is an internal modem
Re: Plug and Pray problems in Warp 4
Author: wellner
Date: Thu, 30 Oct 1997 00:00
Date: Thu, 30 Oct 1997 00:00
39 lines
2466 bytes
2466 bytes
In <637nse$qb0@tandem.CAM.ORG>, zeus@cam.org writes: >In <DtMT0UjRQE7f092yn@netcom.com>, skoper@netcom.com (Stan Koper) writes: >>I just picked up an internal Philips k56flex modem. I have a >>dual boot system, Win95 and OS/2 4.0. The modem set up under >>Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and >>they don't recognize the modem *unless* I stop the boot at the >>white square and select full hardware detection. >> >>When it does work under OS/2 it's still com3 (since the >>motherboard has two serial ports), but the Irq is 7. I haven't >>tried it under WinOS/2. >> >>What I'd like to know is, is it possible to establish full >>hardware detection *without* interrupting boot up? Is there >>some line I can add to config.sys or is there some other process >>(like selective install) that I can use to get the modem >>recognized by OS/2? If you go to the Properties setting of the Hardware Manager you can set for full hardware detect. (OS/2 System>System Setup>Hardware Manager and right click). >> >> >>In article <342F3E86.4012@focus.winternet.com>, >>Trev Peterson <tpeterso@focus.winternet.com> wrote: >>>I am having problems with a Boca Office Communicator FDV34SVD PNP >>>fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I >>>checked this using Win95 to verify that it worked there and it did. >>> >>disable one of your comports if it is an internal modem > > ------- Ed Wellner Yes, these are my opinions, not those of the company I work for.
Re: Plug and Pray problems in Warp 4
Author: Charlie Jager
Date: Sat, 08 Nov 1997 00:00
Date: Sat, 08 Nov 1997 00:00
71 lines
3579 bytes
3579 bytes
In message <63a458$qg0@interserv.etn.com> - wellner@pop.mke.etn.com writes: :> :>In <637nse$qb0@tandem.CAM.ORG>, zeus@cam.org writes: :>>In <DtMT0UjRQE7f092yn@netcom.com>, skoper@netcom.com (Stan Koper) writes: :>>>I just picked up an internal Philips k56flex modem. I have a :>>>dual boot system, Win95 and OS/2 4.0. The modem set up under :>>>Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and :>>>they don't recognize the modem *unless* I stop the boot at the :>>>white square and select full hardware detection. :>>> :>>>When it does work under OS/2 it's still com3 (since the :>>>motherboard has two serial ports), but the Irq is 7. I haven't :>>>tried it under WinOS/2. :>>> :>>>What I'd like to know is, is it possible to establish full :>>>hardware detection *without* interrupting boot up? Is there :>>>some line I can add to config.sys or is there some other process :>>>(like selective install) that I can use to get the modem :>>>recognized by OS/2? :> :>If you go to the Properties setting of the Hardware Manager you can set for :>full hardware detect. (OS/2 System>System Setup>Hardware Manager and right click). :> :>>> :>>> :>>>In article <342F3E86.4012@focus.winternet.com>, :>>>Trev Peterson <tpeterso@focus.winternet.com> wrote: :>>>>I am having problems with a Boca Office Communicator FDV34SVD PNP :>>>>fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I :>>>>checked this using Win95 to verify that it worked there and it did. :>>>> :>>>disable one of your comports if it is an internal modem :>> :>> :> :> :> :>------- :>Ed Wellner :>Yes, these are my opinions, not those of the company I work for. :> There are a couple things you can try. First, if there are jumpers on the modem for com port and irq make sure you have them set correctly. If you have and OS/2 still doesn't recognize it, reboot with full hardware detect and then look at the Hardware Manager. Find out what hexadecimal port address the modem is using, and what irq. If these aren't reflected in the hardware manager, bring up an OS/2 window and type: rmview/dc |more then scroll through all of the details until you find the modem and write down the port address and irq. Next you can revise your com.sys line in your config.sys file like this: device=x:\os2\boot\com.sys (n,addr,irq) n=com port addr=port address irq=irq So if you want com3 at port address 3E8H to use irq 7, then type: x:\os2\boot\com.sys (3,3E8,7) This should work as long as nothing else is using this address and irq.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads