Recommended Posts

Bootcamp x64 will refuse to install on anything that is not a Mac Pro or a MacBook pro. You can always make that MSI file install somehow (it will require you to be an admin and even if you run the windows explorer as admin it will still ask it. so I guess the troubleshoot compatibility will do the trick). Apparently all but two drivers can get installed, one of them being the iSight
The only part of the bootcamp drivers that is designed to stop you from installing on unsupported machines is the setup.exe launcher at the root of the Windows partition of the SL disc.

the file /Drivers/Apple Bootcamp64.msi should install on a 64bit vista/7 installation without any need for special tricks

at least on my iMac it didn't, but that setup.exe launcher it designed to quit when run on anything other than the "Pros"

Thanks guys, and the others that contributed. I'll try it again at home. I did a bit of digging but not too much. I'll play with it some more and maybe try the compatibility stuff. I'm installing it on the current line of iMac's if it makes a difference.

Restoring does the normal effect, but when minimizing it doesn't get "sucked" into the dock as it used to. I've used OS X since 10.3, it's definitely different. Or it was a bug.

I've been using Mac OS X since its initial release in 2001 and the betas before that. I don't see any difference to be honest. Minimizing and restoring gives me the exact same result only in de opposite direction.

Restoring does the normal effect, but when minimizing it doesn't get "sucked" into the dock as it used to. I've used OS X since 10.3, it's definitely different. Or it was a bug.

Are you talking about this? wether it goes to the right of the dock or into the app icon?

post-24918-1251913444_thumb.png

Are you talking about this? wether it goes to the right of the dock or into the app icon?

No, the effect is somewhat strange. I'll see if it still happens when I get home.

EDIT: Yeah, it's completely different from the "being sucked" effect I remember.

I took this in slow motion:

Edited by Ricardo Gil
No, the effect is somewhat strange. I'll see if it still happens when I get home.

EDIT: Yeah, it's completely different from the "being sucked" effect I remember.

I took this in slow motion:

Wow, that is messed up

here is what mine looks like, Ive also found a little more about the base10 Vs. base2 file size math, it is incredibly inconsistent here is a screen,

I understand it is up the app on how to display it but Safari? come on apple's own app? shows 32.6 mb, and notice finder displays 2 different sizes, 34.1mb on the desktop and 34.2mb in the info box.

http://www.youtube.com/watch?v=wf0WN8YcqkY

Am i going to have to resort to checking the bytes for every file when i want to compare them GAH!!! loll

Now that i'm using SL on a day to day basis i'm getting the feeling more and more that it was Rushed To Manufacturing

post-24918-1251916849.png

Edited by Phantom Helix

The method change lead to a lot of loose ends it seems. Should be a while until everything gets calculated the same way :/

Anyway, the genie effect seems to work fine if I tell it to minimize into the application icon. Restoring minimized windows looks OK both ways.

No, the effect is somewhat strange. I'll see if it still happens when I get home.

EDIT: Yeah, it's completely different from the "being sucked" effect I remember.

I took this in slow motion:

that looks like messed up scale effect. :blink:

here is what mine looks like, Ive also found a little more about the base10 Vs. base2 file size math, it is incredibly inconsistent here is a screen,

I understand it is up the app on how to display it but Safari? come on apple's own app? shows 32.6 mb, and notice finder displays 2 different sizes, 34.1mb on the desktop and 34.2mb in the info box.

You just don't understand the differences.

There are two sizes for every file stored on a drive in any operating system

  • The actual size of the file: the sum of the number of bytes it uses. echo "Hello" > example.txt produces a 5-byte file. One byte for each letter.
    You can see this size as the file-size (rounded off) on the desktop when "Show info" is enabled. It is also displayed unmodified inside of the brackets on your show info window.
  • The amount of space the file uses on disk. This amount varies from drive to drive, partition to partition and OS to OS. The reason for the variation is because file systems don't allocation bytes to a file, they allocate blocks: and blocks are all the same size (for example 4 kilobytes). Any file that is less than 4 kilobytes will still take up "4 k on disk" because it can't be assigned less space. A file that contains 6,000 bytes will consume 8 kilobytes on disk because you would be assigned 2 blocks for the file. You can see this size in the get info window as labeled "[file size] on disk".
    Moving a file from a device with 4kb blocks to one with 512 byte blocks (like a small fat32 drive) will actually turn your 4 kilobyte "hello" file from into a 512 byte file containing "hello".

Safari is reporting the number of bytes downloaded divided by 1024^2. It's a safari bug - likely because it runs on both 10.6, 10.5 and Windows. File a bug report.

Am i going to have to resort to checking the bytes for every file when i want to compare them GAH!!! loll

You always had to. This is not something new with 10.6: it's been around since the beginning of Mac OS X (possibly longer).

A 1000245 byte file, and a 100250 byte file would both use 12 kilobytes on disk, and finder would display them both as 10.1 kilobytes.

20090902-jmh3sfnhu6ana2t9akj3qbjjwd.jpg

If you are comparing sizes based on the finder reported size: you'd be no worse off under 10.6 than you are on 10.5.

If you are comparing sizes based on the get info window: you'd be no worse off under 10.6 than you are on 10.5.

for those that are still trying to find out new useful features or just justify the ?$ spent I HIGHLY recommend wathcing the Macbreak Podcast Videos via itunes.

