>Sorry, my fingers wasn't syncronized with my brain. What I meant was:
>
>So we are back to the usual problem, where in the 640kB..1024kB range should
>we
>put or own EPROM.
Somewhere free from C8000 to F.
>The code Christian has contributed does just this, though I have not yet
>been able to get it to work as I am still tracking down a network card that
>will take a 64K ROM. I have the plans for a flashcard, but have not yet
>been able to get thte parts to build one.
I've seen some NE2000 clones t
Stefan Pettersson writes:
>
> On 13-Nov-99 David Murn wrote:
> > On Sat, 13 Nov 1999, Stefan Pettersson wrote:
> >
> >> So we are back to the usual problem, where in the 640 kB should we put
> >> or own EPROM.
>
> Sorry, my fingers wasn't syncronized with my brain. What I meant was:
>
> So we
On 13-Nov-99 David Murn wrote:
> On Sat, 13 Nov 1999, Stefan Pettersson wrote:
>
>> So we are back to the usual problem, where in the 640 kB should we put
>> or own EPROM.
Sorry, my fingers wasn't syncronized with my brain. What I meant was:
So we are back to the usual problem, where in the 640
>Whats the speed of microwindows like at the mo? any faster?
It takes approx. a minute to load insanely strange pages like www.vg.no.
But that is because it does a LOT of resizing during loading.
This forces nano-x to refresh the whole screen and that takes a few seconds.
>Has it made it to th
On Sat, 13 Nov 1999, Greg Haerr wrote:
> I'm happy to announce that I've just heard that Opera Software has
> just ported their fully functional web browser to Microwindows!
> They have sent me a screen shot, which I will post. The port
> uses the Nano-X API, and runs in client/server mod
On Sun, 14 Nov 1999, Alistair Riddoch wrote:
> I am slightly confused about the int 19h issue however. If cassette BASIC
> uses this mechanism, but is not envoked until Floppy and HDD boot have
> failed, is this what we want?
INT 19 points to a code block which tries to search for the drives the
David Murn writes:
>
> On Sat, 13 Nov 1999, Blaz Antonic wrote:
>
> > All you have to do is to insure your ROM image uses correct format
> > (utils in netboot package create correct images from executable
> > binaries) and BIOS will do the rest of the job
>
> Actually, 'format' simply means 0x5
