VOGONS


Pył, Pyl, Dust English language version

Topic actions

Reply 80 of 121, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie

Thanks for uploading these. But how do you get it to run, please?

I've downloaded and installed Pyl from the Pyl CD image (called Pyl.iso, size 606,162,944 bytes), then downloaded both of your .7z files, un-archived them into the Pyl folder, and run the qemu.bat file, and the game doesn't start. Neither does the game start if I run s.exe

I've put the .ISO file into the folder, and even mounted the ISO file (which became drive R:), but neither qemu.bat nor s.exe start the game.

Here's the file listing of the folder:

Directory of D:\Pyl

15/05/2020 22:21 <DIR> .
15/05/2020 22:21 <DIR> ..
15/05/2020 21:38 <DIR> DATA
15/05/2020 21:38 <DIR> LEVEL
15/05/2020 21:38 <DIR> PLAYER
01/02/2020 01:32 262,144 bios-256k.bin
14/05/2020 15:16 2,149,580,800 boot.vdi
14/05/2020 22:14 15,578 dgvoodoo.conf
17/04/2020 18:55 352,256 dgVoodooCpl.exe
15/05/2020 21:39 265,396 DOS4GW.EXE
01/02/2020 01:32 240,128 efi-e1000.rom
13/05/2020 20:23 93 glide.cfg
17/04/2020 19:09 146,432 glide.dll
17/04/2020 19:09 145,920 glide2x.dll
17/04/2020 19:09 148,480 glide3x.dll
01/02/2020 01:32 9,216 kvmvapic.bin
09/04/2020 13:16 32,768 libffi-7.dll
06/04/2020 14:13 82,944 libgcc_s_seh-1.dll
10/04/2020 16:43 1,560,576 libgio-2.0-0.dll
10/04/2020 16:43 1,228,800 libglib-2.0-0.dll
10/04/2020 16:43 24,064 libgmodule-2.0-0.dll
10/04/2020 16:43 333,824 libgobject-2.0-0.dll
13/05/2019 07:18 1,055,522 libiconv-2.dll
14/05/2019 11:23 135,218 libintl-8.dll
09/03/2020 17:26 283,648 libpcre-1.dll
20/04/2020 19:21 681,472 libpixman-1-0.dll
06/04/2020 14:13 20,480 libssp-0.dll
25/04/2020 15:02 53,760 libwinpthread-1.dll
15/05/2020 21:39 1,011,472 MFC42.DLL
15/05/2020 21:39 267,536 Msvcrt.dll
15/05/2020 21:39 1,633,038 PYL.EXE
15/05/2020 21:39 1,078 PYL.ICO
15/05/2020 21:39 131 pyl.ini
26/01/2013 17:49 606,162,944 Pyl.iso
15/05/2020 21:39 770,048 PYLINSTL.EXE
15/05/2020 21:39 40,960 PYLSETUP.EXE
14/05/2020 15:53 3,014 qemu.bat
12/05/2020 20:18 9,113,088 s.exe
13/04/2020 07:54 1,549,312 SDL2.dll
15/05/2020 22:21 0 t.txt
01/02/2020 01:32 39,424 vgabios-stdvga.bin
22/05/2019 13:06 93,720 zlib1.dll
37 File(s) 2,777,345,284 bytes
5 Dir(s) 16,483,233,792 bytes free

The t.txt file is just the directory listing, obtained by me typing dir /o > t.txt, if you're wondering what it was doing there.

Thanks for any help.

Reply 81 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

you must install
Intel® Hardware Accelerated Execution Manager (Intel® HAXM)
from here https://github.com/intel/haxm

Reply 83 of 121, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie

Nope, still not working. First of all, should I put the .ISO in the PYl folder, or mount the ISO as a disc in a drive, or (mount the ISO as a disc in a driver and) install Pyl via it's own installer to the Pyl directory using MagicDisc or similar?

I've currently done all three, , but the game won't run.

Running qemu.bat (with the ISO mounted as R:) writes the following text to the screen (recorded here by qemu.bat > t2.txt)

D:\Pyl>SET QEMU_AUDIO_DRV=sdl

