I've got a set of two spanish disk for Olivetti PCS 86. Disk 1 have MS-DOS 3.30, Disk 2 have some MS-DOS files, a tutorial and a diagnostic utility. I had a friend that had a Olivetti PCS33. It came with DOS 5.0, Windows 3.x (I think it was 3.1, but maybe it was 3.0) and a disk compression utility ...

I found one archived page with Olivetti setup disks and drivers for some models http://web.archive.org/web/19980418135138/http://nssweb.olivetti.za:80/pages/softlib.htm And about IDE PIN 28 'controversy' it was docummented at least on some FIC mainboards: ____________________________________________...

Not really, it died too... Then it was killed in the line of duty :( If you want to know what's using DMA1 you can use Dr. Hardware Sysinfo https://www.majorgeeks.com/files/details/dr_hardware_sysinfo.html it's shareware and you can test almost everything (chipset tests are disabled) for 14 days be...

My PCS now has a 4.1 GB hard disk, and Ontrack Disk Manager does its job just fine. I'm SOOOOO happy I'm really happy to hear that :D - the old HD actually killed my IDE-USB adapter (the SATA port on it is fine). They seem dangerous! The old hard disk finally wins a battle against USB adapters ;) -...

Can you program an EEPROM with the original BIOS? Because they ship an "anonymous" BIOS Very interesting proyect It's a clone of the IBM 5150 board so it can be fitted with all the same ROM chips, take a look here for more info: http://www.minuszerodegrees.net/5150/motherboard/5150_u33.htm

It seems that IDE PIN 28 was early used for ALE (Address Latch Enable) later for SPSYNC (Spindle Synchronization) and finally for CABLE SELECT. And the drives recognised by the Olivetti PCS can be jumpered for SINGLE DRIVE, MASTER, SLAVE and CABLE SELECT. Then I guess that those drives used on Olive...

PCS 286: Works with a few issues during boot and CMOS setup. Tested with: DOS, Windows 3.1 and some games. During boot it will complain about VGA and Protected Mode, just press F1 to skip. Needs HEADLAND GC101, GC102, GC103 chipset and a few things. PCS 286 S: Works with a few issues during boot an...

:!: I've found by the hard way that those drives with single drive feature will die when connected to USB or SATA converters or even to modern mainboards. :!: I'm not sure if setting them before to MASTER can solve this but I've already lost 3 working drives trying to make backups and after asking ...

Nice to hear that, congratulations! and what a surprise by the way :o I didn't know that, the few times I used it without the riser was booting from HD and with some card fitted on the mainboard slot for testing without conflicting with the other cards or having to remove them from the raiser. Yess,...

:arrow: I must clarify this a little, when I said: As with physical machine BIOS expects some CMOS bytes initialised (using provided NVR image) I meant to set DS1287 (for models using this RTC chip) control registers to proper values (enable RTC oscillator, disable low battery bits and son on) becau...

Welcome, see the private message because it's not very related to PCem development to post here…

I've this CD-ROM with some SB drivers: https://1drv.ms/u/s!AsfYUL_MlCt-hNRfWrscUt-kVwkTdg (size is about 12MB)
See the readme files to know for what is each one.

[/quote] And yet, I never ever saw the splash screen being drawn from the bottom to the top . Wild guess: different adapters = different drivers = different ways to access the framebuffer? [/quote] In this case VGALOGO.RLE is a standard BMP file (first two bytes are 'BM') and the image on Windows bi...

Well, I've tested the same HD image with PCem with 386DX @ 16 MHz and DOSBox with cpu settings core=normal cputype=386 and PCem appears to be too fast, but according to those videos of 386 computers the 'progressive' splash would happen only on very very slow machines/video cards and PCem display sp...

This could be altered because on Windows 3.x VGALOGO.LGO contains the code to display VGALOGO.RLE and it's not the same code on all drivers/resolutions/versions possibly having different splash effects WIN.COM is not present on setup disks :roll: it's made by joining WIN.CNF + VGALOGO.LGO + VGALOGO....

