[Qemu-devel] CDROM /Network with Win98

[Qemu-devel] CDROM /Network with Win98

[Emmanuel Charpentier]

Setup : Debian unstable + QEMU 0.5.2-4 as packaged in Debian ...

I seem to be unable to install correctly Win98/Win98SE with cd access. I 
tried repeatedly to install either of them (from a CDROM, of course ...) : 
the first pass is OK (and impressively fast, for an emulation ...). During 
the second phase, Windows complains of being unable to allocate itself 
enough memory for Plug'Play device detection. I have to restart this phase. 
Thie third and fourth phase seem okay, and I can boot Win98, but I have no 
network device and no hard disk.

How can I get rid of these inconveniences ?

I install with :

charpent@yod:~/qemu-w2000$ qemu -hda w2000.cow  -cdrom /dev/cdrom -boot d 
-m 256

The ntext phases are started with -boot c instead of -boot a

Any ideas ?

					Emmanuel Charpentier

PS : Any idea on how to install Win2K ? I have a non-bootable CD, which can 
be either used from Win98 or with 4 diskettes to boot. Both methods work on 
real hardware, but I can't use either of them with QEMU. Ideas ?

PPS : I'm not on the list, and I'm reading it throug the archives. Could 
you please Cc me ?

Re: [Qemu-devel] CDROM /Network with Win98

[Hetz Ben Hamo]

Hi,

> Setup : Debian unstable + QEMU 0.5.2-4 as packaged in Debian ...

At the moment I would recommend to use the CVS version. 0.5.2 is already 
obsolete..
 
> I seem to be unable to install correctly Win98/Win98SE with cd 
> access. I tried repeatedly to install either of them (from a CDROM,
>  of course ...) : the first pass is OK (and impressively fast, for 
> an emulation ...). During the second phase, Windows complains of 
> being unable to allocate itself enough memory for Plug'Play device 
> detection. I have to restart this phase. Thie third and fourth phase 
> seem okay, and I can boot Win98, but I have no network device and no 
> hard disk.

> PS : Any idea on how to install Win2K ? I have a non-bootable CD,
>  which can be either used from Win98 or with 4 diskettes to boot. 
> Both methods work on real hardware, but I can't use either of them 
> with QEMU. Ideas ?

You can convert those 4 floppies to images, and then use the monitor prompt 
to swtich between the floppy images I guess. Never tried it though...
 
> PPS : I'm not on the list, and I'm reading it throug the archives. 
> Could you please Cc me ?

You're more then welcome to subscribe, it's fun place here ;)

Thanks,
Hetz

Re: [Qemu-devel] CDROM /Network with Win98

[Emmanuel Charpentier]

Hetz Ben Hamo wrote:
> Hi,
> 
> 
>>Setup : Debian unstable + QEMU 0.5.2-4 as packaged in Debian ...
> 
> 
> At the moment I would recommend to use the CVS version. 0.5.2 is already 
> obsolete..

I tried that. Same result by different ways : the 2nd stage detection of 
Plugn'Pray harware seems to pass OK, but the emulated system freezes (no 
more mouse moves) during detection of non-PnP hardware. You have to 
"reboot" (stop the emulator and restart it), and end up with a system 
without CDRom or NNIC. The same thing happens when trying to add them with 
the damn "New Hardware Assistant" of the Cotnrol Panel. ...

[ ... ]

>>PS : Any idea on how to install Win2K ? I have a non-bootable CD,
>> which can be either used from Win98 or with 4 diskettes to boot. 
>>Both methods work on real hardware, but I can't use either of them 
>>with QEMU. Ideas ?
> 
> 
> You can convert those 4 floppies to images, and then use the monitor prompt 
> to swtich between the floppy images I guess. Never tried it though...

I have been able to use an image of the first floppy to boot, but I'm at 
loss about how to switch between images during the process. How do you do 
that ?

>>PPS : I'm not on the list, and I'm reading it throug the archives. 
>>Could you please Cc me ?
> 
> 
> You're more then welcome to subscribe, it's fun place here ;)

I'm already reading my share of lists (plus the @#[!! spams ...). 
Furthermore, I found that perusing the lists archive is a nice way not to 
bother people with tooFAQ's

					Emmanuel Charpentier

Re: [Qemu-devel] CDROM /Network with Win98

[Jim C. Brown]

