Problems with WHDLoad on a CDTV

[jtorrance]

Hi!

I'm trying to use WHDLoad on my CDTV, but I had the same problem with every game I tried so far (Wings of Fury, Turrican 2 CDTV, Xenon II, Apidya, Hybris).
The game starts, the initial screen/logo is displayed, then the image freezes, while the music plays in the background. I can use the quit key to leave the game. If I try to start the game a second time, the CDTV freezes with a black screen. Sometimes the CDTV even freezes on the initial start.
I tried several options (chipnocache, noautovec, nommu, pal/ntsc), but the problem remained the same. I tried to free more memory by using addbuffers but I don't think memory is an issue here (see below).
It is very similar to the problem described in this (unresolved) thread: http://eab.abime.net/showthread.php?t=22166

The CDTV is outfitted with:
- 68020
- 2 MB Chip RAM
- 8 MB Fast RAM
- 1.8 MB Slowmem (BogoMem? I'm not an expert...)
- SCSI Controller with 2GB HD
- Kickstart 3.1 and 1.3

I tried to disable as many upgrades as possible, but it didn't work. In the end I only used the 2MB Chip RAM on a 68000 with Kickstart 1.3. The SCSI controller has to be active all the time, since I need the HD. The CDROM has to be active since the SCSI controller depends on the CDTV-only stuff.

Are there any CDTV-related problems known, or is there at least anyone who can confirm/deny that WHDLoad does work on a CDTV?

Thanks
Kevin

[killergorilla]

Do you have a keyfile?

[jtorrance]

Hi!

None that I know of. I just downloaded whdload from its website. Do I need one?

Thanks
Kevin

[musashi5150]

You don't "need" a keyfile but you should register if you haven't. Trouble will find you quickly though if you are using a "borrowed" keyfile ;)

[killergorilla]

The reason I asked was because sometimes you get similar problems if you are using a dodgy keyfile but as you aren't I can't help!

Sorry!

[jtorrance]

OK, thanks anyway. I will gladly register, as soon as it works. At the moment it doesn't make too much sense to pay. Except for the reason that the nag screen is really becoming annoying since I have to
1. Boot
2. Start game
3. Wait for nagscreen
4. See game crash
5. Goto 1

Where 3 is the one that takes the longest ;)

So is there nobody who ever tried to use whdload on a CDTV?

Kevin

[MrZammler]

So is there nobody who ever tried to use whdload on a CDTV?

Kevin

Yes, me, but cant help. I was actually considering these days to get a 68010 for mine, hoping that it would fix something. But seeing that yours with 020 does the same, I wont be getting one...

I've given up on this, let me know though if you manage to get something working.

[jtorrance]

Yes, me, but cant help. I was actually considering these days to get a 68010 for mine, hoping that it would fix something. But seeing that yours with 020 does the same, I wont be getting one...

I've given up on this, let me know though if you manage to get something working.

So you are having the exact same problem on a CDTV? Well so at least we know that it is very probably a problem with the CDTV. Next week I'll try some other stuff like booting WHDLoad from a floppy with the CDROM disabled. In that configuration the CDTV should behave like a normal A500. If that works it should be pretty clear that it is the cdrom driver causing the problems. Maybe the developers can find a way around this problem.
Dont't give up hope ;)

I'm surprised that so few people tried using WHDload on a CDTV. There is practically no information available on the net for this configuration.

Kevin

[jtorrance]

Oh I forgot, there is somtimes another symptom. After starting WHDLoad the Floppy starts to rattle and the CDTV's power LED blinks with the exact same 'rhythm' as the floppy rattles. After that some graphic and sound artifacts appear and that's it.

Kevin

[Wepl]

I have no CDTV for testing.
Because WHDLoad requires Kick2.0 and the CDTV has factory Kick1.3, I think there are less people who have ever tried it.
The game starts, the initial screen/logo is displayed, then the image freezes, while the music plays in the background. I can use the quit key to leave the game. If I try to start the game a second time, the CDTV freezes with a black screen. Sometimes the CDTV even freezes on the initial start.
This sounds like an Interrupt problem.
It would be interesting to see the Interrupts window output of Scout here.
You may try the WHDLoad option ReadDelay=200.
You should also try other games, especially some which use kickemu.

If you have a floppy drive, take a small game/demo and make a bootable floppy and start whdload from the floppy booted. That could show if the cd/scsi is the problem.

[MrZammler]

Hmm, you also have a 2GB disk? You could then disable the onboard cdrom with a jumper somewhere I think:

