> > > Could somebody PLEASE FIX THE FUCKING WIDNOWS SHIT PLEASE? > > > > Yeh could someone PLEASE GIVE ME A FUCKING BUG REPORT PLEASE? > > Could someone READ THE FUCKING BUG REPORTS PLEASE?
My reference was to 'The Fucking Windows Shit'. Not the absence of bug reports. Which bug(s) is/are referred to as The Fucking Windows Shit (or is that just the general impression of all of the Windows support software?) > a) on Win9x/ME it will ALWAYS CAUSE A FUCKING WARNING MESSAGE if you > SHUT DOWN WINDOWS and a WIN32 CONSOLE APP (LIKE JAVA.EXE) is open. USE > JAVAW on these OSes (AFAIK that was the real reason for Sun to provide > javaw.exe). There were numerous bug reports. I was under the impression that this had been fixed but that shutting down freenet.exe from the systray icon would cause a warning message (rather than shutting down Windows). But your point is clear and, as you'll know by reading my other posts, has already been fixed > b) there is NO FUCKING WAY to send keystrokes to Win32 Console apps on > Win9x/ME (except putting the text into ckipboard and issuing a > WM_COMMAND to the "paste" menu command. (I don't remember the article > number, but that is listed as known issue in ms knowledge base) Which is why we don't do that (or at least we don't rely on it working). At one point I tried doing this but in the presence of negative feedback changed the code to GenerateConsoleCtrlEvent instead (effectively sending a SIGINT to the console app). > c) when you send a WM_CLOSE to a Win32 console app window (Process: > WINOA386.MOD), it will by default create a warning (you can switch that > one off in system policies, but Freenet as a user app may NOT do that!) > and then will send a TerminateProcess to the underlying Process. So > java.exe WILL NOT GET ANYTHING FROM IT! Which is why we don't do that either. Because YOU told me it didn't work, so I changed it. This does not mean that you or someone else doesn't need to test it - as I have no access to Win9x or ME it makes testing my 9x/ME-specific fixes quite hard without external support. Did you test it after I made the change? > And I also wrote the solution here: Check the OS version, and if > 95/98/ME, use the old (javaw) code. However, my C programming skills are > near zero (i get horror when I see a /strn?[csl][pmte][yprn]/ function), > so someone else should fix that (most likely that one that created that > version...). I saw your proposed solution but I didn't like it - it smacks too much of working around Microsoft's problems which isn't really the issue here. Which is why I took a simpler approach and just put the old code back in, warts and all, as it had fewer bug reports. It's technologically-retarded but it works. Did you try the latest freenet.exe yet (I think I announced it yesterday)? Did you offer constructive advice over whether that works for you or not? d _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
