Re: PilOS
Thanks for the boost, Alex. I'll do some work on my own now, and get back to you. I am going to try more qemu versions, then I am going to try modifying or rewriting the bios file in qemu to see if I can bypass this limit. I guess it is trying to emulate the x86-64 architecture to the bit, so maybe as a vm the 64kb limit is not needed? Another thought I had was designing my own hardware in the vm along the lines of PilMCU. I am by no means qualified to do so (yet!), but that's the fun isn't it? 64bit is the kicker, since I have some 32 bit boards lying around, and an FPGA proto board. Rob On Mon, Jul 20, 2015 at 9:26 PM, Alexander Burger a...@software-lab.de wrote: On Mon, Jul 20, 2015 at 08:30:01PM +0800, Robert Herman wrote: Is there a way to change a qemu bios file config? The man page of qemu-system says QEMU uses the PC BIOS from the Seabios project and the Plex86/Bochs LGPL VGA BIOS. But there is also a -bios file option. I haven't tried. Could I change beg.l to load it in segments, or would it still require a 670kb read to put it together again? This is surely possible, but quite tedious. You would have to modify the 'DAP' structure (starting at line 87) for varying Start sectors, Offsets and smaller Number of sectors values, and call int 13h repeatedly. So you could read it all in e.g. 11 pieces, each = 64 KiB. Perhaps not worth the effort ... ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
BIOS limitations
This link mentions extended read. Could this be relevant to read blocks larger than 32 or 64 kbytes? https://stackoverflow.com/questions/856050/how-to-load-kernel-into-memory-from-cd-rom-using-assembly-nasm -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PilOS
Hi Rob, I'm using qemu-2.0.9.1 on win64 with pilos and it works fine I downloaded it from here: http://qemu.weilnetz.de/w64/qemu-w64-setup-20140715.exe Later versions, including qemu-w64-setup-20150503.exe did not run for me Hope that helps On Mon, Jul 20, 2015 at 6:10 AM, Robert Herman rpjher...@gmail.com wrote: I tried several, and when I finally tried version 2.2.90 for windows 64 bit, It went past that error and went to a 'READ ERROR 09' Is that a 09h Attempt to DMA over 64kb boundary using the same Wiki reference you supplied in a previous posting? How can I fix it or keep moving on? Where do I look in the source to troubleshoot this myself? Exciting fun anyhow, so no complaints here! Rob On Mon, Jul 20, 2015 at 1:32 PM, Alexander Burger a...@software-lab.de wrote: Hi Robert, First, I would like to donate some money anyway, seeing how much fun I have had with PicoLisp and PilOS. Thanks, that's very nice! But don't worry, that's not what I'm looking for. I need some stable, long-term project(s) ;) Second, I get a 'Guest has not initialized the display (yet).' when trying to run PilOS in qemu on my i5 Windows 8.1 64bit machine. Any steps I am missing? I am a qemu newbie, and PilOS newbie. I did a short search on the web, and it seems this error appears in qemu in other situations too. Not only on Windows, but also on other guest operating systems. I have no idea what might be the reason. PilOS simply uses the standard VIDEO memory (VGA) on hardware address 0xB8000. Can you try another version of qemu? ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: BIOS limitations
On Tue, Jul 21, 2015 at 07:25:52AM -, jakob wrote: This link mentions extended read. Could this be relevant to read blocks That's what we are talking about all the time. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PilOS
On Tue, Jul 21, 2015 at 03:26:03PM +0800, Robert Herman wrote: Thanks for the boost, Alex. I'll do some work on my own now, and get back to you. I am going to try more qemu versions, then I am going to try modifying or rewriting the bios file in qemu to see if I can bypass this limit. Yes, but still strange why qemu differs so much. I never had any problem, and, it seems, other people too. I guess it is trying to emulate the x86-64 architecture to the bit, so maybe as a vm the 64kb limit is not needed? If the error diagnosis is correct, it is only the DMA transfer by this special BIOS which is limited to 64 KiB. And - I suspect - if it fails so early, the following code will give problems too ;) ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
