First, my answers to your questions:
> ........ Which
>library are you using? What is the time/date stamp of the .geo on your target
>system? Is there a more recent version on the SDK CD-ROM that you could use
>instead?
- the timestamps on the pcmcia.geo and on the pcmciaec.goe in the
host system as well as in the target system are all 11-06-95
- there is no further pcmcia(ec).geo on my system
- no, I don't have another version of SDK CD-ROM accessible
Next, I have some questions left:
> The library you require is newer than the one on the system. In other
>words, you're asking for a library with a higher protocol number than the one
>on the system. .........
Let's assume the system asks for a pcmcia library with protocol number P.
1.Who tells the system that protocol number P is required ?
> The protocol number of the library you want (specified in the file header
>of the .geo file) and the protocol number of the library on the system
>(stored in it's file header).
2.In the file header of which geo file ? And how does it get there ?
3.Why isn't it possible for me to change something (e.g. the file
header)
such that the system would be satisfied with protocol number P-1
(or P-2) ?
4.Can you send me a newer version of the PCMCIA library via the
Internet ?
Or something else such that the newer version is not required ?
Regards, Hans Diel
=======================================================================
In <961217120721_641458515@emout01.mail.aol.com>, on 12/17/96
at 12:07 PM, GWRepNate@aol.com said:
>In a message dated 96-12-17 11:37:59 EST,
>diel@intbuso.boeblingen.netsurf.de writes:
>> Nathan, as I send you the previous urgent message, I think I should inf
>> you on my newest findings. My PCMCIA driver (as any PCMCIA driver) need
>> the PCMCIA library. When GEOS attempts to load my driver, it first
>> attempts to load the PCMCIA library. A few hours ago, I got suspicious
>> that the problem GEOS seems to have with my driver is in fact a problem
>> has with its PCMCIA library. So I removed all references to the PCMCIA
>> library from my device driver and tried a again the GeodeUseDriver() fo
>> my driver.
>> It worked successfully !!!!
> Great!
>> This leads to new and modified questions (i.e. you may ignore my previo
>> note):
>>
>> 1. Isn't it possible to get more detailed possible causes for the retu
>code
>> GLE_LIBRARY_PROTOCOL_ERROR for the case where an indirectly
>> required library is the source of the problem ?
> See below for explanation.
>> - what is the exact condition being violated ?
> The library you require is newer than the one on the system. In other
>words, you're asking for a library with a higher protocol number than the
>one on the system. GEOS does this checking because newer
>drivers/libraries might have functions that your geode requires. If you
>can't get the version of the driver/library you need then it's possible
>your geode would crash trying to use an older version.
>> - which two protocol numbers are compared (if at all) ?
>> (PCMCIA library with device driver, or with the system, or wit
>the
>> application)
> The protocol number of the library you want (specified in the file
>header of the .geo file) and the protocol number of the library on the
>system (stored in it's file header).
>> 2. Is it possible for me to change the protocol number of the PCMCIA
>> library ? I experimented already, and found out that I'm able to
>generate
>> a .REV file for the PCMCIA library, but I rather ask you before I
>> may damage something.
> This requires modifying the .geo file of the library on the target
>system. This is not a solution to the problem. It sounds like you need to
>get a more recent version of the library and put it in the emulator
>system. Which library are you using? What is the time/date stamp of the
>.geo on your target system? Is there a more recent version on the SDK
>CD-ROM that you could use instead?
>> 3. Do you have any idea what a reasonable protocol number would be ?
>> (assuming that the protocol number is the source of the problem)
> See previous answer as to why this isn't the solution you want.
>> 4. Is it (a) necessary and (b) possible for me to reset the protocol
>number
>> of my device driver after having it increased to 12 ?
> Yes, delete the .rev file and all non-source files (e.g. .ec, .nc,
>.ebj, .obj, .rsc, .geo, .sym). Then run grev again to get the protocol
>number you want, then recompile your geode.
>> 5. What can I expect when I move to the real Omnigo ? (So far I'm sti
>> with the emulator).
>> Are the protocol numbers of the Omnigo Simulator and that of the r
>> Omnigo identical ?
> I believe the file set is identical. If you need to replace any of the
>system geodes on the emulator, you will also need to replace them on the
>OmniGo itself. This is simple to do: When packaging your geode using
>Shipper, simply include the up-to-date library your geode requires in the
>package, making sure to specify the correct target directory (e.g.
>\GEOWORKS\SYSTEM\PCMCIA). When the end-user runs Installer to install
>your package onto their OmniGo, the new library will be written to RAM.
>If you reboot GEOS on the OmniGo, it should seek out the new version of
>the library and use that, rather than the one stored in ROM. Rebooting
>may not be necessary, but it will make GEOS use the new version of the
>library for certain.
>Nathan
-- ----------------------------------------------------------- diel@intbuso.boeblingen.netsurf.de -----------------------------------------------------------