"To do this, open the CDTV up, and remove the jumper on JP15, which is nearthe front centre of the CDTV. Removing this jumper disables the CDTV functions,placing it on the left two or right two pins (it doesn't matter which) will enable the CDTV functions. "

Check if games work then, so it should indicate a problem with the cd rom drive functions.

[Toni Wilen]

Hmm, you also have a 2GB disk? You could then disable the onboard cdrom with a jumper somewhere I think:

"To do this, open the CDTV up, and remove the jumper on JP15, which is nearthe front centre of the CDTV. Removing this jumper disables the CDTV functions,placing it on the left two or right two pins (it doesn't matter which) will enable the CDTV functions. "

Check if games work then, so it should indicate a problem with the cd rom drive functions.

CDTV SCSI expansion's driver is in extended ROM that JP15 disables..

[MrZammler]

CDTV SCSI expansion's driver is in extended ROM that JP15 disables..

Oops, didint know that, thanks for the info.

[Toni Wilen]

Here is some techical information that may or may not help.. (I probably do more testing when I have time to finish my real CDTV upgrades.. It will become WHDLoad game machine someday..)

CDTV CD hardware uses interrupt level 2. It has 2 different interrupt sources, DMAC and 6525 ("Tri-Port interface", CIA-like io/interrupt controller chip).

Both probably needs to be disabled for compatible WHDLoad support.

I think CDROM drive can trigger "random" interrupts anytime, also DMAC status may need to be checked, CD driver apparently does some kind of prefetching (you don't want kill system when DMAC is still DMAing data)

I can post some code that disables, and also can re-enable them correctly, interrupts later.

DMAC is used by CD and SCSI expansion (basically makes it A590 but A590 driver does not work because CD is also connected to DMAC. CD drive is not SCSI)

[Toni Wilen]

Sending CMD_STOP to cdtv.device seems to disable 6525 interrupts, and CMD_START re-enables them.

Perhaps this fixes the problem (as long as DMAC is idle)

[jtorrance]

Hi!

Wow, what a discussion. Thanks for the feedback.

I found a game that actually works (even with CD enabled ) : 'Transplant'
I found two games that work only when the CD is disabled: Demo of 'Tensai' and 'Turrican'.

But all of them only work when the 68020 is disabled. Do other games that would normally run on an A500 need the 68020 when run with WHDLoad? If not I will have the upgrade disabled for all further tests.

All of these tests were done with an empty (non-existant) config file and no other options except the ones in the slaves' info files. I booted WB3.1, copied WHDLoad and the slaves to the ram drive, then started them.

I didn't have the time to test other games from floppy, but will do so tomorrow.
Maybe the current data (especially the game that works even when the CD is enabled) will help you identify the problem.

I installed Scout, but didn't actually know what to do with all the information. If you give me directions, I'll gladly help testing.

How can I send that command to the device? Sorry, if this is a stupid question, but I'm not familiar with amiga internals.

Thanks alot
Kevin

[Wepl]

Sending CMD_STOP to cdtv.device seems to disable 6525 interrupts, and CMD_START re-enables them.

Perhaps this fixes the problem (as long as DMAC is idle)
Thanks for the info Toni. I will create a test version which includes that.

[Wepl]

I found a game that actually works (even with CD enabled ) : 'Transplant'
I found two games that work only when the CD is disabled: Demo of 'Tensai' and 'Turrican'.

But all of them only work when the 68020 is disabled. Do other games that would normally run on an A500 need the 68020 when run with WHDLoad? If not I will have the upgrade disabled for all further tests.
All OCS games should work on a 68000 if not stated otherwise in the ReadMe. But as all devs use a 68020+, therefore installs are usually not tested on a 68000...
All of these tests were done with an empty (non-existant) config file and no other options except the ones in the slaves' info files. I booted WB3.1, copied WHDLoad and the slaves to the ram drive, then started them.
Running from RAM will make no difference, but ok if you use FFS.
You should try READDELAY as I already wrote.
I didn't have the time to test other games from floppy, but will do so tomorrow.
Maybe the current data (especially the game that works even when the CD is enabled) will help you identify the problem.
The list of games which run/not is a bit short for that. But it can help if there is some idea where the problem is.
I installed Scout, but didn't actually know what to do with all the information. If you give me directions, I'll gladly help testing.
Open the Interrupts window, press Print, select a file and post the contents of the file here.
How can I send that command to the device? Sorry, if this is a stupid question, but I'm not familiar with amiga internals.
I dont know a tool which allows you to do that. I will add this to WHDLoad itself.

Also do the following:
Get http://aminet.net/package/util/misc/SetCPU and run SetCPU CHECK 68020 I like to see if it brings "FPU Logic Error".
PM me a .whdl_register file. Make a Coredump for that with Transplant and EXPERT, DEBUGKEY=$xx (see docs).

[musashi5150]

But as all devs use a 68020+, therefore installs are usually not tested on a 68000...
Except for me :laughing

[jtorrance]

Running from RAM will make no difference, but ok if you use FFS.

I just copied the slaves to the ram drive to simulate the speed of the hd. I thought it was a good idea. ;)


