VOGONS


First post, by rz8472

User metadata
Rank Newbie
Rank
Newbie

Per the guidelines, here is a list of my system stats -
1. Motherboard: No idea
2. Processor type and speed: Intel Core Duo T2050 1.60GHz
3. Amount and type of RAM: 2048 MB PC5300 DDR2
4. Video board w/ RAM amount and type: ATI Radeon X1300 256MB
5. Sound board: SigmaTel Audio Integrated
6. Operating system: Windows XP
7. Game name: Loadstar, The Legend of Tully Bodine (PC Version)
8. Description of problem: See Below
9. Reproducibility of problem: Always
10. Sound mode used: I don't know actually, new to this sort of thing
11. Video mode: Direct3D
12. Version of emulator: Dosbox 0.72
13. Steps already attempted to solve the problem: Tried to google "cd-rom thread went to sleep", no results

Ah Loadstar... I remember fondly getting one of those free demo CDs at Compusa and decided to buy the whole game from EBay since it was cheap and for nostalgia's sake. Unfortunately it seems to be one of the most incompatible games out there for DOSBox, and there are actually two problems when running this in DOSBox

The first is that setup.exe fails to save any sound settings even though it says it has automatically detected your sound settings - I'm assuming that Loadstar will copy several KB of user settings onto your hard drive similar to what TIE Fighter did, but it does not autorun or do anything of the sort.

The second and big problem is that upon running the actual game, I get the rocket science games "Loading" screen only to find a "cd-rom thread went to sleep" error, which occurs consistently.

Any insight would be greatly appreciated

Reply 1 of 14, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

one of the most incompatible games out there for DOSBox

And you're absolutely sure your mounting is correct, yes?

Reply 2 of 14, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Read my 60 Seconds Guide to DOSBox.

If that doesn't help, come back with details on how you mounted your C and D drives, how you did the install, how you configured sound, music etc.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 3 of 14, by rz8472

User metadata
Rank Newbie
Rank
Newbie

I did this -
mount C D:\Loadstar
mount D E:\ -t cdrom -ioctl

Now the sound issue is resolved, but the "CD-ROM thread went to sleep" error still persists. I read in an earlier thread that some people were able to get it to work at 2000 cycles (and it does when I try it), but it goes at 1FPS and is completely unplayable.

Cadillacs & Dinosaurs - system timer 2 error

Reply 4 of 14, by ADDiCT

User metadata
Rank Oldbie
Rank
Oldbie

I have the game somewhere, but can't test now (no time). You could try to create images (ISO or BIN/CUE if the game uses CDDA tracks), and mount them with the "imgmount" command.

The other thread is quite old, there have been a lot of improvements in DOSBox since 0.65. The information in that thread might be obsolete.

EDIT: game doesn't work properly with 0.72. I've tried the CD and an ISO image with various parameters, dynamic/full core, and various cycle settings. With all variations, i get the "CD-ROM thread went to sleep" message, and the game exits. When setting the cycles to "2000", the game will get past the "CD-ROM thread went to sleep" message, and will display a message saying that the video speed is below the recommended minimum. After proceeding, the game hangs. There are no error messages in the DOSBox console. I couldn't find any updates for the game, and DOS/32A can't be used instead of the DOS4GW executable on the disc (DOS/32A error message).

This is one of a handful of games i couldn't get to work in DOSBox. Damn you, Tully Bodine!

Reply 5 of 14, by pjpsyco

User metadata
Rank Newbie
Rank
Newbie

<- guy from last thread

I tried it again on dosbox 0.72, and it works as before at 2000 cycles. I found that if I sped up the cycles during the actual game (just after hitting the mattresses) to 5000 it was playable until I died the three times returning to the screen that needs 2000 messed it up. It seems to be the level selection screen that is the problem.

I suspect the way to fix this would be to make the video prompt at he beginning happy by dedicating 3000 of of dosbox's cpu cycles to the video card, and 2000 to the rest of it (or something to that effect). Sadly, as before, I am not a programmer, and do not know how to do this.

Reply 6 of 14, by 06metzp

User metadata
Rank Newbie
Rank
Newbie

Sorry to hijack the thread, but it looks like this one hasn't been used in a little while, and also looks like my issue is directly related to the existing discussion.

I'm trying to get the Rocket Science game "WingNuts" to run on my laptop here, and I'm getting the "CD-ROM thread went to sleep" error as well. I'm using DOSbox 0.72 and tried running the game both directly from the CD and from an ISO image of the cd. I have to run the game as "loadhigh wingnuts" otherwise I get a memory error. When I do it this way it runs through the loading screen but then gives me the error.

help?

Reply 7 of 14, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Problem is these games seem difficult to acquire...

1+1=10

Reply 8 of 14, by 06metzp

User metadata
Rank Newbie
Rank
Newbie

I managed to snag a copy off of Amazon.com recently. I was glad to find it because WingNuts used to be one of my favorite games and I had lost the disc. It's the version published by SoftKey but the disc contents should still be the same.

actually, there are still two copies up for sale:
http://www.amazon.com/gp/product/B000MP0YHW

Reply 9 of 14, by KingOfApoc

User metadata
Rank Newbie
Rank
Newbie

I actually looked into reading Loadstar.exe from the CD-ROM in a Hex Editor and came across some interesting text:

SET ROCKET=(options) to override the default CD-ROM calibration, where:. C[1-99].Percentage of time to spend reading the CD. D[0-255].Delay in milliseconds between reads. F[0-1].Should reads go through the DOS file system?. P[0-1].Should reads be preempted

Then in DosBox I typed SET ROCKET=C99 D255 F1 P1
Loaded loadstar.exe and it skipped the launch screen but then I got the fatal error: CD-ROM thread went to sleep error.

Perhaps there is a way to get past this error message by setting the correct values?

Reply 10 of 14, by rcblanke

User metadata
Rank Oldbie
Rank
Oldbie

Advanced Galactic Empire, Wingstar and Tully Bodine are all working in CVS

Reply 11 of 14, by KingOfApoc

User metadata
Rank Newbie
Rank
Newbie

Oh goodie, I just tried it out, and it works...

Thanks

Reply 12 of 14, by S£CTOID

User metadata
Rank Newbie
Rank
Newbie

That sounds awesome, wich CVS ?

Reply 13 of 14, by kolano

User metadata
Rank Oldbie
Rank
Oldbie

I can concur with RCBlanke that this does work with current DOSBox revs, (i.e. .74 and newer SVN releases, possibly .73 as well) however...

Video Bugs:
• The intro video (and likely elsewhere) suffer from an odd palette flickering, where a few, likely-edge palette colors vacillate between incorrect colors. Thankfully such is addressed by use of the "vgaonly" machine type.

Variable Cycle Speed Issues:
• It appears to require fixed cycles to run reliably without a "Fatal error: clock malfunction in disk calibration" error.
• The cycle rates mentioned earlier here and elsewhere (i.e. 2000-3000) are generally too low for a game released in 1995. A higher value (30000-50000) works significantly better for me to resolve the clock malfunction errors. However, your PC must be able to run the emulation at that rate, so a somewhat lower value may be appropriate for slower machines.
• The parameters mentioned by KingOfApoc seem like another promising route to solve this issue, but I haven't had a chance to play with them. I remain interested in hearing more regarding folks tests with such.

Reply 14 of 14, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well, games that do some sort of speed calibration will have a difficult time with autocycles as the speed changes all the time. The 2000-3000 cycles were a workaround for a timer bug that has been fixed. vgaonly is meant for just these cases where the palette is changed on-screen.

1+1=10