Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Re: safari twice as fast

Originally posted by irobot75
I just purchased my imac today and I'm in love! I've waited 1 year for this day!
I see that this was your first post, irobot75, so welcome to MacRumors and congratulations on your new iMac. You posted at 2am Pacific Time, which makes me curious what time zone you are in.

If you are new to Macs (or even if you are not), you can get advice and help here. Just post a question in the "Mac Help/Questions and Tips" forum.

Here's a tip to start with: If Safari is your main web browser, but you have trouble with a web site (e.g., an e-commerce site), try another browser. For example, some web sites are designed for and only tested with Internet Explorer. No single web browser is best for all sites.
 
Originally posted by Awimoway
We all understand that it's a beta, thank you very much.


Most of us do. I think Apple made a big mistake, though, releasing the public beta on SUPP. Both here and on other forums I've heard a ton of people complaining -- not just about how buggy Safari is, but about how Apple shouldn't release software before it's ready. They're surprised when people point out that it's beta.

I wasn't trying to be disparaging or condescending in my previous post -- if I came across that way, I'm sorry. I'm just trying to be helpful as well and, since I'm new to these boards (and Macs in general) I'm still learning my own way. :)
 
Two things

1) I downloaded v64 from 2 different places, and neither one worked. At first it simply crashed on startup (about 5 times in a row). After that I would double-click on it and it would open iMovie. I restarted, booting from my Norton Systemworks CD, and it found the 3 major errors it finds when things go wrong (VHB, B-tree, etc.). It fixed them. I rebooted. Safari crashed on startup. V62 still works just fine.

Any ideas?

2) The plural of Canadian is "Canadians", not "Canadian's". Funny when someone is trying to point out how stupid someone else is and they can't even pluralize a simple word.

Thank's in Advance's,
Chris
 
Re: Two things

Originally posted by chmorley
1) I downloaded v64 from 2 different places, and neither one worked. At first it simply crashed on startup (about 5 times in a row). After that I would double-click on it and it would open iMovie. I restarted, booting from my Norton Systemworks CD, and it found the 3 major errors it finds when things go wrong (VHB, B-tree, etc.). It fixed them. I rebooted. Safari crashed on startup. V62 still works just fine.

Any ideas?

2) The plural of Canadian is "Canadians", not "Canadian's". Funny when someone is trying to point out how stupid someone else is and they can't even pluralize a simple word.

Thank's in Advance's,
Chris
i have no idea. these are the same reasons why apple has this in beta mode. i havent expreienced those problems. sorry.

iJon
 
Autocomplete... is anyone getting it to work?

Subject about says it all... had v62, now have v64... have turned on the feature in the debug menu, but am having no success in the autocomplete forms feature actually working... any details would be appreciated
 
Re: Re: Two things

Originally posted by iJon
i have no idea. these are the same reasons why apple has this in beta mode. i havent expreienced those problems. sorry.

iJon
What made you want to reply?

Chris
 
Beta

Originally posted by cnladd
Most of us do. I think Apple made a big mistake, though, releasing the public beta on SUPP. Both here and on other forums I've heard a ton of people complaining -- not just about how buggy Safari is, but about how Apple shouldn't release software before it's ready. They're surprised when people point out that it's beta.

I wasn't trying to be disparaging or condescending in my previous post -- if I came across that way, I'm sorry. I'm just trying to be helpful as well and, since I'm new to these boards (and Macs in general) I'm still learning my own way. :)

I think the idea of the beta was to get feedback on websites so as they were finishing the "Tabs, Auto-Fill, etc" they could get all the "HTML, CSS, etc" worked out.
Remember it was said at the expo that there was no way they could go and check out all the web to test it so you, and I, are doing that for them.

And thats why they are not releasing interim betas... the second v60 was released because of the deleted home directory bug. You are not ment to be testing the tabs etc you are ment to be testing the way it handles web code. Didn'y you (you being a general term) notice that the report bugs does not have any Feedback Types, i.e. Design / Ease of Use, Efficiency, ect included in it, it is all about the web page you are having a problem with.
 
