Hi,

I have a Toshiba 610CT laptop (mfg abt 1995) that originally had Windows 95. I installed Windows 98SE (removed HD and put "WIN98" folder from System
CD onto C:\ of HD).

I have been using a Megahertz 56K PC Card modem (AOK)

I have a PCMCIA PC card with USB port (adapter) and the Windows 98 driver for this adapter. Windows MUST detect this PC card before I can install the driver.

When I boot up the laptop, Win98 does NOT detect it. Even trying a "Add Hardware" Search via Control Panel does NOT "work". Also, it does NOT
show in the Device Manager's list.

BTW, Another Compaq Windows 95 laptop does detect this PC card!

Is it possible the Cardbuss hardware is the real cause of my problem?

Thank You in advance, John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

jaugustine@verizon.net wrote:

Hi,

I have a Toshiba 610CT laptop (mfg abt 1995) that originally had Windows 95. I installed Windows 98SE (removed HD and put "WIN98" folder from System CD onto C:\ of HD).

I have been using a Megahertz 56K PC Card modem (AOK)

I have a PCMCIA PC card with USB port (adapter) and the Windows 98 driver
for this adapter. Windows MUST detect this PC card before I can install the driver.

When I boot up the laptop, Win98 does NOT detect it. Even trying a "Add
Hardware" Search via Control Panel does NOT "work". Also, it does NOT
show in the Device Manager's list.

BTW, Another Compaq Windows 95 laptop does detect this PC card!

Is it possible the Cardbuss hardware is the real cause of my problem?

Thank You in advance, John

There is probably a host bus chip between the internal
bus and the CardBus.

SB
|
| PCI
|
+------- cardbus-bridge ------ (Cardbus slot) -- Modem-card

I recommend booting an alternate OS, one equipped
with utilities to suss out hardware connectivity,
and whether the cardbus-bridge is turned ON.

Or, you can try Everest. This is where it was the last time.

"EVEREST Free Edition 2.20"
http://www.majorgeeks.com/files/details/everest_free_edition.html

And look in the PCI section.

https://i.postimg.cc/QxXgwV9S/Lavalys-Everest.gif

The database on that copy is pretty old, so newer computers,
almost all the entries will be [nodb], meaning the VEN:DEV
or VID:PID are not in the database. Still, it gives you
some idea the machine is alive.

Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

<SNIP>

There is probably a host bus chip between the internal
bus and the CardBus.

SB
|
| PCI
|
+------- cardbus-bridge ------ (Cardbus slot) -- Modem-card

I recommend booting an alternate OS, one equipped
with utilities to suss out hardware connectivity,
and whether the cardbus-bridge is turned ON.

Or, you can try Everest. This is where it was the last time.

"EVEREST Free Edition 2.20"
http://www.majorgeeks.com/files/details/everest_free_edition.html

And look in the PCI section.

https://i.postimg.cc/QxXgwV9S/Lavalys-Everest.gif

The database on that copy is pretty old, so newer computers,
almost all the entries will be [nodb], meaning the VEN:DEV
or VID:PID are not in the database. Still, it gives you
some idea the machine is alive.

Paul

Hi Paul,

I downloaded Eversthome220.zip and by golly, that is a VERY NICE
utility,

I have used "System Analyser" V5.2 (11-21-01) for getting system information, but Everest is much more advanced by comparison.

I could post a part of the "Report" (saved in text format) relating to PCI, if that would help?

Thanks in advance, John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

jaugustine@verizon.net wrote:

<SNIP>

There is probably a host bus chip between the internal
bus and the CardBus.

SB
|
| PCI
|
+------- cardbus-bridge ------ (Cardbus slot) -- Modem-card

I recommend booting an alternate OS, one equipped
with utilities to suss out hardware connectivity,
and whether the cardbus-bridge is turned ON.

Or, you can try Everest. This is where it was the last time.

"EVEREST Free Edition 2.20"
http://www.majorgeeks.com/files/details/everest_free_edition.html

And look in the PCI section.

https://i.postimg.cc/QxXgwV9S/Lavalys-Everest.gif

The database on that copy is pretty old, so newer computers,
almost all the entries will be [nodb], meaning the VEN:DEV
or VID:PID are not in the database. Still, it gives you
some idea the machine is alive.

Paul

Hi Paul,

I downloaded Eversthome220.zip and by golly, that is a VERY NICE
utility,

I have used "System Analyser" V5.2 (11-21-01) for getting system information, but Everest is much more advanced by comparison.