On Mon, May 03, 2004 at 12:32:53AM +0200, Emmanuel Charpentier wrote:
> Hetz Ben Hamo wrote:
> >Hi,
> >
> >
> >>Setup : Debian unstable + QEMU 0.5.2-4 as packaged in Debian ...
> >
> >
> >At the moment I would recommend to use the CVS version. 0.5.2 is already 
> >obsolete..
> 
> I tried that. Same result by different ways : the 2nd stage detection of 
> Plugn'Pray harware seems to pass OK, but the emulated system freezes (no 
> more mouse moves) during detection of non-PnP hardware. You have to 
> "reboot" (stop the emulator and restart it), and end up with a system 
> without CDRom or NNIC. The same thing happens when trying to add them with 
> the damn "New Hardware Assistant" of the Cotnrol Panel. ...

You can't. In Win98SE, non-PnP hardware detection will consistently cause a
lock up. I had to say "No, I'll select the hardware from a list" option
to install the ne2000 and the svga drivers. For the cdrom, I used config.sys
and autoexec.bat to load the DOS driver, and that works.

> 
> [ ... ]
> 
> >>PS : Any idea on how to install Win2K ? I have a non-bootable CD,
> >>which can be either used from Win98 or with 4 diskettes to boot. 
> >>Both methods work on real hardware, but I can't use either of them 
> >>with QEMU. Ideas ?

You're lucky. I have a pre-installed win2k on a hard disk, but I have no
CD for it. I made a disk image, and qemu fails reliably with a disk read error.
Using the raw hard disk itself (via device file) fails as well, even when using
a fake geometry (as suggested by bochs, btw the disk image actually works for
bochs). I can copy the files from the disk image to a freshly made one, and that
works, but it won't boot because I haven't figured out how to write the boot
sector out yet.

> >
> >
> >You can convert those 4 floppies to images, and then use the monitor 
> >prompt to swtich between the floppy images I guess. Never tried it 
> >though...
> 
> I have been able to use an image of the first floppy to boot, but I'm at 
> loss about how to switch between images during the process. How do you do 
> that ?

This only works for qemu-0.5.3 and above. In the qemu monitor window,
type "change fda imageX" where imageX is the filename of the floppy
you want to change to. Use "eject imageX" when you are done (I'm not
sure if this is stricly necessary but it doesn't hurt).

For qemu-0.5.2, you'll have to use this old trick (from bochs):

You have 4 floppy images:

fd1
fd2
fd3
fd4

type this:

cp fd1 qfloppy

run qemu as such:

qemu -fda qfloppy [rest of qemu parameters here]

when you are done with the first floppy, change via:

cp fd2 qfloppy

continue for each floppy until you are done. I haven't tried this so you might
have mixed results, but in theory it should work... if it doesn't, then upgrade.
:)

> 
> >>PPS : I'm not on the list, and I'm reading it throug the archives. 
> >>Could you please Cc me ?
> >
> >
> >You're more then welcome to subscribe, it's fun place here ;)
> 
> I'm already reading my share of lists (plus the @#[!! spams ...). 
> Furthermore, I found that perusing the lists archive is a nice way not to 
> bother people with tooFAQ's
> 
> 					Emmanuel Charpentier
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

Re: [Qemu-devel] CDROM /Network with Win98

[J. Mayer]

On Mon, 2004-05-03 at 00:57, Jim C. Brown wrote:
 [ ... ]