Originally posted by PieMac
Great I'll give it a go...do you delete the preferences before you install v64 or after or does it matter?

Just make sure Safari is not running and then delete the Prefs. I did not have to re-install.

For the guy who wants to get rid of that Gaudy Metal look, Download Safari enhancer from versiontracker. THat will give you an option to get rid of the metal look and also activate the debug menu to get the tabs(use the v62 of enhancer)
 
So far, so good. The text display has only gone bonkers a couple of times (vs most the time) since I deleted the prefs. Thanks for the tip!
 
Originally posted by cnladd
Most of us do. I think Apple made a big mistake, though, releasing the public beta on SUPP. Both here and on other forums I've heard a ton of people complaining -- not just about how buggy Safari is, but about how Apple shouldn't release software before it's ready. They're surprised when people point out that it's beta.

Mostly I agree. But I like Safari's feature set--the google toolbar, the bookmark borowser, and the snapback button. I like its UI better than Camino (I don't understand what people have against brushed metal, and I think that it's the right metaphor for a browser).

My point being that if mostly/somewhat stable software is in existence, I would rather be able to use it now than have to wait another 6 mos. to a year for the official release. I felt the same way about Chimera when I used it. But you're right in pointing out that Apple is wrong to downplay the beta-ness of Safari.

Originally posted by cnladd
I wasn't trying to be disparaging or condescending in my previous post -- if I came across that way, I'm sorry. I'm just trying to be helpful as well and, since I'm new to these boards (and Macs in general) I'm still learning my own way. :)

I was a little uncharacteristically snappish, I admit (and apologize for any offense). I've just read this comment so much on the Safari threads that I got tired of seeing it. People who want to should share their troubles with Safari, even if it is a beta. I'm fairly new to Macs and public betas myself.
 
Originally posted by PieMac
So far, so good. The text display has only gone bonkers a couple of times (vs most the time) since I deleted the prefs. Thanks for the tip!

Your very Welcome. Also, a cool feature in the debug menu with tabs is the option to open tabs in the front - I'm not sure if this would affect text rendering or not but since enabling, I have not noticed any large text.
 
thanks,

Doctor Q,

Thanks for the welcome. Yes, I am new to macs but I've been doing my homework here for about a year.

My four year old has my PC now, poor kid.

My wife and I want to use the mac for audio visual production and web design.

I'll never go back.
 
it also has a slightly different user agent:

5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/62 (like Gecko) Safari/62

5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/64 (KHTML, like Gecko) Safari/64

Now they included KHTML...
 
Re: Two things

Originally posted by chmorley
1) I downloaded v64 from 2 different places, and neither one worked. At first it simply crashed on startup (about 5 times in a row). After that I would double-click on it and it would open iMovie. I restarted, booting from my Norton Systemworks CD, and it found the 3 major errors it finds when things go wrong (VHB, B-tree, etc.). It fixed them. I rebooted. Safari crashed on startup. V62 still works just fine.
If anyone else has been having this problem. PithHelmet was/is the culprit. The new version fixes this issue.

Chris
 
No Defaults

So,

I DL'd v64 but have thus far been unsuccessful in my attempts to activate the debugger menu. Both Safari Enhancer and manually typing commands into Terminal yield the following negative result:

"defaults: command not found" or "sh: defaults: command not found"

WTF. Has anybody else experienced similar difficulties? Does this indicate a larger problem with my OS? Should I be typing something else?

Thanks in advance for any help.

Traveler
 
Re: No Defaults

Originally posted by Traveler
So,

I DL'd v64 but have thus far been unsuccessful in my attempts to activate the debugger menu. Both Safari Enhancer and manually typing commands into Terminal yield the following negative result:

"defaults: command not found" or "sh: defaults: command not found"