You should try READDELAY as I already wrote.
I tried the READDELAY option when in CDTV mode and had no luck with it. When in non-CDTV mode all (three) tested games worked, so I didn't see a need for testing it.


The list of games which run/not is a bit short for that. But it can help if there is some idea where the problem is.
I will test a few more games tonight.
You recommended to test games which use kickemu. Will that help diagnosing the current problem? Anyway, I'll test some if I find them.


Open the Interrupts window, press Print, select a file and post the contents of the file here.

Also do the following:
Get http://aminet.net/package/util/misc/SetCPU and run SetCPU CHECK 68020 I like to see if it brings "FPU Logic Error".
PM me a .whdl_register file. Make a Coredump for that with Transplant and EXPERT, DEBUGKEY=$xx (see docs).
Ok, consider it done.

...Five minutes later...

Oh, I hope the files aren't too big because at the moment I can't think of any method to get the data to my PC. I normally burn CDs on my PC to get data to the CDTV, but the other way... Well, I think I'll just type it. The interrupt list shouldn't be too big, but a coredump seems to be something that is pretty large... Maybe I have a nullmodem cable lying around somewhere... OK, however, I'll find a way, but it may take some time.

Thanks
Kevin

[Wepl]

I will test a few more games tonight.
You recommended to test games which use kickemu. Will that help diagnosing the current problem? Anyway, I'll test some if I find them.
The kickstart/kickemu will usually better handle unknown interrupts then custom code. Therefore the result may be interesting.
Oh, I hope the files aren't too big because at the moment I can't think of any method to get the data to my PC. I normally burn CDs on my PC to get data to the CDTV, but the other way... Well, I think I'll just type it. The interrupt list shouldn't be too big, but a coredump seems to be something that is pretty large... Maybe I have a nullmodem cable lying around somewhere... OK, however, I'll find a way, but it may take some time.
I think the best would be a floppy drive, but nullmodem should also work.
It will be surely no fun to type the outputs. Better you make a picture then if there is no way to transfer the stuff.

I have added the cdtv.device commands as Toni suggested. Please try http://whdload.de/whdload/whd169cdtv.lha
Use option TRACE and check the .whdl_trace file created. It should contain a line with CDTV kludge.

[jtorrance]

Hi!

OK, I did a lot of testing (and typing).
I will try to get a little structure into all of this...

If I say 'CDTV mode' I mean that the CDROM and thereofore the SCSI controller and HD are enabled.

If I say 'A500 mode' I mean that all of that is disabled and the CDTV should in theory behave like an A500.

The output from setcpu:
SYSTEM: 68020 6881 (FPU LOGIC ERROR) (INST: CACHE)

If I understand correctly that's a problem with the expansion board itself, not with the FPU. This lead me to disable the MMU (and set the other options) in WHDLoad which lead to the 68020 working with WHDLoad.

These are the options used:

ChipNoCache
NoAutoVec
ReadDelay=200
NoMMU
PAL
EXPERT


And now for the games:

000=68000 used (with no options)
020=68020 used (with the new options (see above))
A500=A500 mode
CDTV=CDTV mode
Yes=YES, it works!!
No=Damn, it doesnt work...



Apidya: CDTV 020: No
Tensai demo: A500 000: Yes; A500 020: Yes; CDTV 000: No; CDTV 020: No
Tower Toppler: A500 020: Yes; CDTV 020: No
Transplant: A500 000: Yes; A500 020: Yes; CDTV 000: Yes; CDTV 020: Yes
Treasure Island Dizzy: A500 020: Yes; CDTV 020: No
Turrican: A500 000: Yes; A500 020: Yes; CDTV 000: No; CDTV 020: No


So, 'Transplant' is still the only game working in CDTV mode.

