MacRumorUser
Aug 7, 07:12 AM
it's so sad. in the last few weeks i've seen several apple macbooks get more action than me. :o :(
LOL! Was thinking the same.
Great pic iBlue, it's really classy.
LOL! Was thinking the same.
Great pic iBlue, it's really classy.
more...
manapple
May 4, 12:11 AM
http://www.apple.com/macosx/security/
Mac Virus/Malware Info (http://forums.macrumors.com/showpost.php?p=9400648&postcount=4)
Introduction to Security Overview (http://developer.apple.com/library/mac/#documentation/Security/Conceptual/Security_Overview/Introduction/Introduction.html)
thanks for the thread link. i have seen the apple page, and need more info, as it only lists achievements rather than talks about them. thanks again.
Mac Virus/Malware Info (http://forums.macrumors.com/showpost.php?p=9400648&postcount=4)
Introduction to Security Overview (http://developer.apple.com/library/mac/#documentation/Security/Conceptual/Security_Overview/Introduction/Introduction.html)
thanks for the thread link. i have seen the apple page, and need more info, as it only lists achievements rather than talks about them. thanks again.
more...
profets
Mar 22, 03:34 PM
I'm still unsure.. No idea how good the stock Bestbuy gets will be.. no idea how crazy the lines at apple stores may become..
more...
AppleHead1989
Mar 11, 02:49 PM
Thanks for the heads up! I think I'm actually going to Target first . . .I've heard that some targets have started handing out vouchers already. It would be great to get a voucher and then just wander around. I think you're probably right about 16gb selling out first. Good Luck! If I'm unsuccessful you may see me at BB too.
Really? It's about 30 people over here. And good luck to you too. Hopefully we both get lucky and get the model we want.
Really? It's about 30 people over here. And good luck to you too. Hopefully we both get lucky and get the model we want.
more...
4JNA
Nov 21, 03:20 PM
...looking at the log file
posting a copy of that might help (or the part you are worried about i guess to keep it short). easier to read and research than guess and give you a wrong answer.
the two copies of X are fine. i have several copies/versions in my MP with no issue. and one more on an external firewire drive actually come to think of it...
posting a copy of that might help (or the part you are worried about i guess to keep it short). easier to read and research than guess and give you a wrong answer.
the two copies of X are fine. i have several copies/versions in my MP with no issue. and one more on an external firewire drive actually come to think of it...
more...
dakduel
Apr 18, 11:09 PM
i too am still a beginner at photography but it to me, it seems like the plants in the foreground of the first picture just get in the way. They seem to hide part mountain. i sorta don't know whether i should be looking at the mountain or the plants in front of it.
and you are right, it is a beautiful country. hope to one day visit it
and you are right, it is a beautiful country. hope to one day visit it
more...
methodshop
Jun 3, 09:25 PM
Would anyone really buy a CD of dot matrix printers making music?
http://wiredblogs.tripod.com/cultofmac/index.blog?entry_id=328765 :eek:
http://wiredblogs.tripod.com/cultofmac/printersymphony.jpg
http://wiredblogs.tripod.com/cultofmac/index.blog?entry_id=328765 :eek:
http://wiredblogs.tripod.com/cultofmac/printersymphony.jpg
more...
debroglie
Mar 3, 11:47 PM
I have a wack-o-phone and I love it!
more...
Doctor Q
Apr 20, 07:04 PM
According to the timeline (http://terminator.wikia.com/wiki/Terminator:_The_Sarah_Connor_Chronicles_timeline) of The Sarah Connor Chronicles (http://en.wikipedia.org/wiki/Terminator:_The_Sarah_Connor_Chronicles), tomorrow is Judgment Day. :eek:
Yesterday, April 19, Skynet went online at 20:11. Tomorrow, April 21, Skynet will become self aware and attack us. We'll lose over a billion people but some of us will survive to fight back.
Even though the TV show was canceled, I haven't seen any notice that Judgment Day has been canceled, so I assume Skynet is now operating.
Who's ready for the battle? I'm arming myself with a pocket protector and an anti-static wrist band.
Yesterday, April 19, Skynet went online at 20:11. Tomorrow, April 21, Skynet will become self aware and attack us. We'll lose over a billion people but some of us will survive to fight back.
Even though the TV show was canceled, I haven't seen any notice that Judgment Day has been canceled, so I assume Skynet is now operating.
Who's ready for the battle? I'm arming myself with a pocket protector and an anti-static wrist band.
more...
mpsruo
Jun 23, 11:16 PM
The mall security is informing people that there's a line formed at the bank. There's a list going that will apparently be honored by apple. I'm in the 60's which us worrying. I wonder how many they'll have...
more...
Rob587
Feb 16, 10:26 AM
does it make u feel awkward in public..... do u feel u need more screen space for home?
more...
mammadon
Feb 2, 04:04 PM
lol.. I think HP has bigger problems. Acer is threatened to take their number one position.
more...
iLucas
Apr 26, 12:16 AM
Yes that is correct. It does chime, and the light flashes. After about 5 minutes the fan start to speed up and that's all it does. I never see anything on either screen.
more...
ReverendCharm
Mar 27, 04:35 PM
Heres my deal:
I am a musician working with garageband and I have always been recording to my internal drive until recently
. I was unaware until I read some posts here from the good people like you guys, that that is not a good idea to record to your internal drive. So, I got an external firewire 800 drive (http://www.amazon.com/gp/product/B001DGZ05A) and this cable (http://www.amazon.com/2M-Firewire-800-9PIN-Cable/dp/B000XQILWK/ref=pd_bxgy_e_img_b). When I received it, I first used disk utility and reformatted it for Mac OS Extended Journaled. Then I proceeded to move a couple sample libraries and my entire "Garageband" folder (with my saved songs in it) to the external. I instantly knew something was wrong. The files were taking forever to get written over. It took about 15 mins for a 5GB folder to be moved over. I was already discouraged. Anyway, I plugged in the USB cable that came with the external (the drive has hook ups for both USB 2 and firewire 400/800) and tried moving the same files and it was MUCH faster. The same 5GB file was moved over in a matter of minutes.
I then tried recording to the drive (using firewire again) and it would hardly even PLAY the song without stopping every couple seconds (too many effects error, and yes ALL the tracks were locked). Tried to record as well and i'd get even less time before garageband would stop the song with the same error. So I disconnected firewire and went USB. Thru USB the song didnt stop once, not on playback OR recording. Then I moved the songs back to my internal and played them (and recorded) with no problem either.
I ran a couple tests on the drive using AJA system test and came back with these results:
Basic test of read/write speed using firewire 800:
write - 14/mb sec
read - 21/mb sec
then, using usb 2.0
write - 18/mb sec
read - 37/mb sec
both these connections seemed to be running slower then they should ..but at least the USB connection would actually let me play a song and record to it without stopping
I manually copied over a 2.04GB file and via firewire 800 connection it took 2 mins and 20 secs. Via the USB 2 connection it was 55 seconds! ..also, while i transfered the files i noticed that the USB transfer was nice and steady with tiny increments of the file being transferred. Firewire, however, was speedy then slow, speedy then slow. Very inconsistant transfer speed throughout the process. kind of choppy
So what gives? I cant figure out if I'm doing something wrong, or if my external HD is bad? Or the cable is bad? Or maybe the firewire port on my mac mini is bad (i've never used it before for anything other than this external drive). Or i'm thinking maybe my processor isnt strong/fast enough to record to the external firewire drive? Im working with a mac mini 120GB internal HD and the 2ghz intel core 2 duo with only 2GB ram (i know thats not ideal for recording and im planning to upgrade at some point, but i have been recording to the internal just fine with the RAM i have now and never had a problem until trying to record to the firewire drive). I was going to go out today and get a new cable and see if that was the cause of it. Anyway sorry for the book-length post! But PLEASE SOMEBODY help me here! ..as i said, im not very computer literate and only just started producing music using computers so please use dummy terms lol ..thanks in advance
I am a musician working with garageband and I have always been recording to my internal drive until recently
. I was unaware until I read some posts here from the good people like you guys, that that is not a good idea to record to your internal drive. So, I got an external firewire 800 drive (http://www.amazon.com/gp/product/B001DGZ05A) and this cable (http://www.amazon.com/2M-Firewire-800-9PIN-Cable/dp/B000XQILWK/ref=pd_bxgy_e_img_b). When I received it, I first used disk utility and reformatted it for Mac OS Extended Journaled. Then I proceeded to move a couple sample libraries and my entire "Garageband" folder (with my saved songs in it) to the external. I instantly knew something was wrong. The files were taking forever to get written over. It took about 15 mins for a 5GB folder to be moved over. I was already discouraged. Anyway, I plugged in the USB cable that came with the external (the drive has hook ups for both USB 2 and firewire 400/800) and tried moving the same files and it was MUCH faster. The same 5GB file was moved over in a matter of minutes.
I then tried recording to the drive (using firewire again) and it would hardly even PLAY the song without stopping every couple seconds (too many effects error, and yes ALL the tracks were locked). Tried to record as well and i'd get even less time before garageband would stop the song with the same error. So I disconnected firewire and went USB. Thru USB the song didnt stop once, not on playback OR recording. Then I moved the songs back to my internal and played them (and recorded) with no problem either.
I ran a couple tests on the drive using AJA system test and came back with these results:
Basic test of read/write speed using firewire 800:
write - 14/mb sec
read - 21/mb sec
then, using usb 2.0
write - 18/mb sec
read - 37/mb sec
both these connections seemed to be running slower then they should ..but at least the USB connection would actually let me play a song and record to it without stopping
I manually copied over a 2.04GB file and via firewire 800 connection it took 2 mins and 20 secs. Via the USB 2 connection it was 55 seconds! ..also, while i transfered the files i noticed that the USB transfer was nice and steady with tiny increments of the file being transferred. Firewire, however, was speedy then slow, speedy then slow. Very inconsistant transfer speed throughout the process. kind of choppy
So what gives? I cant figure out if I'm doing something wrong, or if my external HD is bad? Or the cable is bad? Or maybe the firewire port on my mac mini is bad (i've never used it before for anything other than this external drive). Or i'm thinking maybe my processor isnt strong/fast enough to record to the external firewire drive? Im working with a mac mini 120GB internal HD and the 2ghz intel core 2 duo with only 2GB ram (i know thats not ideal for recording and im planning to upgrade at some point, but i have been recording to the internal just fine with the RAM i have now and never had a problem until trying to record to the firewire drive). I was going to go out today and get a new cable and see if that was the cause of it. Anyway sorry for the book-length post! But PLEASE SOMEBODY help me here! ..as i said, im not very computer literate and only just started producing music using computers so please use dummy terms lol ..thanks in advance
more...
h1r0ll3r
May 4, 02:33 PM
Have you ever looked at the location file that saves on your PC? If so, can you tell me where iTunes saves it?
Thanks
I could be wrong but I think it's bundled within the backups from your iPhone. I've never seen this supposed file so I wouldn't know how to access it specifically. I'm sure someone else here might have some better info on this.
Thanks
I could be wrong but I think it's bundled within the backups from your iPhone. I've never seen this supposed file so I wouldn't know how to access it specifically. I'm sure someone else here might have some better info on this.
more...
lordonuthin
Oct 21, 09:05 PM
Still haven't figured out what the problem is with GPU2 in wine.
[19:50:44] Working on queue slot 01 [October 21 19:50:44 UTC]
[19:50:44] + Working ...
Warning: Ignoring unknown arg
[19:50:44]
[19:50:44] *------------------------------*
[19:50:44] Folding@Home GPU Core - Beta
[19:50:44] Version 1.25 (Mon Mar 2 19:49:32 PST 2009)
[19:50:44]
[19:50:44] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[19:50:44] Build host: vspm46
[19:50:44] Board Type: Nvidia
[19:50:44] Core :
[19:50:44] Preparing to commence simulation
[19:50:44] - Looking at optimizations...
[19:50:44] - Created dyn
[19:50:44] - Files status OK
[19:50:44] - Expanded 68640 -> 357580 (decompressed 520.9 percent)
[19:50:44] Called DecompressByteArray: compressed_data_size=68640 data_size=357580, decompressed_data_size=357580 diff=0
[19:50:44] - Digital signature verified
[19:50:44]
[19:50:44] Project: 5915 (Run 13, Clone 422, Gen 13)
[19:50:44]
[19:50:44] Assembly optimizations on if available.
[19:50:44] Entering M.D.
Reading file work/wudata_01.tpr, VERSION 3.1.4 (single precision)
Reading file work/wudata_01.tpr, VERSION 3.1.4 (single precision)
Reading sasa-enabled ir 0 0
Initializing Nvidia gpu library
[19:50:50] Tpr hash work/wudata_01.tpr: 2601313573 3913075720 1380217986 614781101 1211686473
Run: exception thrown during GuardedRun
[19:50:50] SEH code: 3221225477
[19:50:50] Run: exception thrown during GuardedRun
[19:50:50] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[19:50:50] Going to send back what have done -- stepsTotalG=0
[19:50:50] Work fraction=0.0000 steps=0.
[19:50:54] logfile size=4917 infoLength=4917 edr=0 trr=23
[19:50:54] - Writing 5453 bytes of core data to disk...
[19:50:54] Done: 4941 -> 1839 (compressed to 37.2 percent)
[19:50:54] ... Done.
[19:50:54]
[19:50:54] Folding@home Core Shutdown: UNSTABLE_MACHINE
[19:50:44] Working on queue slot 01 [October 21 19:50:44 UTC]
[19:50:44] + Working ...
Warning: Ignoring unknown arg
[19:50:44]
[19:50:44] *------------------------------*
[19:50:44] Folding@Home GPU Core - Beta
[19:50:44] Version 1.25 (Mon Mar 2 19:49:32 PST 2009)
[19:50:44]
[19:50:44] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[19:50:44] Build host: vspm46
[19:50:44] Board Type: Nvidia
[19:50:44] Core :
[19:50:44] Preparing to commence simulation
[19:50:44] - Looking at optimizations...
[19:50:44] - Created dyn
[19:50:44] - Files status OK
[19:50:44] - Expanded 68640 -> 357580 (decompressed 520.9 percent)
[19:50:44] Called DecompressByteArray: compressed_data_size=68640 data_size=357580, decompressed_data_size=357580 diff=0
[19:50:44] - Digital signature verified
[19:50:44]
[19:50:44] Project: 5915 (Run 13, Clone 422, Gen 13)
[19:50:44]
[19:50:44] Assembly optimizations on if available.
[19:50:44] Entering M.D.
Reading file work/wudata_01.tpr, VERSION 3.1.4 (single precision)
Reading file work/wudata_01.tpr, VERSION 3.1.4 (single precision)
Reading sasa-enabled ir 0 0
Initializing Nvidia gpu library
[19:50:50] Tpr hash work/wudata_01.tpr: 2601313573 3913075720 1380217986 614781101 1211686473
Run: exception thrown during GuardedRun
[19:50:50] SEH code: 3221225477
[19:50:50] Run: exception thrown during GuardedRun
[19:50:50] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[19:50:50] Going to send back what have done -- stepsTotalG=0
[19:50:50] Work fraction=0.0000 steps=0.
[19:50:54] logfile size=4917 infoLength=4917 edr=0 trr=23
[19:50:54] - Writing 5453 bytes of core data to disk...
[19:50:54] Done: 4941 -> 1839 (compressed to 37.2 percent)
[19:50:54] ... Done.
[19:50:54]
[19:50:54] Folding@home Core Shutdown: UNSTABLE_MACHINE
more...
TheNewDude
May 29, 07:09 PM
Glad to see such a quick update from Apple for us Windows users.
I can't save I've had the brightness issue, but did have the head phone issue which was an easy fix by downloading the newest audio drivers.
But thanks Apple....
I can't save I've had the brightness issue, but did have the head phone issue which was an easy fix by downloading the newest audio drivers.
But thanks Apple....
more...
holamiamigos
Mar 28, 08:21 PM
i remember getting it with dk 64 and wondering what it was... man i was so clueless.. it was a little weird to put in to...
more...
homeshire
Jul 15, 07:24 AM
right -- just tried 2-3 different ways to get some qt streams. indeed, i got a couple stations playing classical music (WGBH Boston, WCPE), but all the selections that were always there in the past are gone, e.g. npr, cnn, abc, bbc etc. either an error (-2129) on trying to open, or the blurb about channel selection having changed, please update your existing software. i have tried to update, and i assure, there are no updates available.
p0intblank
Dec 6, 03:00 PM
It's not myspace so much folks as it is all the relatively novice computer users dumping all sort of odd code into their page. WMP is a problem simple because we dont have the latest version windows user have, the easiest thing to do is go to the security tab in safari preferences and un check enable plugins, since ive started that ive not had a single myspace crash.
That's a nice tip. Thanks! But does anyone know if MS ever plans on releasing WMP10?
That's a nice tip. Thanks! But does anyone know if MS ever plans on releasing WMP10?
Skystar
Oct 22, 04:52 PM
I get off work at 5pm, and the Apple store is approximately an 8min walk from my office. So I will be there no later than 5:10 :D
Do they generally have enough stock for the people waiting in line with OS X releases? This is my first one..
Do they generally have enough stock for the people waiting in line with OS X releases? This is my first one..
gnasher729
Mar 30, 02:20 AM
1. Why "return 99;"? Doesn't make any sense at all. First, only 0, EXIT_SUCCESS and EXIT_FAILURE have defined meaning. Second, exiting when the input is "q" is the normal successful exit route, so you should return 0 or EXIT_SUCCESS. Or better to use "break;" in case things are added after the loop.
2. Why is this a while loop? You check the same condition at the end of the loop as inside the loop, which won't work. for (;;) is the common idiom for this.
3. It won't work for the second star because you modify path.
4. A safer and much more readable way to concatenate strings and other text would be calling snprintf.
5. system () is dangerous. What happens if I enter this as a star name:
'; rm -r /;
2. Why is this a while loop? You check the same condition at the end of the loop as inside the loop, which won't work. for (;;) is the common idiom for this.
3. It won't work for the second star because you modify path.
4. A safer and much more readable way to concatenate strings and other text would be calling snprintf.
5. system () is dangerous. What happens if I enter this as a star name:
'; rm -r /;
Dreadnought
Feb 2, 02:16 PM
You should really change a couple of his computers to your name! :D
macmikey2
Apr 13, 05:45 AM
Mine did the same thing. Both preview versions.
I would restart, blue hang, then restart with SHIFT and it would start normally. Restart again, 50% of time it would hang at blue screen.
Verbose did not help as the screen mine hung at was after OS X stops loading scrolling text, so could not see where it would stop (looking for 'we're hanging here...' message).
Finally gave up on Lion yesterday and went back to SL. Not worth trouble. Reported a bunch of stuff so I did my developer thing, now I'll just wait it out until release is near.
Mikey
I would restart, blue hang, then restart with SHIFT and it would start normally. Restart again, 50% of time it would hang at blue screen.
Verbose did not help as the screen mine hung at was after OS X stops loading scrolling text, so could not see where it would stop (looking for 'we're hanging here...' message).
Finally gave up on Lion yesterday and went back to SL. Not worth trouble. Reported a bunch of stuff so I did my developer thing, now I'll just wait it out until release is near.
Mikey
No comments:
Post a Comment