Problem installing OS/2 Warp 4.52

[ATeamInc]

Basically, the installation goes fine until the last portion of copying files in every virtualizor I have tried. Always when OS/2 tries to copy NAMEMOVE.EXE, it hangs for a bit then displays this:

Is there a solution for this? Or it is a defective CD?
PS: I got the CD from the FTP.

[TheCollector1988]

Does this happen on 86Box?

[ATeamInc]

Yes it does

[TheCollector1988]

Try the latest binary release at the softhistory rol channel. Ask Battler for it.

[ATeamInc]

I don't see honestly what that might differ. I think it may be a bad cd, but I got it fron the FTP and that is why I think there is some strange problem. Anyway, I'll try that and see if that makes a difference.
EDIT: I thought maybe the downloaded file may be bad, so I tried this:

And you see they match.
SO I think the copy on the FTP is bad. I will try downloading another one later.

[TheCollector1988]

Can you try using SCSI (on 86Box)? Like, the aha154x or buslogic or trantor 130b.

[ATeamInc]

I'll see then.
EDIT: Interestingly enough, 86Box crashes when it tries to load Disk02.img to proceed after setting both the HDD and CDROM to SCSI.
I don't think this is OS/2's problem, but rather 86box since I had faced a bit similar problems when installing Windows NT 4.0 using the SCSI settings, but I eventually gave up on the project after several tests with multiple adapters and configs.

Offtopic Comment

Even with all this, an S3 compatible graphics card causes no display output on 86box, even with the latest versions and multiple PCI-supported machines. Strange

[Battler]

- ATeamInc: Please paste your 86Box config so I can debug this.

[ATeamInc]

[Machine]
machine = 430vx
mem_size = 32768
cpu_use_dynarec = 1
cpu_enable_fpu = 1
cpu_waitstates = 1

[Video]
gfxcard = tgui9440_vlb
video_speed = -1

[Input devices]
mouse_type = mssystems

[Other peripherals]
hdc = ide_pci_2ch
scsicard = aha1540b

[Standard PS/2 Mouse]
buttons = 3

[Novell NE2000]
base = 0300
irq = 10
bios_addr = 00000
mac = b9:a1:44

[Mouse Systems Serial Mouse]
port = 0
buttons = 3

[Sound]
sndcard = sbawe32

[Network]
net_card = ne2k
net_type = slirp

[Hard disks]
hdd_01_parameters = 63, 16, 1023, 0, scsi
hdd_01_fn = D:\NewEmu\DISK.img
hdd_01_scsi_location = 00:00

[Floppy drives]
fdd_01_type = 35_2hd
fdd_01_fn = D:\NewEmu\Stuff\Operating Systems\IBM OS2 Warp 4.52 (14.089_W4) [English]\media_img\Disk02.img
fdd_02_type = 525_2hd

[CGA]
display_type = 0
composite_type = 0
rgb_type = 2
snow_enabled = 1

[Other removable devices]
cdrom_01_parameters = 1, scsi
cdrom_01_host_drive = 200
cdrom_01_image_path = D:\NewEmu\Stuff\Operating Systems\IBM OS2 Warp 4.52 (14.089_W4) [English]\media_iso\ibm_warpclient_cp2_v4_52_boot.iso
cdrom_01_speed = 24
cdrom_01_scsi_location = 01:00

[Sound Blaster AWE32]
base = 0220
emu_base = 0620
base401 = 0330
irq = 5
irq401 = 9
dma = 1
dma16 = 5
mode401 = 1
onboard_ram = 8192
opl = 1

[Adaptec AHA-1540B]
base = 0334
irq = 9
dma = 6
hostid = 7
bios_addr = C8000

[Battler]

OK, thanks, I'm going to look at both the bugs you reported (error with IDE and crash with SCSI).

Edit: For now, let me point you at some problems I found in your configuration:
- You have both the SCSI controller and the MPU-401 on IRQ 9 - make sure that is not so;
- The AWE32 tends to make OS/2 hang, I recommend switching to Sound Blaster 16;
- That I know of, the Trident graphics cards do not work correctly with OS/2, try the S3 Trio 64, or (since you said the Trio64 does not work) a Cirrus Logic (I recommend the 5434 PCI) or the S3 ViRGE (I recommend the VBE 2.0 one as it's the best ViRGE we emulate).

Also, what build of 86Box are you using?

Edit #2:

Even with all this, an S3 compatible graphics card causes no display output on 86box, even with the latest versions and multiple PCI-supported machines. Strange

Which S3-compatible graphics card exactly?

[TheCollector1988]

Very recently the trio64 (if you chose that) has been improved on the OS/2 guest side

[ATeamInc]

Very recently the trio64 (if you chose that) has been improved on the OS/2 guest side

You did not get me right, as no display output is initialized once 86box starts with any PCI machine.

[Battler]

That does not happen on my end. Are you sure you selected the *PCI* variant of the Trio64?

[ATeamInc]

That does not happen on my end. Are you sure you selected the *PCI* variant of the Trio64?

Interestingly enough, it decided now to work by itself while it wasn't giving any sort of video about 2hrs ago with the exact same config.

[TheCollector1988]

Now try the latest jenkins build.

[StormFiber]

I for one, would benefit from a write-up on OS/2 installation.
Like you, I did an installation on a T42p a year ago, but did not document my steps.
I DO remember it was a long and exasperating experience!
Through trial and error it finally did boot to an this doesnt feel like me operating system.
I have several T60/61 systems and an X220 that are prime candidates for testing!