Hi teddy, I ran into this exact same problem (on win2k using DBI and fork()) and eventually gave up. Alas. Someone more knowledgable will have to give us a definative answer but my primitive understanding is that fork() typically uses the system's implementation of the fork() command and that Windows doesn't have one :(
So, efforts have been made to implement it at the interpreter level with limited success. You might look into Win32::Process but I hear it's slow. I do know that perl6 is supposed to have robust thread support natively, but I don't know much about it. (again...any gurus that can help us?) check out: http://aspn.activestate.com/ASPN/Mail/Message/perl-win32-porters/1178773 and http://perlmonks.thepen.com/181655.html There seems to be a lively discussion on threadding and forking, etc. right here at perl.org on the perl-ithreads list. here's the archive: http://archive.develooper.com/[EMAIL PROTECTED]/msg88946.html Please let me (and all of us) know if you get to the bottom of this... Thanks and Good luck (we're all counting on you ;-) -Peter -----Original Message----- From: Octavian Rasnita [mailto:[EMAIL PROTECTED] Subject: Why this perl error? The error is: perl.exe - Application Error The instruction at "0x28068533" referenced memory at "0x00000004". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program OK Cancel I am running Windows 2000, Apache 2.4 web server, and Perl 5.8. I've discovered that each time I use the fork() function in a program where I also use "use DBI", it gives me that error. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