Nice job, everything works fine again.

Well, I still have the problem with SB16, perhaps am I using some wrong dll? corrupt MSYS2 environment? somewhat missing? :roll: Could anyone with a successful compilation under MSYS2 upload somewhere its pcem.exe + all dll files please? even the full src folder with the good Makefile will be usefu...

Well, I still have the problem with SB16, perhaps am I using some wrong dll? corrupt MSYS2 environment? somewhat missing? :roll: Could anyone with a successful compilation under MSYS2 upload somewhere its pcem.exe + all dll files please? even the full src folder with the good Makefile will be useful...

I did the same (installed everything included in msys2-devel) because I got this message before: $ Mingw32-make -j CDPATH="${ZSH_VERSION+.}:" && cd . && C:/msys64/usr/bin/sh.exe /home/user/pcem/missing aclocal-1.15 /home/user/pcem/missing: línea 80: aclocal-1.15: no se enco...

Yeah, if you want speed, MSYS2 is not the way to go. It is however far more convenient to get started. All the libraries and headers required (except for pcap headers) are available from the MSYS2 repository. There is no need to try and figure out which files go where, especially with wxWidgets. Al...

Good job, now it works perfectly under MSYS2 :-) I ran the following commands to get a fresh executable: hg clone https://bitbucket.org/pcem_emulator/pcem cd pcem ./configure --enable-networking --enable-release-build Mingw32-make -j strip ./src/pcem.exe And about the speed for me it seems that MSYS...

:arrow: EDIT: It was my fault, for some reason I was using one or more invalid dll's, restoring the previous ones from a backup fixed those errors: The procedure entry point _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE7compareEPKc could not be located in the dynamic link library C:\msys64\...

Just a curiosity that I've forgot to mention before: PCS 386 SX BIOS has some kind of built in debugger.

Maybe accessed by a key combination but I don't know it. I've used debug command g=f000:a3be

Now that the emulation problem is solved I want to explain how to determine the version of the game that you are using, because the game itself won' t test CPU type and loading the 286 version on a 8086/8088 will hang the system without any explanation: There are (at least) 3 types of Titus executa...

:?: It's enough to say there's a BUG in the PCem 8086 emulation if other emulator(s) can run it flawlessly? http://www.hampa.ch/pce/ seems sturdy, but I find it difficult to operate it, take a look if you want Well, I meant if someone wants to investigate in PCem why it does not work in PCem... I p...

:?: It's enough to say there's a BUG in the PCem 8086 emulation if other emulator(s) can run it flawlessly? A problem with a single game may not seem important for now but it may affect some other software, if someone wants to investigate it I can provide the 8086 executable because all other files ...

Finally in PCE/ibmpc http://www.hampa.ch/pce/pce-ibmpc.html works peerfectly on all video modes and 8088/8086/80188/80186 CPU @ 4.77MHz titus_pce-ibmpc_cga.png titus_pce-ibmpc_ega.png titus_pce-ibmpc_vga.png Using this configuration: (Here I mean PCE config, NOT PCem config) C:\msys64\home\user\PCE-...

In PCem with 8088/8086 displays the same as in VB8086 with any video card and any Titus command line swithces: titus_PCem-808x.png With 80286 or higher it runs fine in CGA, EGA and VGA: titus_PCem-80286.png In Retro http://jorisvr.nl/article/retro runs well in CGA mode. EGA and VGA aren't implemente...

Titus runs fine on VB8086 emulator on autodetected CGA mode: titus_vb8086_cga.png It can be forced to VGA mode with /V switch and it does work too: titus_vb8086_vga.png But if forced to EGA (/E) it gets stuck on video mode Dh: titus_vb8086_ega.png Screenshot shows MS-DOS booting because it's being l...

I do think many manufacturers used NEC Vxx series mainly because them offered better performance at similar or even lower costs than the Intel 8088/8086/80186 I don't expect to see anything using 8080 (8 bit) code on a XT clone, 8088/8086/80286 emulation should do the job for most BIOS and all PC/XT...