te_lanus wrote:

neozeed wrote:what is LBA?? Is it a mixmode CD?

Im pretty sure there is CD issues as we saw with the stock warp 3.0 install.

LBA = Little Big Adventure

Safe to say I've never heard of it. So is it mixed mode? Straight data? What makes it so special?

what is LBA?? Is it a mixmode CD?

Im pretty sure there is CD issues as we saw with the stock warp 3.0 install.

- neozeed: Install MS-DOS 6.0. I think that's the first version that introduced the /L: parameter. Edit: I just did what I did the last time I experienced a problem and... I somehow experience no problems now. Maybe that segment-related commit from Tom (http://retrosoftware.co.uk/hg/pcem/rev/1578e3...

Crap, I built both exe's as debug by mistake, I've updated the archive. Also I included the OpenAL32 runtime for people that don't have it.

My lh can't specify segments... so I loaded MSD into high memory. It's working fine. I need some more TSR's to load that I can verify work... I guess sidekick and some other crap.

And using a QuickWin variation of torture, I can allocate 22MB of ram, (VM has 16MB of ram, and 16MB of swap) with QuickC, Word 2.0 and Excel 3.0 running. It didn't crash... I'll leave it running some dir/s and dos mem torture for the heck of it. I don't think you can open HMA's to DOS BOXes in Wind...

found some UMB allocation stuff here: https://courses.engr.illinois.edu/ece390/books/artofasm/CH13/CH13-5.html and put together this amateur hour special... :lol: #include <stdio.h> #include <stdlib.h> #include <malloc.h> #include <memory.h> #include <dos.h> #define ELEMENTS 4096 #define BLOCK 4096 ...

I've never written or even patched a windows 3.x driver so I really don't know. I manually copied in the Windows 3.1 driver for the OAK OTI-067. The 256 colour modes don't work (havent tried on Windows 3.1, but the 800x600x8bit looks like it's not paging to the correct video page. as always I tested...

ppgrainbow wrote: Uh oh! That doesn't sound too good! Did Windows 3.0 in Standard and 386 Enhanced mode work with EMM386 driver disabled or did the problem persist?

To test video cards, I start out with only himem.sys ... Keep it simple see if the driver even works before messing with any of that HMA crap.

I just tried the Windows 3.0 drivers from the WINDOWS 3.0 SUPPLEMENTAL DRIVER LIBRARY


And this is what i get for ATI Mode 54h ... so the same thing.

The ATI Mode 55h for both the Charger and Edge just dump me back to MS-DOS.

I was going to try the Windows 3.0 800x600x16 drivers here: http://www.vogonsdrivers.com/getfile.php?fileid=268&menustate=6,1 And they don't work on Windows 3.0 in standard or 386 enhanced mode. I've disabled emm386 so it's just himem.sys. So I thought I'd try the MS-DOS drivers and the test pro...

,I've been thinking that it can't handle largest executable memory greater than 576 KB...so, I had to revert to the Logitech mouse driver. Using the stock vga driver, i get 615kb usable dos ram on 3.0 with ms-dos 5.00 using emm386 from 6.22. Ill write some malloc stress programs for dos and windows...

if you have emm386 running itll try to do the same thing, i was under the impression that it was for configs that didnt se emm38.6. No, Windows 3.0 *ALWAYS* looks in SYSTEM.INI and never at EMM386's parameters. Windows 3.1 seems to also look at EMM386. It's also why Windows 3.0 locks up in Virtual ...

- neozeed: Did you specifically add B000-B7FF into SYSTEM.INI? Otherwise, Windows will ignore those segments. if you have emm386 running itll try to do the same thing, i was under the impression that it was for configs that didnt se emm38.6. If both are doing the same layout wont they conflict with...

The 2.11 install was straightforward. I was very conservative in the setup (486 66Mhz, ET4000AX, SB16, 8MB ram, 500MB HD). Ram was bumped up to 32MB after install and running ok at 1024x768. Multimedia services works partially. It messes up the SB16 IRQ and DMA and those need to be changed. For som...

