12971 Views Previous 1 2 3 4 5 … Next 96 Replies Latest reply: Jul 2, 2007 2:37 PM by Tom34 Go to original post
I install the Safari 3 Beta for the Windows XP Professional SP2 (hungarian edition, with the latest upgrades, Nod32 v2.7 antivirus, Comodo 126.96.36.199 Firewall), but I got error messages, with this error report:
Technical Error report: http://download.yousendit.com/D2D52C94787E4A13
"It a bad show for Apple. Why release something that does not work."
Because it's a public beta, it's not supposed to work If it's still misbehaving like this during the final release then yes, Apple deserve a thrashing.
I'm another person who can't get Safari 3 for Windows to behave itself with a proxy server.
Just because it's a beta, it still shouldn't be crashing and not work AT ALL.
iTunes 7.2 was a final release and not a beta, so that crashed too. If the problem is the same, as some people have speculated it is, then they should have known to look into the problem and try to fix it, before releasing.
Because it's a public beta, it's not supposed to work
If it's still misbehaving like this during the
final release then yes, Apple deserve a thrashing.
I would expect a PUBLIC beta to at least run, not to consistently crash when it opens. And if it is expected to be flaky this should be highlighted on the download page. Yes, I expect bugs in a public beta, but I also expect to be able to reach a position where these bugs can be found.
MacBook Pro 2Ghz Mac OS X (10.4.9) XP Pro under Parallels 3.0
Sounds like something in your admin account is causing a conflict. I had the same problem with XP and some older Corel apps -- they had worked fine in the admin account, then started crashing all the time. I created a new account and they worked fine there but not in the admin account. I used them so infrequently that I never bothered to figure out the cause of the conflict -- but I wouldn't blame Corel for it....
I would expect a PUBLIC beta to at least run, not to
consistently crash when it opens. And if it is expected
to be flaky this should be highlighted on the download
page. Yes, I expect bugs in a public beta, but I also
expect to be able to reach a position where these bugs
can be found.
It doesn't consistently crash when it opens, though. At least, it doesn't on my Dell laptop or AMD64 desktops. It doesn't even crash on my two P4 work PCs, up until I put in the proxy server information anyway. It's not universally flaky and it's not consistently crashing across the board. Besides which, surely the fact that it's clearly labelled as BETA software should suggest that Apple are expecting it to not work 100%?
I too have the MS VPC, with all updates running on top of Tiger. The Win XP has all available updates installed.
Safari crashes on opening every time. I've done a validation of the installation, restarted the virtual machine a few times, etc..
Apple's QuickTime and iTunes both work inside the virtual machine, and I've run the Apple Software Update to make sure all things Apple were updated.
Upon launch the framework of a web page starts to be drawn, and before the outline/framework is complete the crash message appears.
Unfortunately, I suspect that only MS gets a copy of the "send bug/errror report" option. As those experiencing crash upon startup obviously can't use the "bug report" function, perhaps we should include crash reports here?
IF NOT, WHERE CAN WE SUBMIT REPORTS w/ COPIES OF THE CRASH LOG?
I've installed on XP Pro running under Parallels 3.0,
and sure enough it crashes straight away. This is on
a MacBook Pro, so not exactly an old machine.
Whether it's related to the VM environment I don't
know, as there's also a proxy involved - I would
have expected Safari to at least start up if it were
a proxy issue.
This thread on a proxy issue might help
iMac: 20" G5, MacB 1Gb Mac OS X (10.4.8)
might it not be better to keep the thread's focus on crash on startup/open?
I don't minimize the importance of your problem, on the contrary, believe it will get more attention if you use the search to see if other threads are started that are relevant, and, if not then start one. Lumping crashes together just because they are crashes isn't particularly helpful to people looking to sort out issues.