DOSBox works on Win2000. You probably have to reinstall your OS.

I have reinstalled twice, without solving the problem. It does work, but only after giving the message box 17 times. I was hoping there would be a more rigorous and elegant solution.

Thanks anyway. I guess I really should just use one of the Linux boxes, but I like my PC to be useful for something.

Regards,
Toad

Sounds like you are installing something that messes things up, or some service packs are needed.

I'm running vanilla W2k SP4. All I use it for is dvd ripping, because there isn't a decent linux ripper. I keep meaning to install virtualbox to maintain access to my ripper without having to have a PeeCee around, but there's always something else to do.

The problem appeared when I installed 0.70, about a year or so ago, I think. I assumed it was a change in the USER.DLL when w2k support was dropped by M$. Presumably the winxp USER.DLL file has the entry point that mine lacks.

Thanks, I was hoping this was something someone else had seen and there was an easy fix.

As the author, could you direct me to the 0.65 download? If I confirm that the error doesn't appear there, that would tend to indicate a change in DOSBox, whereas if the problem remains the same, it would tend to be some problem on my machine.

It's on the Sourceforge page (about 3 more clicks than the current). I wouldn't want to use that however...

Check the drivers for whatever input devices you use.

All versions of DOSBox work fine on Windows 2000.

Also verify you don't have any other sdl.dll files in your path variable.

OK, I went to the dosbox.sourceforge.net page, went to "Other Versions", but the only one listed there is 0.74.

As far as drivers, I have a vanilla keyboard and a logitech trackball. I have no other input devices. I'm unix/linux, and I don't know how to check the path on a PeeCee looking for sdl.dll files, nor do I know what they are. Can you sell me a clue on how to check for it/them?

Thanks,
Toad

Use 0.74, check your directx version and other drivers and read DosFreak's reply (if you don't know how to check the system path variable try google).

PATH: C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\WBEM;C:\Program Files\Common Files\Roxio Shared\DLLShared

which I think means I have nothing that isn't standard except Roxio. In the C:\Program Files\Common Files\Roxio Shared\DLLShared folder, there is no DLL called sdl.dll.

DirectX Version: DirectX 9.0c (4.09.0000.0904) DirectX diagnostics even say I don't have any input devices, but of course that means DirectX devices. Either way, no DLL to mess things up.

Microsoft Windows 2000 Professional (5.0, Build 2195)

Thanks,
Toad

Could anyone tell me where I can download the 0.65 version of Dosbox? I am aware of the opinion that all versions of Dosbox will work with Win2000, but I am having an error and would like to compare what I am seeing in 0.70 and 0.74 with the 0.65 version which did not show the error.

I appreciate the suggestions for what might be the problem, but since that hasn't solved it, I'd like to continue the troubleshooting process. That requires the last version that I personally had working just for comparison purposes. I am not suggesting that anyone is wrong in their opinion about whether 0.74 should work for me - I just want to determine if my memory is fading or not.

Please, it's a simple thing. I just want to test an old version. Anyone have a link? I'll leave an email address, if someone would rather just send me a copy instead of going through the trouble to create a link somewhere.

Thanks,
Toad

toadbrooks wrote:

OK, I went to the dosbox.sourceforge.net page, went to "Other Versions", but the only one listed there is 0.74.

There is a folder called "DOSBox" below of it, with sub folders of older ones..

Well i don't know about win2000/dx specialities but

DirectX diagnostics even say I don't have any input devices

sounds pretty broken itself and no matter what old version you try it won't work without a recognised mouse/keyboard.

sounds pretty broken itself and no matter what old version you try it won't work without a recognised mouse/keyboard.

Like I said previously, " I have a vanilla keyboard and a logitech trackball", and, " DirectX diagnostics even say I don't have any input devices, but of course that means DirectX devices." The final statement was in response to the question of whether a DLL was messing my system up or not.

I can use the vanilla beyboard and trackball just fine, and if I couldn't, I wouldn't be asking questions unrelated to that issue (or for that matter asking questions at all, since I'm using the keyboard DirectX says doesn't exist to type this response.)

Look, I'm just a newbie and maybe I don't have the right to DARE to suggest there might be anything wrong with Dosbox. But, "sounds pretty broken itself and no matter what old version you try", isn't helpful at all, unless you are just trying to get rid of me. Feel free not to help me any further. Someone else was kind enough to give me the link to 0.65. My ability to do testing is adequate, I will uninstall 0.74, install 0.65, report the results here, and that will be it.

There is no "opinion" of DOSBox working on Windows 2000. You are talking directly with the developers and beta testers of DOSBox.

Run sysinternals autoruns and disable any startup devices that have to do with input (Likely any logtech BS) and then reboot

Also run sysinternals process explorer and/or debug dosbox.exe with Dependency Walker to find out what is causing this error.

If those don't work then the only other option is to:

Try a fresh install of Windows 2000 (yes format the hard drive) and then SP4 and all updates. DO NOT install ANY drivers. Now try DOSBOX.

Look, I started programming professionally in 1977. I know how often users complain about an error in the code when it's just something they did. But I also know that software developers are absolutely sure that their code is 100% perfect and has no bugs at all, even though Nicholas Wirth's famous quote says, "All non-trivial software has at least one bug in it."

