On Tue, May 5, 2009 at 5:24 PM, Eric Auer <[email protected]> wrote:
>
> Jeremy,
>
>>> I could not find any LOAD*.* file in the zip, though... Maybe
>>> this whole experiment is something different than IBID meant?
>
>> See http://www.seasip.info/Gem/gemxm.html   (I'm not sure if its the
>> same/newer/older than the one from the OpenGEM site)
>> This version of GEM/XM includes the changes to use handles instead of
>> FCB, so its load.a86 source (the module that did use FCBs) probably
>> doesn't help much.
>
> As said - source or no source, things just work for me!
> If nothing is broken, I cannot fix anything :-) So what
> exactly do I have to do to "use LOAD" and "make it use

load is simply a module (object file without source) in GEM that [and
this confused me at first until I installed GEM and it created it as I
thought it referred to the DOS command or replacement device driver]
loads a configuration (text) file called ASSIGN.SYS which simply
contains a list of drivers for GEM (similar to CONFIG.SYS, WIN.INI and
all).

> FCB in a way that fails"? If only ancient versions use

you have to use a version that is old enough to not be updated to use
handles, I know of no other way to express this, the latest GEM/XM
versions are fixed and all versions from GEM 3 on (including the
FREEGEM variants) I believe all use file handles, so you have to
install and try to run an older release (available in the SDK
mentioned above, I believe the kernel is fixed now, tested with the
2.2U release of GEM).

> any FCB at all and newer use handles anyway, why bother?

so other programs that only use FCBs will work, not that I know of any ... :-)

>
>> From what I remember reading, GEM v2 and XM in the load
>> module uses FCBs to access information from the assign driver.
>
> It would help to know who and why and how loads that "assign".
>
>> The next step is to figure out what FCB calls GEM v2/XM make and
>> then determine what the FD kernel is doing with those requests.
>
> I can only repeat - it works for me, how can I debug it then?
>
> Eric
>

FYI: GEM issues FCB getfilesize, open, followed by random read calls
for ASSIGN.SYS when loading.
the problem was with our FCB read function, it was returning 0 bytes of data

For those who want to test the fix a compiled kernel (1line patch
committed to SVN already)
http://www.fdos.org/kernel/test/KERNEL.2038RC.SYS

Thanks,
Jeremy

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Freedos-kernel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to