Mac OS X 'Leopard'-related Discussion


Recommended Posts

My mates Leopard disc that arrived yesterday is 10.5.1, I guess as they roll out each revision they burn that onto the new discs and slowly but surly the 5.0 supply runs dry, a good tactic for keeping people up to date.

I know far too many people (mainly PC users) who're still running Windows XP SP0 and didnt even realise you had to update PCs, no doubt i'll be converting them to Mac users, just give me time

And I've run into even more Mac users who're still running OS X 10.3.9 or w/e and have no idea what "Tiger" or "Leopard" is.

Thanks everyone for your post. I was considering buying Leopard and wondered if the disk in the retail box would be 10.5.1 or I would have to update it myself. Thanks again.

truthfully does it even matter? a brand new leopard install only installs 4 updates... itunes, quicktime, ?????, and 10.5.1... it takes tops 10 minuits from start to finish..

  • 2 weeks later...
Remember leopard takes some time to index everything. That'd explain the "Stuck in the Mudd" feeling.

No, it was just sluggish all the way around - Vista indexes everything too, but it's a different kind of slowness, mainly the HD getting hit, but I always clean install Windows, and after about a week, Vista was happily plugging along. Tiger to Leopard (on a week old system no less) was just bad. Felt like the mouse cursor was lagging, mousing over the dock was slow, slow to open programs, some programs weren't loading correctly...

I haven't experienced any problems with the new install - like Windows, a clean install is definitely the way to go.

The only time an upgrade seems to work smoothly is a clean install of the old OS then IMMEDIATELY upgrade on top of that but.. hardly worth the aggro to be honest :D

Plus, upgrade installs aggravate drive fragmentation thus are GUARANTEED to slow down system performance

Mac OS has defragments all files smaller than 20 MB whenever they're opened.

On my system there are 28 files that are larger than that assuming you ignore the iLife media (which should have been laid down in a single contiguous write when they were installed and wouldn't be touched by the installer anyway).

I think you'll find that's not true, download the demo version of iDefrag and just run the analysis scan, you'll see that 99% of the files on your hard drive are way more then 20MB, for example, system and swapfile.

I defraged a two month old Leopard install last night and got the boot time from 30 seconds to 12 seconds :p

Download the demo version of iDefrag and just run the analysis scan

I did: see the attached screenshot: it lists my system at 0.1% fragmentation (assuming I'm reading its statistics tab correctly).

This is a current-gen iMac (3 GB ram) upgraded from 10.4 to 10.5 two days ago. It has the standard assortment of applications you'd expect to find in a new-media/marketing firm. Photoshop, Illustrator, Compilers, Finalcut, office, etc.

Maybe it's returning bogus information? The product page indicated it wasn't leopard compatible.

you'll see that 99% of the files on your hard drive are way more then 20MB, for example, system

I think you'll find the opposite is true:

Count the number of files in /system large than 20 MB
(me@work : /system)$ sudo find . -name "*" -size +20000k | wc -l
	  17

Count the number of files in /system not larger than 20 MB
(me@work : /Library)$ sudo find . -name "*" -size -20000k | wc -l
  321053

You're off by 5 orders of magnitude.

Other directories like /Library, /bin, /Applications are in a similar state.

and swapfile.

The files in /private/var/vm are created and destroyed as needed: trying to defragment them is pointless. (see: Mac OS X - A Systems Approach) as they won't necessarily exist past the current session never mind across reboots.

For the record, dont run iDefrag on Leopard, as they state on their site this can cause some very nasty problems, instead boot of the iDefrag DVD you burn after buying the product.

My Mac loves defragging. Try a full defrag sometime booting from the dvd

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

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!