I am not trying to rain on your parade. I know WD and HAL are authors of the project. Maybe their fecal matter doesn't stink ... or maybe I've found a bug no one else has, and sticking your head in the sand and hoping I'll go away IS NOT a good solution.

I have NO logitech drivers loaded. Win2k recognizes my trackball without any help. Later this evening I will reload everything from scratch. Then I'll load 0.65 for MY testing. You can stick your figers in your ears and pretend I didn't say that, if it will help. THEN I will install 0.74. If the error still occurs, I'll take a screenshot. That will be it. I have no axe to grind. I'm not trying to suggest anyone made a mistake. I'm jsut saying, if you aren't interested in HELPING, please don't write me back.

Look, Dosbox 0.74 WORKS for most users with Windows 2000, I just checked this. No error at all. So this problem is limited to your explicit system. Contrary to what others wrote above, you should use the latest drivers for all your hardware. The problem could very well be with the drivers provided by MS. If it still persists, use Process Explorer by Sysinternals (Microsoft) and make sure that dosbox is really using the correct SDL.dll.
Alternatively, download Exult, http://exult.sf.net and see if that exhibits the same problem (it uses a newer SDL.dll). Exult requires Ultima7 to play but will start without U7 anyways.
The reason why everyone is against you using ancient 0.65 is that it is just that, ancient, too many things got fixed in the meantime...

even though Nicholas Wirth's famous quote says, "All non-trivial software has at least one bug in it."

All respect to Wirth but I prefer PEBCAC for a much higher hit ratio.

Maybe their fecal matter doesn't stink ...

Er what?

You can stick your figers in your ears and pretend I didn't say that

I think there are way more than enough pointers in this thread for you to try,
with the most relevant that "it works for others just fine". So you just have to
figure out if your directx is messed up, if your ancient win2k is plain missing some
ie support libraries or windows patches. None of which couldn't be done on your
own with a little thinking rather than posting crap in this thread.

DOSBox 0.74 works just fine on my crappy old Win2k. In fact, official DOSBox builds doesn't even use the GetRawInputDeviceList() api.

Please just debug DOSBox in Dependency Walker, like DosFreak suggested, and you probably will find the module that is causing your problem in no time.

TheOdds: In fact, official DOSBox builds doesn't even use the GetRawInputDeviceList() api.

Thanks, although I don't think that is true, it did help me track down the problem.

IIGS_User: There is a folder called "DOSBox" below of it, with sub folders of older ones.

Thanks for your help. I was able to download it, and what do you know? It worked without the error. I guess the guys who wrote it aren't as smart as they think they are. Anyway, I did only want 0.65 for testing purposes, so I have to go back to figuring out why 0.74 doesn't work and 0.65 does.

Dominus: Contrary to what others wrote above, you should use the latest drivers for all your hardware. The problem could very well be with the drivers provided by MS. If it still persists, use Process Explorer by Sysinternals (Microsoft) and make sure that dosbox is really using the correct SDL.dll.
Alternatively, download Exult, http://exult.sf.net and see if that exhibits the same problem (it uses a newer SDL.dll).

Thanks for that post. Never heard of exult, but in searching for errors exult users were experiencing, I did find the solution. Here's the gist:

GetRawInputDeviceList is an entry point in user32.dll. Windows stores instructions for graphical elements such as dialog boxes a […]
Show full quote

GetRawInputDeviceList is an entry point in user32.dll. Windows stores instructions for graphical elements such as dialog boxes and windows in the User32.dll file. The User32.dll file is necessary to the operation of Windows. If this file is damaged, deleted, or removed, the system will no longer work correctly. If a program or a service accesses User32.dll incorrectly, the program or the service will not work correctly.

User32.dll errors are typically corrected by repairing the User32.dll file or by reinstalling the program, the hardware component, or the driver that is causing the error. If these procedures do not correct the User32.dll error, you can restore your computer to a condition before the error appeared by using the Windows System Restore feature.

Re: Constant Errors in windows 2000 pro SP4
directX issues with windows 2000 are a rather known problem that i discovered lately; the fact is, one must install SP4 and the patches (especially the KB824141) before installing directX 9.0b, else you get the problem you have specified above. you will probably have to do a fresh install of 2000.

Not quite true. What I found was that I could reapply the KB824141 patch, then reinstall DirectX. Everything works after that. No reload the OS, no unplug everything an don't load any drivers, no other GUESSES by people who ought to be more informed about the package they wrote.

HAL: DOSBox works on Win2000. You probably have to reinstall your OS.
Dosfreak: Try a fresh install of Windows 2000 (yes format the hard drive) and then SP4 and all updates. DO NOT install ANY drivers.

That like asking someone to reboot. You know and I know that's not actually helping someone debug a problem. It's what you say when you don't give a damn about their problem. I SINCERELY hope you find yourself in a bind someday with a software package and you get the same answer, so you'll have a chance to recognize how useless that is.

wd: All respect to Wirth but I prefer PEBCAC for a much higher hit ratio.

Yep, I agree with you there. The problem was the TITANIC EGOs of the authors and beta testers between themselves and their keyboards. Problem SOLVED in spite of you trying to prove how smart you are and how little I knew.

So, I am blocking this thread and putting this base in my spamblock. Please remove my account. I have no desire to be associated with a group that requires ass-kissing before they will deign to answer simple questions. It's too bad that a really good program like DosBox hasn't got people who can get their ego out of the way enough to help their users.