WTF. Has anybody else experienced similar difficulties? Does this indicate a larger problem with my OS? Should I be typing something else?

Thanks in advance for any help.

Traveler

Sounds to me like when you installed OSX you did a custom install and chose not to insall the developer stuff. I have the same problem and will be reinstalling the system so I can have my terminal window goodness back.
 
Re: No Defaults

Originally posted by Traveler
So,

I DL'd v64 but have thus far been unsuccessful in my attempts to activate the debugger menu. Both Safari Enhancer and manually typing commands into Terminal yield the following negative result:

"defaults: command not found" or "sh: defaults: command not found"

WTF. Has anybody else experienced similar difficulties? Does this indicate a larger problem with my OS? Should I be typing something else?

Thanks in advance for any help.

Traveler


Not positive on what's wrong, but I've got two ideas. First, when you installed Mac OS X, did you make sure to install the BSD subsystem?

First, it could be a pathing issue. Try this out:
Code:
/usr/bin/defaults write com.apple.safari IncludeDebugMenu 1
. The difference here is that you're specifying the full path (/usr/bin/) for the defaults command. If that doesn't work then you may need to do a reinstall. Make sure you install the BSD Subsystem -- it's not necessary for normal system operation, but it enables additional advanced functionality.

You've got me really intrigued -- I'm going to look into this. If you figure it out first, let me know (via Private Message, if nothing else.) I always that the defaults system (and commands) were part of the core OS. Now I'm not sure. :) If someone else knows the answer for sure, let me know.
 
Thanks

Macbandit and cnladd:

Thanks for the advice. You're dead on. I was running low on HD when I installed jaguar so I left out the BSD. It had completely escaped my mind.

I guess defaults is not a part of the core system OS.

Unfortunately, I don't think I will be doing a reinstall. I'm not actually a developer so it seems like an awful lot of effort just to preview a beta release of Safari (especially given all the software updates I have already piled on top of it). If only there were a way to augment the system software as opposed to wiping the slate and starting fresh...
 
Re: Thanks

Originally posted by Traveler
Macbandit and cnladd:

Thanks for the advice. You're dead on. I was running low on HD when I installed jaguar so I left out the BSD. It had completely escaped my mind.

I guess defaults is not a part of the core system OS.

Unfortunately, I don't think I will be doing a reinstall. I'm not actually a developer so it seems like an awful lot of effort just to preview a beta release of Safari (especially given all the software updates I have already piled on top of it). If only there were a way to augment the system software as opposed to wiping the slate and starting fresh...

You can always do as I am going to do and that is a archive and install. It will archive you old system and copy over your preferences to the new one your installing. This is of course only if you have the hard drive space to do so. Also all the system updates you download using Software Update are saved in the hard drive/library/receipts folder. That way you don't have to download them again just run them to update your newly installed system.
 
Re: Thanks

Originally posted by Traveler
Macbandit and cnladd:

Thanks for the advice. You're dead on. I was running low on HD when I installed jaguar so I left out the BSD. It had completely escaped my mind.

I guess defaults is not a part of the core system OS.

Unfortunately, I don't think I will be doing a reinstall. I'm not actually a developer so it seems like an awful lot of effort just to preview a beta release of Safari (especially given all the software updates I have already piled on top of it). If only there were a way to augment the system software as opposed to wiping the slate and starting fresh...

The BSD subsystem doesn't have anything to do with development, really -- the developer tools are something completely different (sorry Macbandit, that's why your first post confused me a bit....) While not necessary for regular system use, there are a fair number of tools, utilities, and regular applications that requires the presence of the BSD subsystem.

BSD stands for "Berkeley System Distribution," for the version of UNIX that Mac OS X is primarily based upon. The BSD subsystem is all of the command-line tools and utilities that help to make up BSD UNIX. It's a good thing to havve (if you've got space) and, IMHO, provides much of Mac OS X's power and flexibility.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.