I made memorydumps from most of these tests (even when the game crashes I can often quit/debug it), but since I had to type or photograph it, I will only include the registers from Transplant and Tensai in both modes.
These are included in the attached zip file. Also included is the interrupt list.
Edit: Look a few posts below for the zip file.

I will now try some kickemu games and your new version. I'm not home over the weekend and I don't know if I have the time for all of that today.
If you need more memorydumps I will look for a pc disk drive and install crossDOS, so that I don't have to bug you with my low-quality digicam screencaps.

Oh, and I installed some games on the HD, and some show similar problems as the WHDLoad games. Syndicate comes to mind. It always stops during the intro. Maybe that is a related problem.

Thanks
Kevin

[jtorrance]

I have added the cdtv.device commands as Toni suggested. Please try http://whdload.de/whdload/whd169cdtv.lha
Use option TRACE and check the .whdl_trace file created. It should contain a line with CDTV kludge.

It only says "no CDTV detected" twice. Once before and once after resload.

[jtorrance]

Hi again!

... installing crossDOS... great idea, since it's already installed. For years actually. For years during which I burned a CD for every 10kb file I wanted to transfer to the CDTV... Well this should really cut down on my demand for new CDRs. ;)

However, I tested Monkey Island, which uses kickemu, but had no luck with it either. I could shortly see the OS1.3 screen. After that the screen went black.

I attached a new zip file containing the complete memorydumps from the first few games, from 'Monkey Island' and from my tests with the new version. This time as text files, not as jpegs ;)
I have to delete the old attachment, so if there's anybody who wants to see a photo of my TV screen: bad luck.

OK, I won't have access to the CDTV over the weekend, so I can't do any further tests. Answering to forums posts should be possible though.

Kevin

[Wepl]

thanks for testing...
there was a bug in the last whdload beta which has caused that the cdtv kludge hasn't become effective.
please try the new one http://whdload.de/whdload/whd169.lha
I have also fixed the cpu detection. With that whdload should no longer detect a 68030 for your (broken ;)) 68020 board.
I would like to see a .whdl_register and .whdl_trace file for any game.
The options ChipNoCache and NoMMU have no meaning for your system, you can delete them.

[jtorrance]

Hi!

Wow, that version works! I tested all the games mentioned above and they work. The only flaw I found is in Turrican where the intro screens disappear too fast before the animation is complete. But I can live with that.
I will run a few longer tests tomorrow. I will also send you the register dumps and the trace files (if you still need/want them) tomorrow.

What exactly was the problem? Is there any chance that the same problem causes my other HD installed (not whdload) games to crash? Well I think it doesn't really matter, since I can now run all those games via whdload.

I see a registration and a donation coming.

Thank you very much
Kevin

[MrZammler]

Great news!!

I will try this one on my cdtv these days and let you know!

Many thanks!

[jtorrance]

Hi!

I didn't have any time for long term tests yet, but if you still need them here are a few more traces and register dumps. All done with your new (working) version.
The 1MB version of Mortal Kombat 2 crashes, while the 2MB version works. I think this is more a problem of the slave than the CDTV but I included the completete memory dumps for those two... just in case.
EDIT: Forgot the error message: 'Exception "CHK, CHK2 Instruction" ($2018) at $309D8EA occured'
The CDTV line in the trace files is always "CDTV kludge with rc 0/0" right before and after resload.
All the games mentioned in the zip file worked, except MK2,1MB.

OK, now I'm off actually playing a few games to see if it's stable.

Kevin

[Wepl]

Wow, that version works! I tested all the games mentioned above and they work. The only flaw I found is in Turrican where the intro screens disappear too fast before the animation is complete. But I can live with that.
This is known problem with the Turrican install. Some day I will fix, a rework of this install is anyway planned.
What exactly was the problem? Is there any chance that the same problem causes my other HD installed (not whdload) games to crash?
The problem is the cdtv.device it seems. As the work around, a CMD_STOP to it, like it Toni has suggested solves it.
Other non WHDload installed games may or may not have the same problem. This depends on how the games initialize and setups interrupts. OS friendy games should work. But there also many games which replace the interrupt routines, these may fail.
I didn't have any time for long term tests yet, but if you still need them here are a few more traces and register dumps. All done with your new (working) version.
Thanks, thats enough for now :)
The 1MB version of Mortal Kombat 2 crashes, while the 2MB version works. I think this is more a problem of the slave than the CDTV but I included the completete memory dumps for those two... just in case.
EDIT: Forgot the error message: 'Exception "CHK, CHK2 Instruction" ($2018) at $309D8EA occured'
I think this is install specific.
The CDTV line in the trace files is always "CDTV kludge with rc 0/0" right before and after resload.
This means success.

