Bernkastel7734 wrote on 2021-05-11, 12:54:

So that's the autoexec.bat and config.sys connected to CDROM and that soundcard : [autoexec.bat] SET BLASTER=A220 I5 D1 T4 LH C […]
Show full quote

So that's the autoexec.bat and config.sys connected to CDROM and that soundcard :
[autoexec.bat]
SET BLASTER=A220 I5 D1 T4
LH C:\DOS\MSCDEX.EXE /D:CDROM /L:D
[config.sys]
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\SOUND\CS4232C.EXE /V /O /VSS4232.INI
DEVICE=C:\DOS\DOAKCDROM.SYS /P:360,11 /D:CDROM

I'm guessing it's just a couple of typos there. What does that CS4232.INI file look like?

Bernkastel7734 wrote on 2021-05-11, 12:54:

DEVICE=C:\DOS\DOAKCDROM.SYS /P:360,11 /D:CDROM

Why is this still reading 360 and not 168 ?

weedeewee wrote on 2021-05-11, 13:09:

Bernkastel7734 wrote on 2021-05-11, 12:54:

DEVICE=C:\DOS\DOAKCDROM.SYS /P:360,11 /D:CDROM

Why is this still reading 360 and not 168 ?

Forgot to change it after a try, with 168 doesn't work as well

snufkin wrote on 2021-05-11, 13:07:

What does that CS4232.INI file look like?

[PNP]
WssIO=534
WssInt=5
WssDmaPlay=1
WssDmaCapture=0
SbIO=220
OplIO=388
OplInt=Disabled
GameIO=200
4232IO=538
4232Int=Disabled
MPU401IO=330
MPU401Int=9
CDIO=360
CDInt=11
CDDma=3
Device4IO2=Disabled
Device5IO=Disabled
Device5Int=Disabled

[IniUpdate]
SysIniFile=c:\windows\system.ini

;SoundBlasterIRQ=[sndsys.drv],SoundBlasterIRQ
SoundBlasterAddr=[sndsys.drv],OldMSDOSGameIOAddress
;SoundBlasterDMA=[sndsys.drv],SoundBlasterDMA

UsePnP=[sndsys.drv],UsePnP

WSSIRQ=[sndsys.drv],Interrupt
WSSAddr=[sndsys.drv],IOAddress
WSSPlayDMA=[sndsys.drv],DMADAC
WSSCaptDMA=[sndsys.drv],DMAADC

MPU401IRQ=[mpu401.drv],int
MPU401Addr=[mpu401.drv],port

CS4232Addr=[sndsys.drv],CS4232Control

FMAddr=[csfm.drv],portFM
; For now keep this disabled
;FMIRQ=[csfm.drv],Int
;JoystickAddr=[sndsys.drv],Joystick

Ok, this might be back-to-front, but try changing the CDIO line to 168, or 36E (the resources given in win98)

snufkin wrote on 2021-05-11, 13:15:

Ok, this might be back-to-front, but try changing the CDIO line to 168, or 36E (the resources given in win98)

Already tried with 168, will try with 36E

could you try without loading the soundcard driver in config sys. It might be messing up the config of the chip since there are some differences between the 4232 and 4237.

you will have to experiment with the io,irq adresses again.

and you might want to give unisound a try to set up the card.

Will try without that line in config.sys. Already tried with unisound, if nothing changes I'll focus on it

If you try the Unisound option, then take note of Oetker's post from before:

Oetker wrote on 2021-05-10, 12:18:

I'm not familiar with the stock drivers for that card. However UNISOUND should support it. UNISOUND - Universal ISA PnP Sound Ca […]
Show full quote

I'm not familiar with the stock drivers for that card. However UNISOUND should support it. UNISOUND - Universal ISA PnP Sound Card Driver for DOS v0.81b
Note that the readme says

Anyway as this tool is launched after config.sys, if you want CD-ROM support you'll have to load CD driver (like vid […]
Show full quote

