4 ms·
Thanks for that - useful. I'll have a look at using the embedded version. Currently Chrome comes up with the bar across the top saying something like "the fol
by RiderOfGiraffes 16y ago
Thanks for that - useful. I'll have a look at using the embedded version. Currently Chrome comes up with the bar across the top saying something like "the following plug-in has crashed: Shockwave Flash" (or something - I don't have the machine in front of me right now, and can't remember exactly).
- pmjordan 16y agoI don't know if this works on the windows version, but you could try launching it from the command line and see if there's any output. Maybe get a chromium debug build or something? Have you tried other browsers? You might be able to trace which files are accessed by it as it starts (using whatever the equivalent of strace is on windows - Process Explorer?).
- RiderOfGiraffes 16y agoThanks for the advice and comments. Not sure how to launch from the command line - I've very little experience of Windows, although lots and lots of experience with DOS (of various flavors), Linux console/shell, and Linux GUIs. I can get to the command line, just don't know what executable to run. I haven't tried other browsers, and I have no idea how to trace system calls on Windows without some sort of dev environment. So far I've gone to chrome://plugins and disabled the Flash plugin, then re-enabled it, and now it seems to work. Mostly.
- pmjordan 16y agoStart -> Run; type "cmd"; drag & drop the chrome icon onto the command line window. You may need to prefix it with start /wait To capture output. But there might not be any output. Process Explorer traces some stuff, and doesn't need a system environment. I'm not sure if it would suffice, particularly with a process that dies quickly. You'd have to try it. Good to hear that it works - not quite sure what you mean by "mostly". :-) I'm no Windows expert but feel free to contact me out-of-band (contact info is in my profile) if you think I could help.