[alexh]

Does this mean that you have to preload all slaves being run on a CDTV from a CD?

I mean "cmd_stop" prevents further CD access correct?

[Wepl]

Does this mean that you have to preload all slaves being run on a CDTV from a CD?
with the current whdload yes, if there is demand I could change it so that will be enbled/disabled on each switch
mean "cmd_stop" prevents further CD access correct?
I dont know, but for the scenario it makes no difference, it wont work after an switch

[alexh]

What do you mean by a "switch"?

[Wepl]

a switch between the operating system and the installed program

[alexh]

if there is demand I could change it so that will be enbled/disabled on each switch
Most CDTV users will have a vanilla 68000 and so wont be able to return to the OS and will have to reboot between games

[Toni Wilen]

Most CDTV users will have a vanilla 68000 and so wont be able to return to the OS and will have to reboot between games

I remember someone said slaves that don't exit on 68000 are considered broken :)

[musashi5150]

That sounds like Codetapper to me ;)

[MrZammler]

with the current whdload yes, if there is demand I could change it so that will be enbled/disabled on each switch

I dont know, but for the scenario it makes no difference, it wont work after an switch

Hmm, yes there is demand by me :)

Getting a cdtv to whdload specs (kick 2.0) is okay, but since I'm cheap I thought I'd skip the cost of the fast ram and just not preload games. :D

If it would be easy to implement, I'd be interested to test it if it would work (I only have 1mb chip on mine).

Eventually I will buy some fast ram for the cdtv, but if it could be easily implemented in software, it would be cool.

[alexh]

The cost of a RAM upgrade is only €70 you cheap skate ;)

CDTV 1Mbyte Chip RAM upgrade (http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120179763407)
CDTV 2Mbyte Fast RAM upgrade (http://www.vesalia.de/e_cdtvramexp%5B1009%5D.htm)

[MrZammler]

@alexh

Yeah, I know, too bad the 8MB fast is not available, but the 2Mb should be enough for most of them. :-)

[alexh]

too bad the 8MB fast is not available
I bet that you can buy a 2MB one and turn it into an 8MB one for less than the price of an 8MB.

It wont be more than just soldering on more / higher capacity ZIP RAM.

[thor]

Yeah, I know, too bad the 8MB fast is not available, but the 2Mb should be enough for most of them. :-)

You could order the 8MB version directly from Elbox


It wont be more than just soldering on more / higher capacity ZIP RAM.

Problem would be finding enough 1Mx4 ZIPs

[alexh]

Problem would be finding enough 1Mx4 ZIPs
Nah, you can get them in loads of places.

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120188672708

However I am now not sure that the CDTV/2 and the CDTV/8 are actually the same board sans chips as the CDTV/2 has it silk screened on.

http://amiga.resource.cx/photos/elboxcdtv2,ElboxCDTV2

But we are straying from topic.

[thor]

Nah, you can get them in loads of places.

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120188672708


Sure, you can get them (Softhut lists them too), but "loads of places" is a bit exaggerated ;)

However I am now not sure that the CDTV/2 and the CDTV/8 are actually the same board sans chips as the CDTV/2 has it silk screened on.I'm quite sure it's the same board and that you can replace the 16 256kx4 with 1Mx4 ZIPs. Here's a picture of Toni's 8MB version and I'm certain it reads CDTV/2 under the sticker ;)
http://img410.imageshack.us/img410/4216/8mbvz8.th.png (http://img410.imageshack.us/my.php?image=8mbvz8.png)

[rare_j]

Most CDTV users will have a vanilla 68000 and so wont be able to return to the OS and will have to reboot between games

IS the 68000 in a CDTV socketed like in the A500? In which case a quick-fix would be to drop in a 68010 which I believe supports returning to the OS.

[alexh]

a quick-fix would be to drop in a 68010 which I believe supports returning to the OS.
And screw up compatibility with CDTV games, just to be able to quit WHDload... yeah right.

[Wepl]

And screw up compatibility with CDTV games, just to be able to quit WHDload... yeah right.

I doubt that there will be many games which have problems. CDTV games are more compatible than floppy games and usually dont kill the the OS.

[alexh]

Is that why a lot of the early HD installs were of CDTV images?

[gibs]

Toni send me this tread as I'm one of those who wants to run games from CDTV.

My CDTV spect are : Cdkick 1.3 (1.3/3.0/CDTV) rom switcher.
Elbox CDTV/2 : Add 2MB of other RAM.

