Re: Microwindows runs on X11
On Sat, 13 Nov 1999, Greg Haerr wrote: > I will be including these additions in the next cut, as well as getting > a CVS repository up. Thanks for the contributions, this project > seems to be gaining momentum... I think this is probably a good time to announce that I am resigning my role in the NanoGUI project and handing it on to Greg. Greg has been pretty much coordinating the project on his own for the past few months anyway, and has proven himself easily capable of the job. The mailing list will continue to reside on linuxhacker.org, and ftp.linuxhacker.org will continue to mirror the the ftp repository (and the contents of the ftp area are also accessible via http at the same URL), however the official website will be moving to either microwindows.censoft.com or www.nanogui.org depending on the outcome of negotiations between Greg and I, and Stormix who have registered the nanogui.org and nanogui.net domain names. Similarly, the CVS area will be moving to either cvs.nanogui.org or another repository at Greg's discretion. I would like to take this oppurtunity to wish Greg good luck in his new role as manager of the NanoGUI project; good luck Greg! --- Linux- the choice of a GNU generation. -- : Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham : http://www.linuxhacker.org/
Re: Linux on 486 without fdd/hdd
> Hi there, > > Sorry to bother you again. > Is it possible to run a browser on linux running on 286 or lower cpu m/c? > Can I connect CDROM drives to those m/cs. For the record, I used a CDROM with my 286 with no problem, I used a SoundBlaster cd drive, but IDE and SCSI should work fine as well. There is really little reason to have a CDROM on a 286 though :) At this point, I don't know that any browsers are ported...even Lynx. And if there was, there's no networking yet, so you'd only be browsing local files. If you still interested, I'm sure someone else on the list can point you towards more information. Dan
Microwindows runs on X11
A big thanks to Tony Rogvall for writing Microwindows mouse, screen and keyboard drivers for X11. This means that X11 users can now develop Microwindows applications from within the X environment, running them as another X Window. Currently the size of the Microwindows application window is compile-time fixed, but it might be nice to allow it to be dynamically sized. Also big thanks to Martin Jolicoeur for contributing Makefile and build enhancements including a ./configure program and graphical make xconfig, as well as changes for StrongARM cross-compilation. I will be including these additions in the next cut, as well as getting a CVS repository up. Thanks for the contributions, this project seems to be gaining momentum... Greg
Web browser ported to Microwindows
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 mode. Full color support, palette mapping, jpeg and gif image and font support is working, as well as transparent images. It actually works! I will be rearchitecting the client/server networking code shortly, as the browser is running a bit slower than it should. I'm sure this is because of the extreme handshaking occuring for each parameter, which causes excessive context switches for any i/o. The total size of the browser codefile is 667k, much, much smaller than most web browsers. This means that it's possible that Opera could port the software to any of the newer palmtop or LinuxCE [MIPS, StrongARM or SH3] devices for browser access, since Microwindows now runs on these processors. For more information on Opera Software, see www.opera.com. Greg
Re: Linux on 486 without fdd/hdd
On Sat, 13 Nov 1999, Alan Cox wrote: > > In my proposed setup I don't have hdd/fdd. I am just having CDROM drive > > and 16MB RAM, 486 PC. I am interested in booting linux from CDROM and run > > a browser like Netscape from the same CD. > > Wrong list. This list is for Linux on 286 or lower CPU machines > > Alan Hi there, Sorry to bother you again. Is it possible to run a browser on linux running on 286 or lower cpu m/c? Can I connect CDROM drives to those m/cs. OR Pl. suggest me a mailing list for my problem. Thanks in advance. Jitendra.
Re: Linux on 486 without fdd/hdd
> In my proposed setup I don't have hdd/fdd. I am just having CDROM drive > and 16MB RAM, 486 PC. I am interested in booting linux from CDROM and run > a browser like Netscape from the same CD. Wrong list. This list is for Linux on 286 or lower CPU machines Alan
Linux on 486 without fdd/hdd
Hi there, I am a student and working on Linux related project. In my proposed setup I don't have hdd/fdd. I am just having CDROM drive and 16MB RAM, 486 PC. I am interested in booting linux from CDROM and run a browser like Netscape from the same CD. Pl. comment on this and would be delighted to receive few tips. (Pl. note I am not interested in network booting option for some reason.) Thanks in advance, Jitendra.
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
>Actually, 'format' simply means 0x55aa at the start of the image, and the >3rd byte contains the number of 256 byte pages in the ROM. Nothing else >is involved in the 'format'. 0x55aa number of 256 word = 512 byte pages entry point, entered with long jump and cs = segment of ROM All the bytes in the image must checksum to 0.
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
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 0x55aa at the start of the image, and the 3rd byte contains the number of 256 byte pages in the ROM. Nothing else is involved in the 'format'. > it will detect the ROM fetch its size and start address and start > executing code from it. It is up to you (ROM) to return control to BIOS > (and let it boot normaly) or execute kernel and boot into your OS > (that's the way you want it if you imaplnt a ROM inthere). I'd suggest that you don't do it this way, and that you actually hook interrupt 0x19. This allows BIOS to detect various hardware, and call any other important ROMs, such as video and disk controller. While you (in theory) can boot directly from the ROM, ELKS won't like you much. Apart from anything else, quite a few drivers, notably the disk and console drivers generally use BIOS calls. Davey
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
> This is unverified, but > I think the Basic-hook is still there, untouched. > But some of the EPROM area reserved for Basic has been used for the setup > subprograms. > So we are back to the usual problem, where in the 640 kB should we put or own > EPROM. Nowhere. There is a memory area meant for ROMs above 640 KB. It is called UMB. That's where VGA BIOS, Network card boot ROM, special (SCSI and alike) adapter BIOS ROMs are. 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 - it will detect the ROM, fetch its size and start address and start executing code from it. It is up to you (ROM) to return control to BIOS (and let it boot normaly) or execute kernel and boot into your OS (that's the way you want it if you imaplnt a ROM inthere). bye, Ab
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
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. On x86 you've got 20 address lines, this is 0-1mb. What do you think the space is reserved for from 640k-1024k? ROMs. When the system boots, it will probe various address, in 2k blocks, from c800:0 to f400:0, looking for a ROM. So basically, stick your ROM anywhere in that range that isn't otherwise used. Davey
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
BTW, neither BIOS nor cassette ROM map to low memory--BIOS starts in the 0E range for PS2s, 0F for normal ATs, cassette Basic having a start of about 0F6000. This might provide some interesting consequences, as the Linux Kernel maps BIOS with all zeros, the BIOS being unnecessary to the kernel after the BIOS hands off to the kernel. So, concievably, Linux COULD remap memory mapped anywhere on bootup to int 18h cassette BASIC. DOS even used to do this--the Compaqs never had the ROMs, but still could use BASICA (which made an int 18h call) by using a specialized diskette that had an image that would be software mounted to 0F6000-ish. AFAIK nobody's ever touched int 18h, so it seems possible that anything mapped to 0F6000 for whatever reason should be still executed on an int 18h, even in a SMP PIII (this is an old enough legacy that AMD/Cyrix should use it as well, but this is PURE speculation on my part). This should work even for software mapping, as evidened by the Compaq behavior (BTW the reason I use Compaq as an example is that was my first PC-type computer, in 1985--I only found out why we had to use the special BASIC diskette in my recent studies of XT ROMS, though...). On Sat, 13 Nov 1999, Stefan Pettersson wrote: > On 12-Nov-99 Sam Steele wrote: > > My PCjr has a BASIC ROM (a slightly modified version that shows off > > the "advanced grahpics/sound" of the PCjr when you hit escape as soon > > as it starts), and when booted without a harddrive, my AMIBIOS based > > K5 says "NO ROM BASIC", so I don't know if the BASIC call has been > > replaced with the BIOS setup > > This is unverified, but > I think the Basic-hook is still there, untouched. > But some of the EPROM area reserved for Basic has been used for the setup > subprograms. > So we are back to the usual problem, where in the 640 kB should we put or own > EPROM. > > > -- > Stefan Pettersson Voice +46-70-5933800 Kanard AB > [EMAIL PROTECTED] ([EMAIL PROTECTED]) Fax +46-221-50180 Vretberga > finger [EMAIL PROTECTED] for my public key S-732 96 ARBOGA > > "What a scary world it must be, for those with no UID:GID" /OZ9ABN > The Internet must be a medium for it is neither Rare nor Well done! mailto:[EMAIL PROTECTED]">John Galt
