PCem

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...

Yay real numbers! OK, I'm using MS-DOS 5.00 and no config.sys just the commands above in autoexec.bat. My Processor is.. Number of cores 4 (max 8) Number of threads 8 (max 16) Name Intel Xeon E3 1230 v3 Codename Haswell-WS Specification Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz Package (platform ID)...

ppgrainbow wrote: I should start a new thread regarding DOS memory optimisation.

Yes....

And this is why I want an EMS board so I don't have to deal with emm386... or any of it's friends. I've never liked that POS, and all the magical issues it brings into the world.

That's the entire file. This was on OS/2 Warp 3 Connect CD Version with DOS and Windows support. It's one that came with two CDs (one install and one Bonus Pack) and two floppy disks for boot and install. I used the same modified Floppy disk that I posted on the other OS/2 thread for install. The i...

@neozeed- Thanks for updated build. The same issue persists with OS/2 Warp 3 and PCem just quitting. pclog is attached as an fyi. Thanks Wow.. what version of OS/2 3? There is blue and red.. are you using stock diskettes? Is it the CDROM version? Was that log file truncated on your end, or the uplo...

Thank you for the update! :) I should be fine with r334, until I run into problems again. Since you like IE 5.0 on 3.1 I did find another copy I had tucked away... http://i.imgur.com/oyG1l95.png ie5win31.exe It's a cintek customized version that they kind of botched, it's missing some cursor but yo...

Ugh never mind I figured it out. I had a dead drive mapping, I didn't notice. So yeah on closing the search dialog it scans all drive mappings for some reason.

te_lanus wrote:I don't know, always seems instant for me

I'm on Windows 10 x64...

And I should add, a stock source dist, with default flags....

is it me, or does chaining disk images, take forever? Getting the dialog and selecting the disk image is quick, but after that the UI locks. ejecting is instant, but loading the image locks for about 5-30 seconds. Is there a reason the main thread seems to spin on vacation somewhere else? Just wonde...

Latest build: build 334: http://vpsland.superglobalmegacorp.com/install/pcem/PCem-build-334-pcap-slirp.7z Username password for the 404 page is currently: user / dryherring35 Although this changes on it's own, so if you are from the future, just guess, it'll then tell you the updated user/password i...

I've noticed something with the Phoenix 386 clone. The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amou...

Try this disk. (this is disk 1, disk 0 stays stock) https://www.dropbox.com/s/0mzaha844q2wdd5/Disk1.zip?dl=0 It bombs in the same spot. Oh well it's no big deal, personally I hated Warp 3 with it's stupid dock thing. It wasn't good enough to be like in NeXTSTEP, and it sure wasn't enough to compete...

The ATAPICD$ error is repaired using the IBM fixpack that was mentioned in the link I posted above: http://service.software.ibm.com/os2dd/free/idedasd.exe I will send you my updated "fixed" floppy disk 1 this afternoon. But if you want to do it now check out the readme file in the pack. (delete the...

Ok, so here is some more information on this crash. I've tried updating the CD-ROM drivers, and the stock drivers, and they fail the same way..... Which I suppose is good. I'm running Windows 10 (x64) with a 32bit MinGW building PCem. I'm using VirtualCloneDrive 5.4.7.0 mounting the BlueSpine CD. By...

Ok, I see that the probes will of course do stupid things, since they think the NE2000 is a sound card, or some other old sound card CD-ROM interface, so it sends bad data which causes a panic. So I 'fixed' all the panic path's in the NE2000 to log an event, and continue. It won't exit now (it never...

Not sure which other driver triggers the fault but here we go. Breakpoint 1, 0x005aac18 in exit () (gdb) bt #0 0x005aac18 in exit () #1 0x00506b37 in fatal ( format=0x655218 <outputleveldifference_bp_hp+39492> "page 2 write to reserved offset 4\n") at pc.c:108 #2 0x0058cf89 in ne2000_write (address=...

Thank you for telling me. I have to apologise that I gotten carried away on how to get OS/2 Warp 3/4 to work on PCem. I'm gonna have to go with neozeed and stick with OS/2 2.0, just to play safe. If I really wanted to install Warp 3, I'm gonna have to modify the CONFIG.SYS file to make things work....

look we don't need 30 threads, and you don't need to post it all over the place, try to keep this in one spot. First OS/2 warp is a total piece of shit. It has zero auto-detection for anything. As always the problem is that it's spamming port 0x300 and one of the drivers doesn't like what it see's. ...

the disk read/write corruption seems to be too severe to allow the installation to continue. Is anyone else getting this 'disk corruption' thing? I've never had this issue. And other than shitty CD-ROM probes I don't see how the NE2000 has anything to do with what is going on. This just reeks of un...

I have been informed by Tom that PCem crashing was due to the networking code that neozeed implemented and not in the main repository. I have tested r332 and the CD crash is not existent, but I end up getting a complaint that OS/2 install can't find the source drive to install Warp 3. Neozeed, you ...

I haven't seen the patch, but thanks for mentioning it! I've had some weird mouse issue crop up a few times where it won't hide the OS mouse, and running winodws on windows gets confusing as to which is which... Although I have no idea what triggered it as I never entered fullscreen. But I can apply...

@neozeed, I would recommend the following CFLAGS for the Sandy Bridge build: -march=corei7-avx -mtune=corei7-avx -mno-avx -mno-aes This will target Sandy Bridge and higher and exclude AVX and AES-NI (which are not supported in Pentium versions such as G3258). Will do a test of your posted builds to...

I'm wondering if buggy hard disk emulation is causing the IE5 (16-bit) to not install properly or not. In the years of using PCem I've never had it lose data... I just keep my disks small and in the realm of what existed back then... 63 sectors, 16 heads, 511 cylinders for a 251Mb disk. Or just loo...

What is a good way to get numbers on the overall performance? I just tried a bunch of different things, and all Ive seemed to prove is that PCem can give performance that measures from the inside at a constant rate... which is a 'good thing'.. 1282 -O3 -march=native -DRELEASE_BUILD 1283 -O2 -DRELEAS...

Success!!! All I did was comment out the entirety of the cdrom-ioctl-linux.c except the headers, then comment out those lines that were referencing it, and boom, it runs! I'm not entirely sure how to bring up the configuration menu (couldn't get it to open in linux), but I'm sure I'll figure that o...

- neozeed: There would probably be a big improvement if whatever is causing rendering to be very slow when the guest is not in 16-bit/24-bit/32-bit color modes, was fixed. As a comparison, look at the Windows 98 welcome screen in 256 color mode and in 32-bit color mode. In the former, it will take ...

Thanks for the updated build neozeed. Did some very basic testing of both the pcap and slirp configs using your core2 build on a WfW 3.11 PCEM "virtual" and they appear to work as expected. Can you include the ethlist.exe tool? It's very helpful. You had it in the last build but not on this one. Th...

Next time this happens, can you post the output of 'disassemble sound_cd_thread'? Looks like it was my fault mixing up makefiles... ugh. If it matters... the -O3 -march=i686 gives the same code as -O2 -march=core2 -O3 goes crazy, I guess some unaligned access thing. (gdb) disassemble sound_cd_threa...

Thanks for the updated build neozeed. Did some very basic testing of both the pcap and slirp configs using your core2 build on a WfW 3.11 PCEM "virtual" and they appear to work as expected. Can you include the ethlist.exe tool? It's very helpful. You had it in the last build but not on this one. Th...