I don't own a harddrive so each time I try, I need to use one CDR.

The whdload version used is the 1.70

So, I can boot the Workbench and some games are working (from my notes : Pinball Dreams, Blood Money, Xenon 2 are working)

I don't want to build a CD with the maximum of games, but the ones that I really enjoyed in the past, and also the demos.

-There is one game which is cult that refuse to work : Shadow of the beast.
It load the intro, an when the floppy version would ask to insert the disk 2, nothing happen. the screen become black and the CDROM won't load anymore.

I did the same setting on my Minimig (1MB of CHIP, 1,5MB or Fast) same kickstart, same workbench, same whdload install game and I noticed that the game should continu to load. It feels like the CDROM from the CDTV is deactivated.

-I have another game that I like which is not working (Xenon 1) : Black screen.
-I have also tried Monkey Island 1 & 2 : Black screen.

If Wepl have a clue or a tips ?

[Boo Boo]

Toni send me this tread as I'm one of those who wants to run games from CDTV.

My CDTV spect are : Cdkick 1.3 (1.3/3.0/CDTV) rom switcher.
Elbox CDTV/2 : Add 2MB of other RAM.

I don't own a harddrive so each time I try, I need to use one CDR.

The whdload version used is the 1.70

So, I can boot the Workbench and some games are working (from my notes : Pinball Dreams, Blood Money, Xenon 2 are working)

I don't want to build a CD with the maximum of games, but the ones that I really enjoyed in the past, and also the demos.

-There is one game which is cult that refuse to work : Shadow of the beast.
It load the intro, an when the floppy version would ask to insert the disk 2, nothing happen. the screen become black and the CDROM won't load anymore.

I did the same setting on my Minimig (1MB of CHIP, 1,5MB or Fast) same kickstart, same workbench, same whdload install game and I noticed that the game should continu to load. It feels like the CDROM from the CDTV is deactivated.

-I have another game that I like which is not working (Xenon 1) : Black screen.
-I have also tried Monkey Island 1 & 2 : Black screen.

If Wepl have a clue or a tips ?

I probably wont be much help:)
You should test under WinUae, I did make an ISO a little while ago of MonkeyIsland 1&2 to run from CDTV using its own HDinstall

I dont know if there is a stange problem with the CDTV but when I tried running Titus Fox witch is ADos compatible from CD it just stops loading also a few other games, Maybe the CD buffers eat memory

[Toni Wilen]

I am quite sure the (simple) fix would be to call cdtv.device/CMD_START when re-enabling OS (so that CDROM hardware works properly again)

[gibs]

@Boo Boo I have tested with WinUAE/EUAE (With a CDTV profile), and the Minimig : games are working.
they aren't on the real (CDTV) device.
Ok for the HdInstall tips, but there should be lot of whdload still not working with the CDTV.

Toni: Who is going to do that ? Wepl ?

[Toni Wilen]

@Boo Boo I have tested with WinUAE/EUAE (With a CDTV profile), and the Minimig : games are working.
they aren't on the real (CDTV) device.
Ok for the HdInstall tips, but there should be lot of whdload still not working with the CDTV.

Toni: Who is going to do that ? Wepl ?

Someone who have whdload sources :)

Real CDTV CDROM drive most likely sends "random" status information messages when it is idle.

I haven't really examined CDTV's exact behavior because most (all) programs don't care. (or even see them, it is all handled in cdtv.device and all(?) cdtv programs are system-friendly, no direct hardware poking)

Of course no one must not depend on current CDTV emulation behavior because it will be improved sooner or later :)

[Boo Boo]

http://whdload.de/whdload/whd169.lha


I dont know if its worth trying this particular version of WHDload but you would think XENON 1 would Preload and the problem wouldnt exist not sure about SOB but games that are calling the OS alot I guess not.

Is there a one off shell comand for CMD_START and Stop

[gibs]

Only Wepl can tell us if it's better to use the 16.9 version.
Wepl himself gave me de link of the 1.70 version.

When I have burnt the CD I also put the 14.5 version of whdload as this is the version used in the unofficial compilation "CD200" but it also fail running SOB after the intro.

In comparison, Xenon2 (2 disks version) play the intro, but then succeed to run the second disk...

I'm a bit lost, and I don't have a HD on the CDTV to test different things: each time it cost 1 CDR. I tried tu burn in multisession, but it seems that the CDTV CDROM read only the 1st session. (I need to confirm that info, I only tried with one burning software, need to try with Nero)