There are two podcasts on the improved 'services'

The new 'Services' functionality are very impressive...

You just don't understand the differences.

There are two sizes for every file stored on a drive in any operating system

  • The actual size of the file: the sum of the number of bytes it uses. echo "Hello" > example.txt produces a 5-byte file. One byte for each letter.
    You can see this size as the file-size (rounded off) on the desktop when "Show info" is enabled. It is also displayed unmodified inside of the brackets on your show info window.
  • The amount of space the file uses on disk. This amount varies from drive to drive, partition to partition and OS to OS. The reason for the variation is because file systems don't allocation bytes to a file, they allocate blocks: and blocks are all the same size (for example 4 kilobytes). Any file that is less than 4 kilobytes will still take up "4 k on disk" because it can't be assigned less space. A file that contains 6,000 bytes will consume 8 kilobytes on disk because you would be assigned 2 blocks for the file. You can see this size in the get info window as labeled "[file size] on disk".
    Moving a file from a device with 4kb blocks to one with 512 byte blocks (like a small fat32 drive) will actually turn your 4 kilobyte "hello" file from into a 512 byte file containing "hello".

Safari is reporting the number of bytes downloaded divided by 1024^2. It's a safari bug - likely because it runs on both 10.6, 10.5 and Windows. File a bug report.

You always had to. This is not something new with 10.6: it's been around since the beginning of Mac OS X (possibly longer).

A 1000245 byte file, and a 100250 byte file would both use 12 kilobytes on disk, and finder would display them both as 10.1 kilobytes.

If you are comparing sizes based on the finder reported size: you'd be no worse off under 10.6 than you are on 10.5.

If you are comparing sizes based on the get info window: you'd be no worse off under 10.6 than you are on 10.5.

I understand the technical differences, now after we started talking about it in this thread, reminding me accomplished nothing.

However it shows that they didn't fully examine these issues before they made a public release, and that is my point.

I apologize if I did not make my overall point apparent, that is just how I speak, re-explaining the technical specs of how things work was unnecessary and carried out with a condescending tone.

No biggie though, I get where you are coming from and why it comes out that way.

Here's a small gripe over snow leopard. Has anyone noticed a performance drop when transitioning between spaces? When I swap spaces I feel a definite performance drop (i.e., chugging) over leopard.

Anyone experience this?

I would say that is just as quick, but the redraw does seem a little jaggedy !

There is now a 3rd video on 'Services' from the Macbreak podcast....

Anyway, the genie effect seems to work fine if I tell it to minimize into the application icon. Restoring minimized windows looks OK both ways.

Definitely a bug.

That's funny you say that, because I get extremely choppy and jerky Genie effects when minimizing and restoring windows UNLESS I make it minimize to the application icon. Then magically these animations move veeeeeeery smoothly.

Here's a small gripe over snow leopard. Has anyone noticed a performance drop when transitioning between spaces? When I swap spaces I feel a definite performance drop (i.e., chugging) over leopard.

Anyone experience this?

Yes, in fact all animations seem to be jerky now (i'm ajm83 on this thread - also see this one)

Did a totally clean install, and not installed anything except iWork + iLife

Edited by hornett
Yes, in fact all animations seem to be jerky now (i'm ajm83 on this thread - also see this one)

Did a totally clean install, and not installed anything except iWork + iLife

All these graphic bugs were kind of expected, OpenCL is still an infant technology, but Apple really shouldn't have rushed this.

The "window minimize" genie effect changed, wasn't expecting it. Now I'm just waiting for iStat 2.0 to come out.

There is a beta 2.0 out that I found on the bjango forums. Keynote is BETA. I would recommend updating whenever iStat says there is an update as the devs are diligently working around the clock on this one. The link is about 2/3 down the page. Remember, BETA, although it runs well so far on my system.

Does anyone seem to lack the majority of the 'services'? For example, if I command click an image, there should be workflows to rotate it clock/anti-clockwise etc - yet all I see is 'Set desktop picture'. Likewise, in iPhoto options are severely lacking for me, which I am bemused about...

With pics are you talking about using Preview? If so you should right click near the top toolbar and select 'customize', from there you can select all the toolbar buttons (such as rotate, etc.) Also, you might need to set your defaults for services in System Preferences. Go to Keyboard..Keyboard Shortcuts and on the left you'll see a configuration for Services.

my safari has beeen hating life. it randomly beachballs and won't download some links (.zip, .torrent, .dmg etc). I have to copy past the link into the downloads window to get them to download, it's sooo annoying. Is there like a reinstaller somewhere out there for snow leopard beta? Imma try out a webkit built and see how that goes.

edit: tried webkit... does it to :s

Amit Singh of Mac OS X Internals fame has a blog post about enabling the 64-bit kernel on machines that otherwise can't boot it (macbooks, mac minis, etc) including machines with 32-bit EFI, not that it's useful.

I tried briefly: it works as advertised.

20090903-g3u7dr5u6kgfd118pw6ud4mfkp.jpg

Having dug around it seems that Macbook Pro 3,1 won't boot to 64 by default because the AirPortAtheros driver is still 32bit which would indicate why it's been blacklisted from booting in native.

I've give it a little test to see if my hypothesis on the matter is correct.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nobody is buying a PS5 only for playing Until Dawn 2. Their loss.
    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      233
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!