D:\Pyl>s.exe boot.vdi -cdrom a: -soundhw sb16,adlib -accel hax
s.exe: -cdrom a:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom b: -soundhw sb16,adlib -accel hax
s.exe: -cdrom b:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom c: -soundhw sb16,adlib -accel hax
s.exe: -cdrom c:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom d: -soundhw sb16,adlib -accel hax
s.exe: -cdrom d:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom e: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom f: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom g: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom h: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom i: -soundhw sb16,adlib -accel hax
s.exe: -cdrom i:: Could not refresh total sector count: Input/output error

D:\Pyl>s.exe boot.vdi -cdrom j: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom k: -soundhw sb16,adlib -accel hax
s.exe: -cdrom k:: Could not refresh total sector count: Input/output error

D:\Pyl>s.exe boot.vdi -cdrom l: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom m: -soundhw sb16,adlib -accel hax
s.exe: -cdrom m:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom n: -soundhw sb16,adlib -accel hax
s.exe: -cdrom n:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom o: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom p: -soundhw sb16,adlib -accel hax
s.exe: -cdrom p:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom q: -soundhw sb16,adlib -accel hax
s.exe: -cdrom q:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom r: -soundhw sb16,adlib -accel hax
Failed to open the HAX device!
Open HAX device failed
Failed to get Hax capability:6u
No accelerator found.
s.exe: -accel hax: failed to initialize hax: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom s: -soundhw sb16,adlib -accel hax
s.exe: -cdrom s:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom t: -soundhw sb16,adlib -accel hax
s.exe: -cdrom t:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom u: -soundhw sb16,adlib -accel hax
s.exe: -cdrom u:: Could not read image for determining its format: Input/output
error

D:\Pyl>s.exe boot.vdi -cdrom v: -soundhw sb16,adlib -accel hax
s.exe: -cdrom v:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom w: -soundhw sb16,adlib -accel hax
s.exe: -cdrom w:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom x: -soundhw sb16,adlib -accel hax
s.exe: -cdrom x:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom y: -soundhw sb16,adlib -accel hax
s.exe: -cdrom y:: Could not read image for determining its format: Input/output
error

D:\Pyl>s.exe boot.vdi -cdrom z: -soundhw sb16,adlib -accel hax
s.exe: -cdrom z:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom a: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom a:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom b: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom b:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom c: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom c:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom d: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom d:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom e: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom f: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom g: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom h: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom i: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom i:: Could not refresh total sector count: Input/output error

D:\Pyl>s.exe boot.vdi -cdrom j: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom k: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom k:: Could not refresh total sector count: Input/output error

D:\Pyl>s.exe boot.vdi -cdrom l: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom m: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom m:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom n: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom n:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom o: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom p: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom p:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom q: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom q:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom r: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

D:\Pyl>s.exe boot.vdi -cdrom s: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom s:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom t: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom t:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom u: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom u:: Could not read image for determining its format: Input/output
error

D:\Pyl>s.exe boot.vdi -cdrom v: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom v:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom w: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom w:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom x: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom x:: Could not open device: Invalid argument

D:\Pyl>s.exe boot.vdi -cdrom y: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom y:: Could not read image for determining its format: Input/output
error

D:\Pyl>s.exe boot.vdi -cdrom z: -soundhw sb16,adlib -accel whpx
s.exe: -cdrom z:: Could not open device: Invalid argument

D:\Pyl>pause
Press any key to continue . . .

(The pause, of course, was added by me to the batch file). I don't think the failure of the game to run is down to the .ISO or it's contents, because I've tried to cover all three ways of using it, but maybe something due to:

D:\Pyl>s.exe boot.vdi -cdrom r: -soundhw sb16,adlib -accel whpx
s.exe: -accel whpx: Could not load library WinHvPlatform.dll.
s.exe: -accel whpx: failed to initialize whpx: Function not implemented

Reply 84 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

if you have Windows 10 you have to uninstall WHPX,
so uninstall "Hyper-V" and "Windows Hypervisor Platfrom" from windows components

Reply 85 of 121, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie

No, it's Windows 7.

Reply 86 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

cpu must be at least Nehalem

Reply 87 of 121, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie

