Hi ... & my first problems

Good morning! :)

By pure chance I found this project, and was very interested.
So I downloaded some files yesterday, and wanted to give it a try today.

I'm running an Asus A7V8X Board, with an AMD 2200+ processor using W2k
SP4, and so I downloaded QemuInstall-0.6.0.exe plus some images.
After installing qemu, and unpacking those images as descibed on the
website, I wanted to start reactos - so I opened an command line, went
to qemu's directory, and typed-in:
qemu reactos-0.2.3.img
... it seems an window opend for a short part of a second, that's all.
Trying other images (freedos, netbsd, openbsd) gave the same result -
even with modified start parameters ...

Later on I upgraded to another qemu version (QemuInstall-20040730.exe &
QemuInstall-20040801.exe), but the results are the same: no image can be
started ...

Is there something wrong I'm doing?

Thanks in advance!

c y
Torsten

Re: Hi ... & my first problems

Le Sun, 01 Aug 2004 12:51:24 +0200, Torsten E. a écrit :

> Good morning! :)
> 
> By pure chance I found this project, and was very interested. So I
> downloaded some files yesterday, and wanted to give it a try today.
> 
> I'm running an Asus A7V8X Board, with an AMD 2200+ processor using W2k
> SP4, and so I downloaded QemuInstall-0.6.0.exe plus some images. After
> installing qemu, and unpacking those images as descibed on the website, I
> wanted to start reactos - so I opened an command line, went to qemu's
> directory, and typed-in:
> qemu reactos-0.2.3.img
[...]
> Is there something wrong I'm doing?

Try to add at least the path to the bios in the command:
when in qemu directory: qemu.exe -L . reactos-0.2.3.img

Re: Re: Hi ... & my first problems

Ronald schrieb am Sonntag, 1. August 2004 17:09:

> Le Sun, 01 Aug 2004 12:51:24 +0200, Torsten E. a écrit :
>
>> Good morning! :)
>>
>> By pure chance I found this project, and was very interested. So I
>> downloaded some files yesterday, and wanted to give it a try today.
>>
>> I'm running an Asus A7V8X Board, with an AMD 2200+ processor using
>> W2k SP4, and so I downloaded QemuInstall-0.6.0.exe plus some images.
>> After installing qemu, and unpacking those images as descibed on the
>> website, I wanted to start reactos - so I opened an command line,
>> went to qemu's directory, and typed-in:
>> qemu reactos-0.2.3.img
> [...]
>> Is there something wrong I'm doing?
>
> Try to add at least the path to the bios in the command:
> when in qemu directory: qemu.exe -L . reactos-0.2.3.img

