First post, by megatron-uk
I've just restored a Thinkpad 240 with a broken screen and am having a difficult time getting sound working correctly. This has an ESS Solo 1E (ES1946) onboard and an Intel 440DX chipset. The Thinkpad BIOS has almost no options for managing resources, but I have disabled IRDA, serial and parallel ports to free any assigned interrupts. The only other option is under "PCI" and has an option to assign an IRQ to the "1st", "2nd", "3rd" and "4th" PCI devices - though no indication on what each of those devices are.
FM seems to work regardless of what driver I use (ESSOLO.SYS, ESSOLO.COM - v212Y and v321D, the pciset technique), so I did think it was all working.... but I observe the following other issues:
- ESSOLO.SYS: No errors during loading (shows "SOLO") when the driver is loaded. FM works, but doesn't appear to do anything else (no effects/digital output).
- ESSOLO.COM: initialises the card according to what I set in c:\essolo.ini; and shows a success message about the configured resources, but the system immediately locks up after it loads; the C:\ prompt and cursor return, but no input is possible.
- Changes to essolo.ini to affect DDMA, TDMA or PC/PCI make no difference to the behaviour (the mode is correctly shown in the output of essolo.com) - I don't know what implementation IBM have got on the 240 motherboard, so have tried all 3 options
- Changes to assigned IRQ (tried both 5 and 7) makes no difference
If using the pciset technique everything seems to run okay (and unlike ESSOLO.COM - it doesn't lock up), but once you run an audio setup tool (like Duke3d setup.exe) FM works, but testing the effects shows an error about initialising the card and possible dma/address error. Hard setting the values in something like Doom will blow up DOS4GW runtime part way through loading.
All of the above have been tried with various combinations of blank config.sys, with himem.sys and with himemx (in case it was a memory manager issue). There appears to be no difference, which leads me to believe it's not anything to do with any of those DOS components, and instead a hardware resource/hardware configuration issue.
Anyone with a Thinkpad 240 able to get the Solo-1E working properly in plain old DOS?
My collection database and technical wiki:
https://www.target-earth.net