matt020 wrote: 10 Jun 2021 16:02
Ok, by using CDIS jumper on the TF1260?
Yeah.. and for others with issues do the same on your respective card.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Still failed to initialise the driver, but Im wondering if its prism2.device and OS3.2 because "cardreset" and "cardpatch" programs work. I would think if theres a problem with pcmcia/os32/tf1260 that it would fail early on in the piece with cardreset ?
matt020 wrote: 14 Jun 2021 15:30
Ok, I got around to jumpering CDIS.
No change.
Still failed to initialise the driver, but Im wondering if its prism2.device and OS3.2 because "cardreset" and "cardpatch" programs work. I would think if theres a problem with pcmcia/os32/tf1260 that it would fail early on in the piece with cardreset ?
I made a post on a Facebook group and someone has suggested that it might be the version of SetPatch included in 3.2 that might be causing PCMCIA problems, so I will try another (earlier) version of SetPatch and report back.
Ok, I have found that my PCMCIA and OS3.2 issues are a result of a missing pccard.library
Once I moved this across to libs: , it appears to be working and I can get the wifi card to connect to the wireless network as it did under 3.1
I am a tad embarrassed. Silly error on my part. But it means PCMCIA + OS3.2 + TF1260 is all OK at this end.
matt020 wrote: 21 Jun 2021 11:52
Ok, I have found that my PCMCIA and OS3.2 issues are a result of a missing pccard.library
Once I moved this across to libs: , it appears to be working and I can get the wifi card to connect to the wireless network as it did under 3.1
I am a tad embarrassed. Silly error on my part. But it means PCMCIA + OS3.2 + TF1260 is all OK at this end.
Thats good to know.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."