> > >
> > >You can convert those 4 floppies to images, and then use the monitor 
> > >prompt to swtich between the floppy images I guess. Never tried it 
> > >though...
> > 
> > I have been able to use an image of the first floppy to boot, but I'm at 
> > loss about how to switch between images during the process. How do you do 
> > that ?
> 
> This only works for qemu-0.5.3 and above. In the qemu monitor window,
> type "change fda imageX" where imageX is the filename of the floppy
> you want to change to. Use "eject imageX" when you are done (I'm not
> sure if this is stricly necessary but it doesn't hurt).

eject isn't mandatory. Note that the syntax is "eject fda", not "eject
image". This is also useful for CDROMs.

> For qemu-0.5.2, you'll have to use this old trick (from bochs):
> 
> You have 4 floppy images:
[...]

> type this:
> 
> cp fd1 qfloppy
> 
> run qemu as such:
> 
> qemu -fda qfloppy [rest of qemu parameters here]
> 
> when you are done with the first floppy, change via:
> 
> cp fd2 qfloppy

This won't work as qemu doesn't release the first image until "eject" or
"change" command is used. So the first image will still be used after
you did overwrite it.

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

Re: [Qemu-devel] CDROM /Network with Win98

[David Sibai]

Hello,
I also had a nonbootable win2K CD and solved it by making a bootable CD out of 
my non bootable one.
Instructions available at http://old.bink.nu/xpbootcd/ 
(for xp, but it works just as well for 2K)
basically, just copy the files from your nonbootable win2k cd to your hd, then 
create a new iso out of it using the bootsector file provided at the url I 
gave.

David

On Monday 03 May 2004 00:32, Emmanuel Charpentier wrote:
> Hetz Ben Hamo wrote:
> > Hi,
> >
> >>Setup : Debian unstable + QEMU 0.5.2-4 as packaged in Debian ...
> >
> > At the moment I would recommend to use the CVS version. 0.5.2 is already
> > obsolete..
>
> I tried that. Same result by different ways : the 2nd stage detection of
> Plugn'Pray harware seems to pass OK, but the emulated system freezes (no
> more mouse moves) during detection of non-PnP hardware. You have to
> "reboot" (stop the emulator and restart it), and end up with a system
> without CDRom or NNIC. The same thing happens when trying to add them with
> the damn "New Hardware Assistant" of the Cotnrol Panel. ...
>
> [ ... ]
>
> >>PS : Any idea on how to install Win2K ? I have a non-bootable CD,
> >> which can be either used from Win98 or with 4 diskettes to boot.
> >>Both methods work on real hardware, but I can't use either of them
> >>with QEMU. Ideas ?
> >
> > You can convert those 4 floppies to images, and then use the monitor
> > prompt to swtich between the floppy images I guess. Never tried it
> > though...
>
> I have been able to use an image of the first floppy to boot, but I'm at
> loss about how to switch between images during the process. How do you do
> that ?
>
> >>PPS : I'm not on the list, and I'm reading it throug the archives.
> >>Could you please Cc me ?
> >
> > You're more then welcome to subscribe, it's fun place here ;)
>
> I'm already reading my share of lists (plus the @#[!! spams ...).
> Furthermore, I found that perusing the lists archive is a nice way not to
> bother people with tooFAQ's
>
> 					Emmanuel Charpentier
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

-- 
"We don't care.  We don't have to.  We're the Phone Company."

Re: [Qemu-devel] CDROM /Network with Win98 : summary of answers

[Emmanuel Charpentier]

Dear list,

A big thank to to all who responded ! You were all very helpful

A short sumary of what works and doesn't in your answers :

- Installation : you do need to copy the oakroom.sys driver, the mscdex.exe 
driver and to edit autoexec.bat and config.sys in order to get access to 
the cd.

- installing the network card : has to be done manually with the "new 
hardware" control panel utility. Seems to work.

- VGA : installing the SVGA driver doesn't give you much : you're still 
stuck with 640x480x16c. It's still horribly *S*L*O*W* ...

- sound : -enable-sound works (sort off) but you get lots of error messages 
  in the monitor and qemu eventually crashes.

Now for Win2K :

- copying (or symlinking) : doesn't work.

- switching the disks in the monitor : works (sort off), but the 2nd stage 
install doesn't finf*d the "hard disk.

- Installing Win98 then upgrading to W2K : works, but is highly tedious.