That's probably it then. I'm trying to run it on my laptop (it's been too nice recently to not spend time in my garden, one of the few good things about the present state of the world), which is an old HP Pavilion g6-1331sa with a 1.6 GHZ AMD Quad-Core A8-3520M CPU (according to (https://support.hp.com/gb-en/document/c03125593#AbT0).

Reply 88 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

you must use intel desktop

Reply 89 of 121, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie
robertmo wrote on 2020-05-18, 14:47:

you must use intel desktop

You mean it needs an Intel CPU and probably a desktop, not laptop, PC? Fair enough, and thanks for all the help. It's much appreciated.

Reply 90 of 121, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie
Kerr Avon wrote on 2020-05-18, 20:40:

You mean it needs an Intel CPU and probably a desktop, not laptop, PC? Fair enough, and thanks for all the help. It's much appreciated.

Only if you want to use Intel HAXM accelerator for obvious reason.
AMD CPUs have no viable accelerators for QEMU on Windows, other than Windows 10 x64 when Microsoft finally provides vendor agnostic user-space APIs for virtualization. However, AMD was more generous with CPU features. Unlike Intel, AMD did not leverage CPU virtualization for market segmentation, so every AMD CPUs had AMD-V when the feature was marketed while Intel reserved it for higher priced segment in the Core series. Celerons and Pentiums did not get Intel-VT in the beginning.

Reply 91 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

you need the power of desktop cpu, gpu and haxm

Reply 92 of 121, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie

With x86/PAT cacheability fix, I guess WHPX would probably have the same performance as HAXM.

Reply 93 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++
rasz_pl wrote on 2019-02-13, 12:28:
RaVeN-05 wrote:

i tried Pyl on real hardware Pentium 2 350Mhz + Voodoo2 8mb seems not enough for better fps, does game designed that bad way?

Yes, it was a crap/paździerz. Dos only Glide only Quake 1 clone build on 3d engine written by first timer while working on his midterm exams, and released in 1999 by incidental "hey, we manufacture millions of computers per month lets branch out to development" publisher of low budget edutainment pre-install shovelware (software whose sole purpose was padding value of Optimus computers sold to edu segment in Poland).
I only remember this game from gaming magazines (something about being shit quake clone), never knew personally anyone who either played or owned it, didnt even see it listed by pirates. Sad state of affairs really.

i5-3450 + Voodoo 5 5500 gives worse results than qemu + dgvoodoo2 on same machine (different gpu 😉

Last edited by robertmo on 2021-04-15, 05:07. Edited 1 time in total.

Reply 94 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

i5-3450 + Voodoo 3 2000 PCI has same problems
but Athlon 1666 works nicely with either Voodoo 3 2000 PCI or Voodoo 3 2000 AGP 😀

Reply 95 of 121, by robertmo

User metadata
Rank l33t++
Rank
l33t++

v3 pci and v5 pci slow down problems were caused by having game on a usb drive. While on hdd it is ok.

Reply 96 of 121, by MrBunwah

User metadata
Rank Newbie
Rank
Newbie

Hi, I wonder if anyone can help me. I'm writing about Dust for an upcoming FPS project and I'm not sure who to credit the game to.

I've only seen the name Optimus-Nexus associated with the game, but that seems to be the publisher, so what were the developers called? I've also seen Optimus Pascal Multimedia listed as the publisher, but that doesn't match what the developers say in an interview.

Any help would be great to help me avoid errors in the text.
Thanks a lot!

Reply 97 of 121, by Garrett W

User metadata
Rank Oldbie
Rank
Oldbie

I believe you can find the credits in this page by one of the creators.

Reply 98 of 121, by MrBunwah

User metadata
Rank Newbie
Rank
Newbie

Thanks, I've had a good look at that site as well as interviews like this: https://www.old-games.ru/articles/55581.html and pretty much anything else I can find relating to the game.

I can see the names of the various people who developed the game, but - possibly due to having to translate most of the pages to English - can't work out the development studio's name. For instance, that site says "The headquarters of Optimus-Nexus was in Sopot, but the production team operated in Silesia." which implies they were separate.

It's not a huge deal, I can just put Optimus-Nexus as both developer and publisher, but just wanted to check in case I can be more accurate.

Reply 99 of 121, by NostalgicAslinger

User metadata
Rank Member
Rank
Member

This game is very hardware demanding and has a high level of difficulty.
I have played it on my Celeron A 333@375 with a Voodoo2 12MB and it is playable with the highest settings, but with lot of smoke effects on the screen, the framerate goes under <20 fps.
The recommended CPU for this 1998 game is a Pentium II 300! A good polish game, also with details textures like Unreal, good lighting effects (for example the lamps) and Pyl reminds me on a Polish Half Life! 😁