Anyway as this
tool is launched after config.sys, if you want CD-ROM support you'll
have to load CD driver (like vide-cdd.sys) with device driver loaders
like DEVLOAD after Unisound IDE port activation.

Maybe that's the issue you're having wit hthe stock drivers as well? That they initialize the card after the cd driver tries to do its thing?

I think the devload referred to is here: https://www.infradead.org/devload/, which should let you load oakcdrom later.

Incidentally, the project write up is quite funny. Essentially an exercise in trying to get around college IT restrictions to be able to run Adobe Type Manager, and then submitting it as their A-Level project.

snufkin wrote on 2021-05-11, 13:34:

It is also possible that the soundcard gets everything initialized due to the onboard eeprom and some plug'n pray magic and that the seperate driver screws it up and misconfigures the crystal chip, thus making the cdrom inaccessible.

Maybe, maybe.
Also, in the configurator there is and option like Override PnP BIOS and '/o 'following the initializator in the config.sys is responsible for that.

Have tried to initialize it with unisound. Still the same, sound works, but ' No device found' when trying to set up the CDROM

But I think I know what can cause a problem with unisound. It says 'Loading Unisound default settings. And the IDE is disabled by default. I've put 'C168' in the 'SET BLASTER' line but it seems to ignore it.

Ok, so what's your autoexec.bat looking like now? And what does unisound /r output (should read the current settings)? Are you using devload to load oakcdrom.sys after running unisound? I notice in the unisound.txt instructions that it sets up the IDE IRQ based on the address. Given Win98 had the CDROM using IRQ 11 then it might be worth trying forcing the address to 1e8 as that would apparently be the normal base address for an IDE controller on IRQ 11 (tertiary controller would be 168/10, quaternary 1e8/11, according to random internet page).

it worked with 1e8/11. Now the CDROM works

Also, I've noticed that it works only with atapicd.sys. Both vide-cdd.sys and oakcdrom.sys crash the PC.

Bernkastel7734 wrote on 2021-05-12, 12:55:

Also, I've noticed that it works only with atapicd.sys. Both vide-cdd.sys and oakcdrom.sys crash the PC.

Yay! Sort of. Wonder why that happens. Still, good enough for the moment.

Could you post your config.sys and autoexec.bat so that if anyone else has a similar problem then they don't have to read through the whole thread?

Okay, so the entires in autoexec.bat are:
SET BLASTER =A220 I5 D1 H1 P330 C1E8
[path]UNISOUND.COM /V80
[path]DEVLOAD.COM [path]ATAPICD.SYS /D:CDROM
[path]MSCDEX.EXE /D:CDROM

And config.sys does not contain any changes.

Bernkastel7734 wrote on 2021-05-12, 13:31:

Okay, so the entires in autoexec.bat are: SET BLASTER =A220 I5 D1 H1 P330 C1E8 [path]UNISOUND.COM /V80 [path]DEVLOAD.COM [path]A […]
Show full quote

Okay, so the entires in autoexec.bat are:
SET BLASTER =A220 I5 D1 H1 P330 C1E8
[path]UNISOUND.COM /V80
[path]DEVLOAD.COM [path]ATAPICD.SYS /D:CDROM
[path]MSCDEX.EXE /D:CDROM

And config.sys does not contain any changes.

Where did the atapicd.sys file come from?
Just wondering if it might be useful for @matskatsaba, 286 16mb ram, cdrom driver issues who is trying to get an atapi cdrom working on his 286 with more than 4MB of ram 😀

weedeewee wrote on 2021-05-12, 14:21:

Where did the atapicd.sys file come from?
Just wondering if it might be useful for @matskatsaba, 286 16mb ram, cdrom driver issues who is trying to get an atapi cdrom working on his 286 with more than 4MB of ram 😀

https://www.hiren.info/downloads/dos-files