- creating a Win2KSP4 bootdisk (as desctibed in http://www.bink.nu/bootcd) 
: if you have access to a Win2K installation on native hardware, it works 
with the downloaded version of NERO. I tried to create a bootdisk with 
mkisofs/cdrecord, and failed (the bootrecord program doesn't find "NTLDR). 
This has probably links to the zillion options you have to set in Nero, 
some oif them having no equivalent in mkisofs (the ISO9660 charset is 
highly suspicious ...).

I have had various hurdles with Win2K installation and use, but I'l report 
them separately. I have to say that this installation is *impressive* : 
Win2k is actually usable (at least on fast hardware). A pity that MS 
Office, Openoffice or mozilla doesn't install (more on this later ...).

Again, thank you !

					Emmanuel Charpentier

PS : Again, could you please Cc me your possible answers : I'm not on the 
list and reading it through the archives ...

Re: [Qemu-devel] CDROM /Network with Win98 : summary of answers

[David Sibai]

Hi
> - creating a Win2KSP4 bootdisk (as desctibed in http://www.bink.nu/bootcd)
>
> : if you have access to a Win2K installation on native hardware, it works
>
> with the downloaded version of NERO. I tried to create a bootdisk with
> mkisofs/cdrecord, and failed (the bootrecord program doesn't find "NTLDR).
> This has probably links to the zillion options you have to set in Nero,
> some oif them having no equivalent in mkisofs (the ISO9660 charset is
> highly suspicious ...).
I also had the same problem when I first tried. Either you did not set 
emulation mode to "no emulation" or you did not read the right number of 
blocks(4) or did not set the proper  boot address (0x7c0). You can build the 
iso with mkisofs, since I did it. It is however easier with k3b.

David

[Qemu-devel] W2K minor and not so minor hurdles

[Emmanuel Charpentier]

Dear list,

Thank to your help, I have been able to attack the creation of a Win2K disk.

It essentially works. But I met some booboos and I'm currently fighting 
some issues. Since I don't know what the booboos meant, They might well be 
the cause of my current problems.

Setup : I made a Win2K SP4 boot disk starting with a W2K non-bootable disk 
and the instructions pointed at in a recent message 
(http://www.bink.nu/bootcd, iirc ...).

I've made various attempts with qemu-cow disks varying from 1 to 4 GB in 
size and memory allocations varying from none (no -m option) to 512 Mb. The 
  booboos and problems are fairly consistent and reproductible.

the first pass goes always OK : the disk is formatted (NTFS in all cases). 
The second pass starts well with a (lengthy) hardware detection phase, then 
a configuratioon phase (mostly national options for display, date/time, etc 
...). Afterwards, the system tells me that the list of options to be 
installed is too long, and that I should modify this list. Whatever I'm 
doing (suppressing all possible options, for example), I end up with the 
need to install 21 Mb of options with 0 Mb available on the disk. So I 
abort the installation ("q" in the monitor).

Restarting the very same installation  gives very curious results : the 
installer stards again, but the hardware detection phase seems much faster 
(sory, no hard data on this one, I didn't use a stopwatch ...) and the 
installation proceeds after the "national options" phase without further 
noise about a full disk. However, all is not rosy : during the "component 
installation", I have very consistently an error telling (backtranslated 
from French) :

The COM+ subcomponent has raised an exception during processing of the 
installatio program message.
OC_COMPLETE_INSTALLATION
.\csetuputil.cpp(line 3419)
Error code = 0x800703e6

Access to this memory address is invalid.
Library can't be loaded
C:\WINNT\system32\catsvr.dll


Before that, I may or may not get another error telling me "error loading 
catsvrutl.dll" : invalid memory access to this adress" (and no, no address 
is specified ...).

However, the installation proceeds and, lo, after another reboot, I get a 
(more or less, see below) functional W2K installation.

A booboo : I haven't yet be able to use an "-fda" floppy or floppy image. 
W2K tells me that the driver doesn't start, and no attempt has been able to 
revive it (deinstalling-reinstalling, booting all passes with a -fda 
option). Mistery ...

Another booboo is the video driver. Although the VBE drive is said to be 
able to go up to 1280x1024x32, I haven't be able to get more than 800x600x4 
(16 colors). I tried the BXVGA driver installer pointed at by some previous 
posts : this driver has two variant : the plain "BXVGA" version gave me 
black lines superimposed on the screen for about 2/3 to half its width, the 
second crashes the installation immediately after boot. Scratch one disk ...

More serious is the fact that I've been unable to install MS Office or 
mozilla. the MS Office 97 fails immediately after start, telling it can't 
read an ".sft" file (the very same disk installs perfectly on a native W2K 
installation ...). The mozilla installation fails after 3/4 of the 
installation, telling me that an error log is prepared (I've never been 
able to find it ...).

Any ideas ?

					Emmanuel Charpentier

PS : As usual, please Cc' me your answers, since I'm not on the list 
(reading it through the archives).

Re: [Qemu-devel] W2K minor and not so minor hurdles

[Joe Batt]

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

Though normally frowned upon.

me too.

- I gave up on the COW files and just use full dd'd disks to avoid the
out of disk space problems.
- Installing the FreeBE/AF driver causes my w2k image to exit (cleanly
mind you) during boot.

After doing a Microsoft update, the update site failed up update my
machine anymore.  That may be a license issue given that I was
attempting to multiple copies of w2k with the same license on one
machine concurrently.

Joe

On Wed, 2004-05-05 at 15:27, Emmanuel Charpentier wrote:
> Dear list,
> 
..very detailed report deleted...

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [Qemu-devel] W2K minor and not so minor hurdles

[Jason Gress]

On Wednesday 05 May 2004 03:27 pm, Emmanuel Charpentier wrote:
> Dear list,
>
> Thank to your help, I have been able to attack the creation of a Win2K
> disk.
>
> It essentially works. But I met some booboos and I'm currently fighting
> some issues. Since I don't know what the booboos meant, They might well be
> the cause of my current problems.
>
> Setup : I made a Win2K SP4 boot disk starting with a W2K non-bootable disk
> and the instructions pointed at in a recent message
> (http://www.bink.nu/bootcd, iirc ...).
You got farther than I with SP4.  My SP1 CD installs without problem, however.

>
> I've made various attempts with qemu-cow disks varying from 1 to 4 GB in
> size and memory allocations varying from none (no -m option) to 512 Mb. The
>   booboos and problems are fairly consistent and reproductible.
>
> the first pass goes always OK : the disk is formatted (NTFS in all cases).
> The second pass starts well with a (lengthy) hardware detection phase, then
> a configuratioon phase (mostly national options for display, date/time, etc
> ...). Afterwards, the system tells me that the list of options to be
> installed is too long, and that I should modify this list. Whatever I'm
> doing (suppressing all possible options, for example), I end up with the
> need to install 21 Mb of options with 0 Mb available on the disk. So I
> abort the installation ("q" in the monitor).
>
I'm not sure of this exactly, but I did notice that after my install on a 4GB 
image that every last byte was taken up by error logs in the C:
\WINNT\Security directory (if my memory serves).  Sorry if I didn't keep 
them.. if anyone would like to see them I can reinstall if you like.  After 
all, what's a couple of hours?  :P

> Restarting the very same installation  gives very curious results : the
> installer stards again, but the hardware detection phase seems much faster
> (sory, no hard data on this one, I didn't use a stopwatch ...) and the
> installation proceeds after the "national options" phase without further
> noise about a full disk. However, all is not rosy : during the "component
> installation", I have very consistently an error telling (backtranslated
> from French) :
>
> The COM+ subcomponent has raised an exception during processing of the
> installatio program message.
> OC_COMPLETE_INSTALLATION
> .\csetuputil.cpp(line 3419)
> Error code = 0x800703e6
>
> Access to this memory address is invalid.
> Library can't be loaded
> C:\WINNT\system32\catsvr.dll
>
>
> Before that, I may or may not get another error telling me "error loading
> catsvrutl.dll" : invalid memory access to this adress" (and no, no address
> is specified ...).
>
I'm not sure, but this may be related to the SP4 problems we all are having.  
When you right click on My Computer and go to properties, what service pack 
does it show you have installed?
> However, the installation proceeds and, lo, after another reboot, I get a
> (more or less, see below) functional W2K installation.
>
> A booboo : I haven't yet be able to use an "-fda" floppy or floppy image.
> W2K tells me that the driver doesn't start, and no attempt has been able to
> revive it (deinstalling-reinstalling, booting all passes with a -fda
> option). Mistery ...
From what I have read, I am not aware that floppy emulation works in Win2k 
yet.  Anyone care to confirm?
>
> Another booboo is the video driver. Although the VBE drive is said to be
> able to go up to 1280x1024x32, I haven't be able to get more than 800x600x4
> (16 colors). I tried the BXVGA driver installer pointed at by some previous
> posts : this driver has two variant : the plain "BXVGA" version gave me
> black lines superimposed on the screen for about 2/3 to half its width, the
> second crashes the installation immediately after boot. Scratch one disk
> ...
The video line problem is known; using 1024x768x16bit color with the BXVGA 
driver works well for me. :)

>
> More serious is the fact that I've been unable to install MS Office or
> mozilla. the MS Office 97 fails immediately after start, telling it can't
> read an ".sft" file (the very same disk installs perfectly on a native W2K
> installation ...). The mozilla installation fails after 3/4 of the
> installation, telling me that an error log is prepared (I've never been
> able to find it ...).
Haven't tried, sorry.  I don't actually own a copy of MS Office :O.  I noticed 
someone else have a problem installing Office as well.  Wish I could help 
there!

I did just successfully install (and test) Mozilla Firefox into my Win2k SP1.  
Which did you try, the full suite or just (the much better) Firefox?
>
> Any ideas ?
>
> 					Emmanuel Charpentier
>
> PS : As usual, please Cc' me your answers, since I'm not on the list
> (reading it through the archives).
>
Hope this helps! :)

	Jason Gress
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] W2K minor and not so minor hurdles

[Jean-Michel POURE]

Le mercredi 5 Mai 2004 23:36, Jason Gress a écrit :
> > Another booboo is the video driver. Although the VBE drive is said to be
> > able to go up to 1280x1024x32, I haven't be able to get more than
> > 800x600x4 (16 colors). I tried the BXVGA driver installer pointed at by
> > some previous posts : this driver has two variant : the plain "BXVGA"
> > version gave me black lines superimposed on the screen for about 2/3 to
> > half its width, the second crashes the installation immediately after
> > boot. Scratch one disk

From memory, BXVGA does not support 32 bits in all resolutions.