Dave's PC Mac OS
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software. SafariDAVclient taking 100% of CPU on Mac OS X 10.7.2 October 24, 2011 By David Wind I have a customer that recently bought a new Mac Mini to replace an older Mac Mini.
macOS Transformation Pack will give you all new macOS user experience such as theme, wallpapers, system resources, and new OS X features combined altogether in single package working on Windows platform since Windows XP to up to Windows 10. In this package, you’ll have the best user experience greatly resembles real macOS from Windows side.
- Windows Version is Coming Soon! Can you save Dave's PC From a harmful, well-known creepypasta virus?! Made for Cursed!!!
- Here at Dave’s Computers in New Jersey, we like all kinds of operating systems. We like Windows, Linux, Raspberry Pi, Chrome OS and Mac OS. It is this latter that we are going to discuss today as there has been a new OS version released called Mojave. Mac OS Mojave is more interesting than usual because it includes some new features.
Features:
– Seamless installation and uninstallation giving users safe transformation
– Easily configurable in single click with intelligence Metro UI design
– Designed for all editions of Windows XP/Vista/7/8/8.1/10 including Server Editions
– Genuine macOS system resources
– Smart system files updating with auto-repair and Windows Update friendly
– UxStyle memory patching
– macOS themes, wallpapers, user pictures and logon screen
– macOS Finderbar emulation as the most authentic port with real Finderbar functions
– OS X Dock emulation with pre-configured docklets optimized for stability/performance
– macOS Frame UI including Aero/Mac features for XP and non-Aero system
– Dashboard and Spaces with shortcut keys configured
– Launchpad access from desktop corner and Dock configured
Credits:
UxStyle memory patching: http://www.uxstyle.com
UltraUXThemePatcher: http://www.syssel.net/hoefs/index.php
Mac Lion 3.0 for Windows XP: http://HeyItPaul.deviantart.com
Aqua SL for Windows Vista: http://Lukeedee.deviantart.com
OS X Yosemite Theme for Windows 7: http://cu88.deviantart.com
OS X Yosemite Theme for Windows 8/8.1: http://cu88.deviantart.com
OS X Yosemite Theme for Windows 10: http://cu88.deviantart.com
Mac Os El Capitan Cursor Pack for Windows: http://arnoldantonio.deviantart.com
Flurry screensaver: http://www.maddogsw.com/flurry
Windows 7 system files resources base: http://sagorpirbd.deviantart.com
Windows XP/Vista system files resources base: http://asilaydyingdl.deviantart.com
iOS 7 icons: http://iynque.deviantart.com
Yosemite icons: http://cjchristianjoel.deviantart.com
ViFind: http://www.lee-soft.com
RocketDock: http://www.rocketdock.com
StandaloneStack: http://www.chrisnsoft.com
XWidget/XLaunchpad: http://www.xwidget.com
TrueTransparency: http://www.pngfactory.net/customxp/TrueTransparency
VirtuaWin: http://virtuawin.sourceforge.net
WinaeroGlass: http://www.winaero.com
OldNewExplorer: http://www.msfn.org/board/topic/170375-oldnewexplorer-117/
LeftSider: http://hsiw.web.fc2.com
Y’z Shadow: http://yzapps.blog24.fc2.com
gdipp: https://code.google.com/p/gdipp/
Changelog:
Version 5.0
-Added new High Sierra and Mojave wallpapers
-Changed Windows 10 theme to use default Aero theme for compatibility reason
-Updated Resource Hacker to version 5.1.7
Version 4.0
-Added El Capitan desktop icons in theme files
-Added more Sierra wallpaper
-Added multiple versions of Windows 10 theme installation support (TH/TH2/AE)
-Added Windows 10 Anniversary Edition v1607 support
-Changed product name to macOS Transformation Pack
-Disabled font rendering engine on Windows 10 Anniversary Edition to (bug on major controls)
-Fixed installation bugs with permission on other cases
-Removed changing Windows 10’s logon screen for now to avoid corrupting logon system on Windows 10 v1607
-Removed some old Helvetica Neue fonts to fix thin font rendering
-Removed Windows 10 v1511 theme installation workaround (still add permissions for manual hack)
-Updated Windows 10 v1607 themes by cu88 from free releases (You can buy full version with more themes)
Version 3.2
-Added Sierra wallpaper
-Fixed installation bugs on non-English OS (Proper)
Version 3.0
-Added Windows 10 logon screen modification
-Improved theme patching reliability in Windows 10
-Improved ViFind’s startup reliability
-Updated cursors with Mac Os El Capitan Cursor Pack for Windows by arnoldantonio
-Updated FinderBar skin
-Adjusted transparency and border strength
-Reduced shadow strength
-Updated RocketDock skin
-Adjusted background transparency and white level
-Adjusted separator strength
Version 2.0
-Added checksum correction after modifying system files
-Added disabling Spaces feature (VirtuaWin) on Windows 10
-Added ViFind, the perfect FinderBar emulation software developed by Windows X & Lee Matthew Chantrey
-Fixed losing pnidui.dll backup file on Windows 8/8.1/10
-Fixed Windows 10 November Update incompatibilities
-Fixed system files modification that may modify x86 program files instead of x64 ones.
-Fixed system files version detection bug on Windows 10
-Improved font rendering on Dock
-Included uxworker.exe file into uninstaller software in case of deletion by antivirus
-Updated cursors with Mac Os X El Capitan Cursor Pack For Win by spysees
-Updated OldNewExplorer configuration for Windows 10 compatibility
-Updated Windows 10 visual style with Yosemite Theme For Windows 10 November Update by cu88
Version 1.0
-Added battery/network tray icon on Windows 8/8.1/10
-Added El Capitan wallpaper from new OS X El Capitan 10.11
-Added OS X font rendering engine (gdipp)
-Added UltraUXThemePatcher auto-removal during installation
-Changed Dock’s font color to black
-Changed theme engine back to UxStyle with installer fixes
-Fixed bug that cause blank navigation pane on x86 software (If you already having this issue, you need to apply our blank navigation pane fixer before installing)
-Fixed permission problems to make changes in bundled features
-Fixed replacing system files bugs on x64 system
-Fixed system files version comparing bug with Windows 10
-Fixed taskbar configuration not working in Windows 10
-Fixed theme applying bug in Windows 10
-Fixed Windows version detection bug with Windows 10
-Fixed x64 system files modification failure on Windows XP x64 platform
-Improved x64 system files modification using single method with better compatibility
-Removed Helvetica Neue Medium/Light/UltraLight type fonts to fix font render glitches on some apps
-Updated OldNewExplorer to version v1.1.7
-Updated Resource Hacker software to version 4.2.5
-Updated UXStyle engine to most recent version
-Updated Windows 10 visual style with Yosemite Theme For Windows 10 RTM by cu88
Awards:
CHIP – “The “Mac OS X El Capitan Transformation Pack” grabs Windows in a new garment.”
DownloadTyphoon – “OS X Mavericks Transformation Pack will give you all new OS X Mavericks user experiences combined with iOS 7 graphics such as theme, wallpapers, system resources, and new OS X features combined altogether in single package working on Windows platform since Windows XP to up to Windows 8.”
Download macOS Transformation Pack 5.0 at ThemeMyPC.net
Here at the Happy Macs Lab, we have a unique issue. In the lab, you will find vintage Power Macintosh models, running everything from Mac OS 7.5.3 up through Mac OS 9.1, a maxed out Power Mac G4 Cube running all of Mac OS 9.2.2, Mac OS X Tiger and Mac OS X Leopard, Power Mac G5s running Mac OS X Tiger and Mac OS X Leopard, multiple older PCs running various versions of Linux and even a sampling of older Windows machines, running Windows NT 4.0, Windows 95, Windows 98SE, Windows ME, Windows 2000 and finally Windows XP. It is quite the “tower of babel” from a computing perspective, and getting all these machines to talk to each other is a real challenge.
Happily, there are multiple solutions that achieve the desired result, and this blog post is the first of a series where we will look at the best of them, one by one. Some of the solutions are point-to-point, connecting just one OS to one other OS (such as Mac OS to Windows), and some are all encompassing, connecting everything to everything.
In this first post of the series, we will look at the first of two “traditional” point-to-point solutions for connecting Mac OS Classic and Windows, Thursby Software’s Dave. In the second post of this series, we will examine the other classic solution to this problem, Connectix’s DoubleTalk.
Throughout this series of networking posts, “Mac OS Classic” is used to imply Mac OS 9.x and lower, and specifically excludes all versions of Mac OS X. Similarly, throughout this series of posts, “Windows” implies Windows NT 4.0 and higher. For the purposes of this series, I used two principal Macs, a Power Macintosh 7500/100, upgraded with a NewerTech 366 MHz G3, and running Mac OS 8.6, and a fairly stock Power Macintosh 7300/200 running Mac OS 9.1. I used a 200 MHz dual CPU Pentium Pro PC running Windows NT 4.0 as the Windows representative in this networking duet.
Windows, Networking and SMB
OK, lets get going. A little background is in order first. Windows communicates with the networked world using the Server Management Block (SMB) protocol, renamed CIFS (Common Internet File System) in later versions of Windows. Pretty much all versions of Windows since Windows NT 3.x have incorporated both an SMB server and an SMB client, meaning that the OS can both read and write other SMB-based machines and can itself be read and written by those same other machines. I have seen, but not yet been able to confirm, that even the creaky Windows for Workgroups 3.11 included an SMB capability.
Since Windows speaks SMB, if a Mac wants to engage in file sharing with a Windows platform, it needs to speak SMB as well. Functionally speaking, this means that it needs to implement an SMB server and /or an SMB client. The two well-regarded third party applications mentioned above, Thursby Software’s Dave and Connectix’s DoubleTalk, do just this.
Thursby’s Dave seems to be the preferred solution in this space, although both garner a recommendation on Apple’s website.
Dave is preferred because it implements both an SMB server and an SMB client, while DoubleTalk only implements and SMB client. Having both an SMB server and an SMB client, a Dave-equipped Mac can seamlessly read and write files to and from a Windows machine and that Windows machine can seamlessly read and write files to and from the Mac.
Installing and Configuring Dave
I tested Dave and can attest that this is all true. I loaded Dave onto my Power Macintosh 7500, running Mac OS 8.6, and took it for a spin. The above mentioned 200 MHz Pentium Pro PC, running Windows NT 4.0, acted as its Windows counterpart in this testing.
Now before we go any further, there is a pink elephant in the room that we should all acknowledge. Astonishingly, not only is Thursby still a going commercial concern, Dave is still an active product at Thursby, and they want a staggering $119 for a current license for it! This will no doubt stop many folks from experimenting with it further.
Of course, the Dave software, and license numbers for it, are available from multiple “abandonware” sites, but none of the licenses I could find this way worked – all were rejected by Dave as “expired”. Thursby has protected their product well. Already having a valid Dave 4.0 license, I was able to proceed, but those of you not in this happy position will need to either pony up a big $119 to Thursby, or make your peace with trolling the web in search of non-expired licenses. I did this yesterday as a test, and successfully unearthed multiple apparently valid licenses. A little bit of persistence may serve you well in this area.
In an effort to save would be users of Dave from having to pay the hefty $119 fee for what is fundamentally an obsolete product, I queried Thursby’s email support, asking if they would be willing to provide a free license, given the lack of remaining commercial trade in Mac OS 9.x and below. The answer back was a firm “no”, followed by an admonition that Dave should not be considered abandonware. The response concluded with a request to know where I had downloaded Dave from! Realizing that this line of inquiry was not likely to result in a free Dave license, I abandoned it and moved on.
I will leave the licensing issue in your capable hands. Moving on, I can report that Dave is an excellent product. It was simple to install and configure, easy to use, and 100% effective at doing what it said it would do.
Installation and setup was a snap.
Dave’s setup runs you through a few simple questions, the most complex of which may be its query for your workgroup name. If you don’t know the answer, just type in “WORKGROUP”, which is what most PCs default it to. Confirm this by visiting the Network control panel of the PC you are trying to connect to, and change the name on the PC side or the Mac side, if need be. Once the installation is done, you will need to restart your Mac and then you are ready to network with your PC friends.
Networking with Dave: Mac to PC
Dave's Pc Mac Os 11
Networking with Dave from a Mac to a PC is quite intuitive, in a very Mac OS Classic sort of way – you go through Chooser, just like you would for the native form of Mac networking. In Chooser, you will now be greeted by a new connection type in the left hand pane, Dave Client.
When you click this, there will be a disconcerting pause, during which you will wonder whether Dave is working at all, and then the right hand pane will suddenly populate, hopefully showing you the PCs you want to share files with (and anything else on your network that has an SMB server – in my case, this included two Power Mac G5s and my current main Mac, a 2012 27” iMac).
Double click the entry for the PC of interest (in this case it was DualPro200 – so named because it is a dual CPU Pentium Pro 200 MHz) and you will get the expected password prompt. Enter the correct user name and password (this is the user name and password from the PC, or just select Guest instead) and Chooser will pop up a dialog showing the “shares” on the selected PC that are available for you to choose from (a “share” is SMB-speak for an available, shared folder).
You may just run into some trouble here – I did. Initially, the share list was blank! There is not a lot of latitude to share files when the list of possible sharing targets is empty! Happily, Dave provides an “Add Share” button below the list, and I took advantage of this to add the shared folders on the PC to the dialog.
This point requires a brief moment of explanation. When you share a folder in Windows NT 4.0, you give it a “Share Name”. This name should show up in the list of available shares that Dave presents you, but in my case, it did not. The share name did show up in the list of available shares when I connected to the PC from either of my Power Mac G5s, but did not from my older Power Macintosh 7300 or 7500 machines. The reason for this will be explained in a postscript at the end of this post.
For now, I was presented with a blank list of shares, but had the potential of adding shares through the Dave “Add Share” dialog. Back at the Pentium Pro PC, I went to Control Panels -> Server, and clicked the Shares button. This presented me with the following list of the available shares:
As you can see there were a LOT of shares there, but most ended with the “$” sign, indicating that they were administrative shares, automatically created by and internal to Windows NT, and not generally advertised for external connection (although they can be connected to if you wish).
Mac Os Download Windows 10
I took note of three shares of interest, C$, D$ and DP200SharedFolder, which corresponded to C:, D: and the folder I was actually trying to share, DP200SharedFolder. One by one, using Dave’s Add Share button, I added these to the list, and they worked. When I double clicked any one of them, Dave promptly mounted the appropriate share on the Windows NT machine and at that point, I could drag and drop, read files, create folders, and in general, do all the things I could do with any local file folder.
I must apologize for the loss of continuity in the screen shot above. The share name mounted on the desktop is different from what is described – I no longer have the original screen shot.
Setting aside the cause of the blank list of shares for a moment, Dave’s Add Share dialog allowed me to work around a potentially show stopping issue and arrive at networking success, at least in the Macintosh to PC direction. What about the other direction, PC to Macintosh?
Networking with Dave: PC to Mac
This was not such a happy story initially. The Power Macintosh 7500 simply did not show up at all in the Network Neighborhood of the PC, nor could I see it in the Network selection of the two G5s I have on the network (both running 10.4.11 Tiger). Guessing that Dave’s SMB server was not enabled, I went hunting for a Dave Control Panel on the Macintosh. Nope, no such thing. There WAS a NetBIOS control panel with Dave labeling in it, so I hunted around in there, but there were no obvious selections to enable or disable visibility of the SMB Server.
My next stop was the Dave installation in the Macintosh’s Applications folder. There was a single file there, a program named, appropriately enough, Dave. Following this obvious lead, I launched the program, selected Dave Sharing and was greeted with what amounts to a Dave control panel.
Of course I immediately noticed that File Sharing was off, which would imply that the Dave SMB Server was not running. I enabled this and then checked to see if Dave was sharing any folders. The list at the top of the window was empty suggesting that it was not. Using Finder, I dropped my AppleTalk shared folder, “PowerMac7300SharedFolder” into the list. It “took” and thereafter, Dave showed that it was sharing this folder. It did warn me that shares with names over 12 characters long might not share properly, but I ignored that for the moment.
Again I must offer my apologies for the discontinuity in the image above – the file share name is slightly different from what I have described – I seem to have misplaced the original screenshot.
Back at the Windows NT machine, success. The Power Macintosh 7500 now showed up in the Network Neighborhood. I double clicked the icon, full of confidence that I had solved the problem, and was greeted with … a blank window. The PC could see the Macintosh, but the Macintosh didn’t appear to be sharing anything. I checked this with both of the G5s, and Tiger pretty much agreed – there was nothing being shared. Tiger’s rather obscure way of indicating this to me was to tell me that it could not open the alias because the original item could not be found. Somewhat of a misleading error indication, but I got the message. Something was still definitely wrong at the Macintosh end.
I went back to the Dave application and removed the current folder I was sharing, suspecting that either you could not share a folder over both AppleTalk and SMB, and/or perhaps the file name really DID have to be 12 characters or less. I created a new folder called “PMAC7500-SMB” (EXACTLY 12 characters) and dropped it into the Dave “Shares” list. I specifically did not share this folder through the usual Mac OS way of doing this – it was only shared via Dave’s SMB server.
This did the trick. The Network Neighborhood window that I got when I doubled clicked the icon for the Power Macintosh 7500 now presented one accessible folder, PMAC7500-SMB. This folder could be opened, read, written to… it was fully accessible. Success! PC to Macintosh networking was now up and running as well.
Networking with Dave – Summary
With both Mac to PC and PC to Mac networking up and running, I can now summarize the recipe for success with Dave:
- On the Macintosh side, make sure you have a unique share folder for Dave, and make sure that the name of that folder is less than 12 characters. Do not share this folder via the normal Mac OS Sharing mechanism. Share it only via Dave.
- On the PC side, make sure that you have one or more shared folders, and take note of the “Share As” name you assign to each. Like the Macintosh side, keep the filename of each shared folder to 12 characters or less as well.
- Still on the PC side, if you CANNOT keep the share names to 12 characters or less (perhaps the machine is not under your control), compensate for this on the Macintosh side. On that side, when you use Chooser to select the PC, if you are greeted with a blank list of available shares, use Dave’s Add Share button to manually add the shares whose names you took note of in the last step. You will only have to do this once. Dave remembers the names.
- That’s it! Apply the above and you should be happily networking in both directions between a Macintosh running Dave and a PC running Windows NT 4.0.
Closing Thoughts
Dave's Pc Mac Os X
A final note on Dave. Dave will very considerately interrupt the Macintosh shutdown sequence to warn you if it is hosting any connected users, giving you a chance to warn them before their favorite Mac suddenly disappears from cyberspace. As I said above, Thursby has done a very nice job.
That’s it for this post. In our next post on networking, we will look at doing the same sort of thing using the other classic application in this space, Connectix DoubleTalk. Until then, happy networking with Dave!
The Promised Postscript on The Empty Share List Problem
p.s.> A postscript to this story. As outlined above, the “empty list of shares” problem is easily resolved. Reasoning that since Dave warned that Macintosh share names over 12 characters might not share correctly, I concluded that perhaps share names on the Windows NT side should ALSO be 12 characters or less. I went back to the Windows NT 4.0 machine and checked the length of the share name for the folder I was trying to share. Sure enough, it was MUCH longer than 12 characters. When I shortened it to 12 characters (8 characters actually, in this case), it showed up instantly in the Chooser selections of both Mac OS Classic machines. So, one final word to the wise – all share names should be 12 characters or less.
And as if that is not enough, Windows NT 4.0 gently reminds you that if you want the share to be visible to DOS and Windows 3.x class machines, its’ name needs to be 8 characters or less! Just so you know…. 🙂