Ah ... THANKS!
Now it works fine - I simply did what the website
(http://www.freeoszoo.org/download.php) said:
[quote]
 Microsoft Windows: qemu.exe -hda guest_image_name.img -boot c -user-net
[/quote]
and Section 3.2 Quick Start (of the user guide):
[quote]
 Download and uncompress the linux image (`linux.img') and type

QEMU Menu for Windows

Attached is a batchfile that creates a simple numbered menu for
running QEMU images under Windows:

Here is an example of the output:
=== QEMU Menu 1.0 ===
  QEMU (C) 2004 Fabrice Bellard
  QEMU Windows Port by kazu?
  QEMU Menu (C) 2004 Garth Dahlstrom (ironstorm <at> users.sf.net)

Type the image number and hit enter to start QEMU:

[1] linux
[2] reactos-0.2.3
[3] freedos
[4] netbsd_1.6.2

[Q] to Quit

Enter your choice now

--

-- 
Northern.CA ===--
http://www.northern.ca/
Canada's Search Engine

 <at> echo off 
REM QEMU menu (C)2004 by Garth Dahlstrom (ironstorm <at> users.sf.net) 
REM Licensed under GNU GPL (like it would work without the source anyway... :) )

Best way to get 6GB = 3 x 2GB + soft raid?

I'm thinking of trying to roll an image of the OE development
toolchain (for Zaurus), to do so I'll need to create a linux system
with approximately 6GB of space...

Reading through the readme that comes with QEMU for Windows 0.60, it
suggests that an image can be a max of 2GB...

Assuming this limitation is valid, I'm guessing my best bet is to soft
raid0?/jbod?/lvm? of 3 x 2GB image files together for hda, hdb & hdc
...

I'm looking for feed back and suggestions on whether: I'm crazy/there
is an easier way/a better overall approach...

Cheers,

-Garth

--

-- 
Northern.CA ===--
http://www.northern.ca/
Canada's Search Engine

Re: Best way to get 6GB = 3 x 2GB + soft raid?

Le Sun, 01 Aug 2004 12:17:22 -0400, Garth Dahlstrom a écrit :

> I'm thinking of trying to roll an image of the OE development toolchain
> (for Zaurus), to do so I'll need to create a linux system with
> approximately 6GB of space...
> 
> Reading through the readme that comes with QEMU for Windows 0.60, it
> suggests that an image can be a max of 2GB...
> 
> Assuming this limitation is valid, I'm guessing my best bet is to soft
> raid0?/jbod?/lvm? of 3 x 2GB image files together for hda, hdb & hdc ...
> 
> I'm looking for feed back and suggestions on whether: I'm crazy/there is
> an easier way/a better overall approach...
> 
> Cheers,
> 
> -Garth

This is the mkqemuimage utility that is limited to 2G image creation.
The next limitation could be your file system if you are using fat
with an old windows that is 4G, don't know about ntfs.
Hope this help in some way.
Oh! and what about the file name QemuMenu.bat (8+3) for your previously
posted batch file.  

[patch] Arm arch5 support

The attached patch adds qemu target support for the new arm instructions 
present in the armv5e instruction set.

I'm probably going to look at adding thumb support next, time permitting.

Paul

_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: OS Support Table additions

Le 07/31/2004 09:51 PM,  Frederic Bezies a écrit :

> Le 07/31/2004 09:06 PM,  Frederic Bezies a écrit :
> 
> [...]
> 
>> I will see and tell :)
> 
> 
> Cannot create bootable CD :|

And the problem is still there with BeOS Max 3.1 beta 1...

And I don't have any blank cd to spare with this, as I prefer - and from 
far - working with iso ;)

> 
> So, I can't say for support...
> 

So... ;)

--

-- 
Frédéric Béziès - mozjf <at> alussinan.org

"Le patriotisme c'est l'amour des siens,
Le nationalisme c'est la haine des autres." (R.Gary)

Re: [patch] Arm arch5 support

Hi Paul,

On Sun, Aug 01, 2004 at 06:08:17PM +0100, Paul Brook wrote:

> The attached patch adds qemu target support for the new arm instructions 
> present in the armv5e instruction set.

Have you actually succeeded in getting ARM binaries to run?  I just
get this all the time (this is with your patch, but I get the same
effect without it):

phi% armv5te-redhat-linux-gcc -Wall -o hi hi.c -static
phi% /tmp/qemu/bin/qemu-arm ./hi
qemu: uncaught target signal 11 (Segmentation fault) - exiting
phi%

The binaries generated with this toolchain run fine on a PXA25x, and
with -mbig-endian they run fine on an Intel IXP2400.

cheers,
Lennert

Re: [patch] Arm arch5 support

On Sunday 01 August 2004 18:41, Lennert Buytenhek wrote:
> Hi Paul,
>
> On Sun, Aug 01, 2004 at 06:08:17PM +0100, Paul Brook wrote:
> > The attached patch adds qemu target support for the new arm instructions
> > present in the armv5e instruction set.
>
> Have you actually succeeded in getting ARM binaries to run?  I just
> get this all the time (this is with your patch, but I get the same
> effect without it):

I've only run some test assembly code inside an armv4 binary.

> phi% armv5te-redhat-linux-gcc -Wall -o hi hi.c -static
> phi% /tmp/qemu/bin/qemu-arm ./hi
> qemu: uncaught target signal 11 (Segmentation fault) - exiting
> phi%
>
> The binaries generated with this toolchain run fine on a PXA25x, and
> with -mbig-endian they run fine on an Intel IXP2400.

Code for "t" variants (maybe all armv5 targets) probably uses the bx thumb 
interworking instruction, which isn't implemented yet.

Paul