86Box/86Box

Printer Error

Remzloi opened this issue · 4 comments

Remzloi commented

What happened?

When the Generic Postscript printer prints, this appears instead of an image:
image

Configuration file

[Standard PS/2 Mouse]
buttons = 2

[General]
vid_renderer = qt_software
vid_resize = 1

[Machine]
machine = cubx
cpu_family = celeron_mendocino
cpu_speed = 533333333
cpu_multi = 8
fpu_type = internal
cpu_use_dynarec = 1
fpu_softfloat = 0
time_sync = local
cpu = 11
mem_size = 32768

[Video]
gfxcard = cl_gd5446_pci

[Input devices]
mouse_type = ps2

[Sound]
sndcard = sb16_pnp
fm_driver = nuked

[Network]
net_01_card = pcnetisa
net_01_net_type = slirp
net_01_link = 2
net_02_link = 0
net_03_link = 0
net_04_link = 0

[Ports (COM & LPT)]
lpt1_device = postscript

[Storage controllers]
hdc = internal
cassette_mode = load

[Hard disks]
hdd_01_parameters = 63, 16, 1054, 0, ide
hdd_01_fn = E:/86box/жд корги.vhd
hdd_01_speed = ramdisk
hdd_01_vhd_blocksize = 1024
hdd_01_ide_channel = 0:0

[Floppy and CD-ROM drives]
fdd_01_type = 35_2hd
fdd_02_type = none
cdrom_01_speed = 72
cdrom_01_parameters = 1, atapi
cdrom_01_ide_channel = 0:1
cdrom_01_host_drive = 200
cdrom_01_image_path = E:/86box/Windows 98 Second Edition.ver.4.10.2222.Russian.iso
fdd_01_image_history_01 = E:/загрузки/86box/Windows/Second Edition Setup Disk.img
fdd_01_image_history_02 = E:/загрузки/86box/Windows/boot98special.img
cdrom_01_type = KENWOOD_CD-ROM_UCR-421_208E

[AMD PCnet-ISA #1]
mac = 4a:6f:3c

Operating system

Windows 10

CPU

Intel Core 2 Duo E7500

86Box version

v4.0 build 5000

Build architecture

Windows - x86 (32-bit)

Build type

  • New recompiler
  • Debug build

Download source

Official website (Jenkins, GitHub)

Additional context

No response

headsetguy37 commented

What printer did you install in the emulated machine's operating system?

OBattler commented

Also, the 86Box build used is very old.

  • 👍1
OBattler commented

Also, a Celeron Mendocino 533 is going to perform very awfully on a Core 2 Duo. Please reduce it to something sensible, such as Pentium 75. I'm quite sure the timings are breaking down, which would explain the observed printer (mis)behavior.

  • 👍1
OBattler commented

Closing this as NOTABUG - the user chose emulated hardware way in excess of what their host can do.