I could post a part of the "Report" (saved in text format) relating to PCI, if that would help?

Thanks in advance, John

If you want. I can't guarantee I'll recognize the bridge, but
maybe it will have an obvious name on it as to what it does.

Sometimes, in the old days, they had combo chips with four
functions, and that makes it harder to figure out just
what the purpose of the chip is.

Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Paul,

I downloaded Eversthome220.zip and by golly, that is a VERY NICE
utility,

I have used "System Analyser" V5.2 (11-21-01) for getting system
information, but Everest is much more advanced by comparison.

I could post a part of the "Report" (saved in text format) relating to >> PCI, if that would help?

Thanks in advance, John

If you want. I can't guarantee I'll recognize the bridge, but
maybe it will have an obvious name on it as to what it does.

Sometimes, in the old days, they had combo chips with four
functions, and that makes it harder to figure out just
what the purpose of the chip is.

Paul

Hi Paul,

I have EXTRACTED from the report the following:

If there is a clue in this information, I hope you find it.

Note: "Megahertz" is the PC Card 56K modem.

Thanks in advance, John

- - - - - - - - - - - - - - - - - - - - - - - - - - -
Computer:
Operating System Microsoft Windows 98 SE
OS Service Pack -
DirectX 4.06.03.0518 (DirectX 6.
Network:
Network Adapter PPP Adapter.
Network Adapter PPP Adapter.
Modem Megahertz XJ1144 or XJ2144 PCMCIA Modem


--------[ PCI / PnP Audio
-----------------------------------------------------
ESS ES688 AudioDrive
PnP

PCMCIA socket:
PCIC or compatible PCMCIA controller
PCMCIA Card Services

Device Properties:
Driver Description Megahertz XJ1144 or XJ2144 PCMCIA Modem
Driver Date 4/23/99
Driver Provider Megahertz Corp.
INF File MDMMHRTZ.INF
Hardware ID
PCMCIA\MEGAHERTZ-XJ1144-5C3E, PCMCIA\MEGAHERTZ-XJ1144-0102-0005

Device Resources:
IRQ 03
Port 02F8-02FF


[ PCMCIA socket / PCIC or compatible PCMCIA controller ]

Device Properties:
Driver Description PCIC or compatible PCMCIA controller
Driver Date 9/2/02
Driver Provider Microsoft
INF File MICROS~1.INF
Hardware ID BIOS\*PNP0E00,
*PNP0E00

Device Resources:
IRQ 15
Port 03E0-03E1

[ PCMCIA socket / PCMCIA Card Services ]

Device Properties:
Driver Description PCMCIA Card Services
Driver Date 4/23/99
Driver Provider Microsoft
INF File PCMCIA.INF
Hardware ID PCCARD

Device Resources:
Memory 000D0000-000D0FFF

PNP0E00 PCIC Compatible PCMCIA Controller
PNP0000 Programmable Interrupt Controller

PCMCIA Devices:
MEGAHERTZ-XJ1144-5C3E Megahertz XJ1144 or XJ2144 PCMCIA Modem
PCCARD PCMCIA Card Services

ntroller
IRQ 03 Undetermined Megahertz XJ1144 or XJ2144 PCMCIA Modem
IRQ 04 Exclusive Communications Port (COM1)
IRQ 06 Undetermined Standard Floppy Disk Contsk Controller
IRQ 15 Undetermined PCIC or compatible PCMCIA controller
Memory 00000000-0009FFFF Undetermined System board extension for PnP BIOS
sk Controller
Port 0220-022F Exclusive ES688 AudioDrive
Port 02F8-02FF Exclusive Megahertz XJ1144 or XJ2144 PCMCIA Modem
Port 0378-037A Undetermined Printer Port (LPT1)
Port 0388-038B Exclusive ES688 AudioDrive
Port 03B4-03B5 Undetermined Chips & Tech. Accelerator

Port 03E0-03E1 Undetermined PCIC or compatible PCMCIA controller
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

jaugustine@verizon.net wrote:

Hi Paul,

I downloaded Eversthome220.zip and by golly, that is a VERY NICE
utility,

I have used "System Analyser" V5.2 (11-21-01) for getting system
information, but Everest is much more advanced by comparison.

I could post a part of the "Report" (saved in text format) relating to
PCI, if that would help?

Thanks in advance, John

If you want. I can't guarantee I'll recognize the bridge, but
maybe it will have an obvious name on it as to what it does.

Sometimes, in the old days, they had combo chips with four
functions, and that makes it harder to figure out just
what the purpose of the chip is.

Paul

Hi Paul,

I have EXTRACTED from the report the following:

If there is a clue in this information, I hope you find it.

Note: "Megahertz" is the PC Card 56K modem.

Thanks in advance, John

- - - - - - - - - - - - - - - - - - - - - - - - - - -
Computer:
Operating System Microsoft Windows 98 SE
OS Service Pack -
DirectX 4.06.03.0518 (DirectX 6.
Network:
Network Adapter PPP Adapter.
Network Adapter PPP Adapter.
Modem Megahertz XJ1144 or XJ2144 PCMCIA Modem

--------[ PCI / PnP Audio -----------------------------------------------------
ESS ES688 AudioDrive
PnP

PCMCIA socket:
PCIC or compatible PCMCIA controller
PCMCIA Card Services

Device Properties:
Driver Description Megahertz XJ1144 or XJ2144 PCMCIA Modem
Driver Date 4/23/99
Driver Provider Megahertz Corp.
INF File MDMMHRTZ.INF
Hardware ID
PCMCIA\MEGAHERTZ-XJ1144-5C3E, PCMCIA\MEGAHERTZ-XJ1144-0102-0005

Device Resources:
IRQ 03
Port 02F8-02FF

[ PCMCIA socket / PCIC or compatible PCMCIA controller ]

Device Properties:
Driver Description PCIC or compatible PCMCIA controller
Driver Date 9/2/02
Driver Provider Microsoft
INF File MICROS~1.INF
Hardware ID BIOS\*PNP0E00, *PNP0E00

Device Resources:
IRQ 15
Port 03E0-03E1

[ PCMCIA socket / PCMCIA Card Services ]

Device Properties:
Driver Description PCMCIA Card Services
Driver Date 4/23/99
Driver Provider Microsoft
INF File PCMCIA.INF
Hardware ID PCCARD

Device Resources:
Memory 000D0000-000D0FFF

PNP0E00 PCIC Compatible PCMCIA
Controller
PNP0000 Programmable Interrupt
Controller

PCMCIA Devices:
MEGAHERTZ-XJ1144-5C3E Megahertz XJ1144 or XJ2144 PCMCIA Modem
PCCARD PCMCIA Card Services

ntroller
IRQ 03 Undetermined Megahertz XJ1144 or XJ2144 PCMCIA Modem
IRQ 04 Exclusive Communications Port (COM1)
IRQ 06 Undetermined Standard Floppy Disk Contsk Controller
IRQ 15 Undetermined PCIC or compatible PCMCIA controller
Memory 00000000-0009FFFF Undetermined System board extension for PnP BIOS
sk Controller
Port 0220-022F Exclusive ES688 AudioDrive
Port 02F8-02FF Exclusive Megahertz XJ1144 or XJ2144 PCMCIA Modem
Port 0378-037A Undetermined Printer Port (LPT1)
Port 0388-038B Exclusive ES688 AudioDrive
Port 03B4-03B5 Undetermined Chips & Tech. Accelerator

Port 03E0-03E1 Undetermined PCIC or compatible PCMCIA controller

Example of a bus bridge.

Cirrus Logic PCIC compatible PCMCIA controller

Example of a driver file. (See if there is
already one of these in the OS.)

MSPCIC.dll

While the PNP entry for the various hardware bus
controllers would work, there is an ACPI-like
entry too. This implies the chip which bridges from
PCI bus to PCMCIA slot, follows standard register
designations.

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607

Whereas the

Megahertz XJ1144 or XJ2144 PCMCIA Modem

entry, that's going to present PNP information when
it runs on the PCMCIA bus in the slot.

The information in the table, doesn't tell much more than
that. I don't have any indication, who made the bus
bridge. And maybe it doesn't matter, as long as it works :-)

Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

<SNIP>

Example of a bus bridge.

Cirrus Logic PCIC compatible PCMCIA controller

Example of a driver file. (See if there is
already one of these in the OS.)

MSPCIC.dll

While the PNP entry for the various hardware bus
controllers would work, there is an ACPI-like
entry too. This implies the chip which bridges from
PCI bus to PCMCIA slot, follows standard register
designations.

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607

Whereas the

Megahertz XJ1144 or XJ2144 PCMCIA Modem

entry, that's going to present PNP information when
it runs on the PCMCIA bus in the slot.

The information in the table, doesn't tell much more than
that. I don't have any indication, who made the bus
bridge. And maybe it doesn't matter, as long as it works :-)

Paul

Hi Paul,

I found "MSPCIC.DLL" in WINDOWS\SYSTEM folder.

Also, in WINDOWS\INF folder, "PCMCIA.INF" file has

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607
(and other lines)

[Control Flags] (section, same file)

"ExcludeFromSelect=PCI\CC_0607"

I have NO idea what that does.

Again, Thanks, John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

jaugustine@verizon.net wrote:

<SNIP>

Example of a bus bridge.

Cirrus Logic PCIC compatible PCMCIA controller

Example of a driver file. (See if there is
already one of these in the OS.)

MSPCIC.dll

While the PNP entry for the various hardware bus
controllers would work, there is an ACPI-like
entry too. This implies the chip which bridges from
PCI bus to PCMCIA slot, follows standard register
designations.

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607

Whereas the

Megahertz XJ1144 or XJ2144 PCMCIA Modem

entry, that's going to present PNP information when
it runs on the PCMCIA bus in the slot.

The information in the table, doesn't tell much more than
that. I don't have any indication, who made the bus
bridge. And maybe it doesn't matter, as long as it works :-)

Paul

Hi Paul,

I found "MSPCIC.DLL" in WINDOWS\SYSTEM folder.

Also, in WINDOWS\INF folder, "PCMCIA.INF" file has

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607
(and other lines)

[Control Flags] (section, same file)

"ExcludeFromSelect=PCI\CC_0607"

I have NO idea what that does.

Again, Thanks, John

It's presumably a Microsoft generic driver for the bridge.

I don't think you can just wire the PCI bus directly to
the Cardbus, and there must be some silicon in there
somewhere to do that.

With that driver in place, then it should be possible to
install the modem driver when the modem card is inserted.

Without the bridge, there's a good chance plugging in
the modem would elicit no response at all. If the system
can see an "event" show up, something to trigger PNP,
then chances are there's a driver in place for the bridge.

Even if the Cardbus was 32 bit (say, muxed address and data),
I think there's a rate difference involved too. That bus
runs a bit slower than PCI bus. The wikipedia on PCMCIA or
cardbus might have more details on the particulars.

I would have expected the silicon to perhaps have more
functions than that, and as a consequence, have a more
visible driver situation. Bridges are relatively low
key items (complex in terms of getting the hardware
details at the gate level right, not so much at
the driver level). And as computer users, we're used
to that one being auto-resolved without us knowing
anything has happened. The OS discovers and probes
past a metric ton of bridges inside, and these
kinds of things hardly ever show up in "trouble"
postings :-)

But getting a modem driver or whatever driver the
card needs, that's a different matter. More trouble
is to be expected in such cases.

Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I found "MSPCIC.DLL" in WINDOWS\SYSTEM folder.

Also, in WINDOWS\INF folder, "PCMCIA.INF" file has

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607
(and other lines)

[Control Flags] (section, same file)

"ExcludeFromSelect=PCI\CC_0607"

I have NO idea what that does.

Again, Thanks, John

It's presumably a Microsoft generic driver for the bridge.

I don't think you can just wire the PCI bus directly to
the Cardbus, and there must be some silicon in there
somewhere to do that.

With that driver in place, then it should be possible to
install the modem driver when the modem card is inserted.

Hi Paul,

The modem PC Card was NOT a problem (detection, etc)
I indicated the Megahertz PC card modem works AOK so
you know that the PC card slot is NOT defective.

My MAIN OBJECTIVE is for Win98 to detect a PC card
adapter with a USB port because I have the Win98
driver for that adapter, but Win98 MUST detect New
Hardware before I can install the adapter driver.
That is in the adapter's instructions.

Again, Thank You for your help, John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

jaugustine@verizon.net wrote:

I found "MSPCIC.DLL" in WINDOWS\SYSTEM folder.

Also, in WINDOWS\INF folder, "PCMCIA.INF" file has

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607
(and other lines)

[Control Flags] (section, same file)

"ExcludeFromSelect=PCI\CC_0607"

I have NO idea what that does.

Again, Thanks, John

It's presumably a Microsoft generic driver for the bridge.

I don't think you can just wire the PCI bus directly to
the Cardbus, and there must be some silicon in there
somewhere to do that.

With that driver in place, then it should be possible to
install the modem driver when the modem card is inserted.

Hi Paul,

The modem PC Card was NOT a problem (detection, etc)
I indicated the Megahertz PC card modem works AOK so
you know that the PC card slot is NOT defective.

My MAIN OBJECTIVE is for Win98 to detect a PC card
adapter with a USB port because I have the Win98
driver for that adapter, but Win98 MUST detect New
Hardware before I can install the adapter driver.
That is in the adapter's instructions.

Again, Thank You for your help, John

You mean, like the maximus decim driver.

nusb31e__maximus_decim_win98.exe 759,296 bytes

From the readme in there.

"Maximus Decim Native USB ver.3.1

Only for Windows 98SE English !!!

*Native (without installation of additional drivers
for each type) support USB flash drives, digital
photo and videocameras and other similar devices.
*Universal Stack USB 2.0 (without installation
of additional drivers for each chipsets) with uninstall.

1.Remove ALL drivers USB flash drives.
2.Remove ALL drivers USB 2.0 controllers.
3.Remove ALL unknown devices.
4.Install NUSB 3.1 and reboot.
5.After detection new USB 2.0 controllers
(if it will occur) too it is necessary to be reboot.

Remember! You install it at own risk!
"

Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

<SNIP>

The modem PC Card was NOT a problem (detection, etc)
I indicated the Megahertz PC card modem works AOK so
you know that the PC card slot is NOT defective.

My MAIN OBJECTIVE is for Win98 to detect a PC card
adapter with a USB port because I have the Win98
driver for that adapter, but Win98 MUST detect New
Hardware before I can install the adapter driver.
That is in the adapter's instructions.

Again, Thank You for your help, John

You mean, like the maximus decim driver.

nusb31e__maximus_decim_win98.exe 759,296 bytes

From the readme in there.

"Maximus Decim Native USB ver.3.1

Only for Windows 98SE English !!!

*Native (without installation of additional drivers
for each type) support USB flash drives, digital
photo and videocameras and other similar devices.
*Universal Stack USB 2.0 (without installation
of additional drivers for each chipsets) with uninstall.

1.Remove ALL drivers USB flash drives.
2.Remove ALL drivers USB 2.0 controllers.
3.Remove ALL unknown devices.
4.Install NUSB 3.1 and reboot.
5.After detection new USB 2.0 controllers
(if it will occur) too it is necessary to be reboot.

Remember! You install it at own risk!
"

Hi Paul,

I downloaded "nusb31e.exe" and will give it a try.

Since the external floppy drive is defective, I use
"PC Link" (like LapLink) to transfer "stuff" to this small Toshiba laptop.

Having a working USB adapter would be AWESOME.

Again Thanks John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

<SNIP>

You mean, like the maximus decim driver.

nusb31e__maximus_decim_win98.exe 759,296 bytes

From the readme in there.

"Maximus Decim Native USB ver.3.1

Only for Windows 98SE English !!!

*Native (without installation of additional drivers
for each type) support USB flash drives, digital
photo and videocameras and other similar devices.
*Universal Stack USB 2.0 (without installation
of additional drivers for each chipsets) with uninstall.

1.Remove ALL drivers USB flash drives.
2.Remove ALL drivers USB 2.0 controllers.
3.Remove ALL unknown devices.
4.Install NUSB 3.1 and reboot.
5.After detection new USB 2.0 controllers
(if it will occur) too it is necessary to be reboot.

Remember! You install it at own risk!
"

Hi Paul,

I downloaded "nusb31e.exe" and will give it a try.

Since the external floppy drive is defective, I use
"PC Link" (like LapLink) to transfer "stuff" to this small Toshiba laptop.

Having a working USB adapter would be AWESOME.

Hi Paul,

UPDATE:

Since this small Toshiba 610CT does NOT have a USB port,
if it did, I would NOT bother with the PC Card to USB port
adapter. With DEFECTIVE external FDDs (two) made for
this laptop, the ONLY way (without removing HD) I can put
"stuff" (updated files, etc.) on it, is using "PC Link", but that requires connecting a LapLink LPT cable to another PC. Not very
convenient, but only method I know.

Even though "nusb31e.exe" does NOT solve my adapter
DETECTION problem, I will keep it. Note: I have several
Lexar USB flash drives with the Win98 driver.

I have considered buying an external 3.5" FDD that connects
to the LPT port, but if I knew with confidence, it is in GOOD condition,
I would pay $103.** for it.

BTW: I could buy anther external FDD for this model laptop, but
the FDD uses a belt. I went through a lot of trouble replacing the
belt in one, but it did not last very long.

Thanks again for all your help, John
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)