amadama wrote:Running the Windows Clock locks up the Windows subsystem in OS/2 2.1 also.

That is so bizzare... i wonder if i have symbols for clock.exe

It never was a SDK sample from what i recall.

2.11 install much easier?

Yes, it is. I am just saying, saying there's no bug because Windows 3.0 still loads OK (when it even ignores EMM386 parameters) is jumping to conclusions. :p You need to try to load *DOS* stuff (or even Windows itself) loaded into those segments to reproduce the erratical behavior, which makes us u...

Yes, Windows 3.0 loads OK, because Windows 3.0 does not use those segments by default. Windows 3.0 doesn't care what parameters are used with EMM386. It uses its own parameters in SYSTEM.INI. Try adding B000-B7FF and most probably it'll start behaving erratically. I thought the goal was maximum ram...

looking through the memory dump... a0000 top of DOS ram (640kb) b8000 text space (CGA/EGA/VGA) c0000 video rom c5b80 video end c6800 something c8000 endthing f0000 bios ffffe biosend so I tried emm386 from MS-DOS 6.22 something like this device=emm386.exe x=a000-afff i=b000-b7ff x=b800-bbef x=c000-c...

Don't install quemm. or emm386 or anything else like it. try to keep the configuration as PLAIN and SIMPLE as possible. More like, the bug in PCem needs to be fixed. Again, I did I=B000-B7FF on real hardware all the time and never had these problems. Only in PCem does that cause problems. PCem's me...

Although the latest update is only a Win64 fix (I never can seem to build this under Win64... grrr) Here is an updated Win32 binary: PCem-build-335-pcap-slirp.7z I've only included 2 executables, the debug, and an -O2 fast float. It turns out all the other stuff had a negligible impact on performanc...

Got my gopher working again... and it doesn't preserve the layout so well. yuck.

Okay, I attempted to install Internet Explorer 5 (16-bit) on Windows 3.11. After IE5 tries to copy the files, Windows crashes and QEMM throws an Exception 6 error: QEMM Exception 6.png Something is amiss here! It either has got to do with the QEMM386.SYS settings in the CONFIG.SYS or due to the err...

Since OS/2 Warp 3 (including Red Spine/Blue Spine and Warp Connect versions) is not easy to install, I think that it would be wise for the PCem forums to include a new category...the Tutorial section on how to install OS/2 Warp 3 (or Warp 4) inside PCem! By the way...has anyone tested Win-0S/2 supp...

amadama wrote:Awesome! Took your advice on the video card and now all is well. Network too using the drivers you pointed out.

Super awsome!
I need to fix my gopher server

I can confirm that this driver, ne2000wc works in OS/2 Warp 3.0 Connect.

ne2000wc.zip 11.09 KiB 1996-05-01 Warp Connect NE2000-compatible network adapter (20-Jun-95)

That's pretty good, but what happened at the end there? I was able to make it to completion of install and it worked ok (minus the network of course). Unfortunately I changed the driver to use the S3 864 (emulating a Paradise Bahamas 64 (S3 864) card in PCEM). After rebooting I got the stretchy, di...

Well I couldn't leave well enough at home and tried neozeed's advice on switching emulated motherboard and CPU. Now with SIS 496/497 and Pentium o/d 83 the OS/2 Warp 3 install continues. Looks like the built in NE2000 OS/2 driver isn't working right so may need an update. Almost there... Yep, anoth...

OK, so I installed Warp 3.0. http://i.imgur.com/WmrHQsZ.png http://i.imgur.com/Cao2eDn.png I'm using the Warp 3.0 Connect blue spine with the 'fixed' Disk1 , which I see is for this version, which is why it was bombing on a file copy with the other Warp 3.0 blue spine (no connect) CD. I'm using: AMI...

ISO image mounted in Virtual CloneDrive. PCem still quits if I reboot with CD-ROM disabled so I don't think it's trying to read from CD at that point. Edit: You know, I'm done with OS/2 versions over 2.11 at this point. Moving on to less frustrating things. I got warp to (mostly) install using an A...