Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using Delphi 5 to develop Apps for XP

Status
Not open for further replies.

MojoJojoFan

Programmer
Jan 30, 2007
3
US
Some of my multithreaded apps work, others do not but can by throttling back the number of background threads to 2. Is Delphi 5 not meant to develop applications for Windows XP?
 
I think D5 is not the problem, it depends how well you implemented the multithreading aspect.

can you explain what your app does and maybe show us some code?

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Hey Daddy,

Thanks,

I think you answered my question. I have had other people ask me the same question and thought D5 did not work well with XP.

My application starts a thread that in turn starts "n" number of threads. Each of these threads logon to a different database along with a master database executing queries, updates, deletes, and inserts all connecting using the DOA (direct Oracle Acess) from Allroundautomations. It's too much to go into in this forum. It works on my 2000 machine but not others on a different network. It runs if I limit the background threads to 2 on those other machines but not at all on XP.

Thanks,
 
I'm running D3 just fine in XP, along with everything I've tried in it.

Just thought I'd note that: anything that's 32-bit and was supportable under Windows NT should be fine in XP.
 
the thread 'model' used in D5 cannot be at fault, because all thread code used in Delphi in all versions are simply wrappers for the Windows API thread code. ie. Delphi simply makes it easy for you to use the Windows API thread model.

So what you're facing must be something that the WinXP machine is doing differently with threads than the other machine.

First guess would be that you have not properly implemented your threads and they're conflicting, and you're only seeing this because the WinXP machine is faster or slower and so the threads are conflicting differently on that machine.

My second guess would be that it has nothing to do with the threads at all, and possibly an authentication issue with the databases.

Post some code if you can - it will really help us help you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top