Saturday, May 22, 2010

Mac OS X 10.6 and Samba browsing sucks! Wait, no!

https://doc.ikw.uni-osnabrueck.de/node/3211
http://rydberg.biology.colostate.edu/sites/bioit/2009/11/10/snow-leopard-and-samba-for-pangea/

Mac OS X Snow Leopard (a.k.a 10.6) has introduced a great and annoying bug. One can not browse Samba shares if the veto files option is used on the Samba server. Ususally one wants to have the .DS_Store et al. files gone on your network share.

But, no you need to turn that option of. Or at least take the Apple-specific files out of that list in /etc/samba/smb.conf:

delete veto files = Yes
veto files = /lost+found/Network Trash Folder/TheFindByContentFolder/TheVolumeSettingsFolder/
# Bad OS X files, but necessary for Snow Leopard:
#.AppleDB/.AppleDouble/.DS_Store/._.TemporaryItems/.TemporaryItems/

After a restart of Samba things work again.

Snow Leopard and SAMBA for Pangea

With the release of Snow Leopard (Mac OS X 10.6) there have been reports of slowness, and hanging of the Finder when attempting to access SAMBA (SMB) network shares. SAMBA network shares are essentially the most popular type of network share in use today, and the primary method of sharing files between Macintosh computers and Windows computers.



Unfortunately for us, Pangea uses SAMBA to share its files. So, we have been experiencing these symptoms, primarily the hanging of Finder when attempting to browse through sub-directories within your Pangea space. For the past couple of months since Snow Leopard has been released, I have been patiently monitoring several forum threads for a solution as well as silently hoping that the releases of 10.6.1 and 10.6.2 would address and fix these issues automatically. This has not happened.

On the other side, these forum threads have provided a solution to this problem which I have implemented on the Pangea server. This solution was to remove a line in the Pangea SAMBA configuration file that prevented certain files from being created by Apple client computers (those of you connecting to Pangea with your Macintosh computers). This line is called the ‘veto file’ setting is now turned off and Macintosh computers will start freely placing these strange files onto the Pangea spaces they access. These files include .DS_Store, .AppleDesktop, .AppleDouble, and .Trashes to name just a few. These files will not be visible to Macintosh computers, but will start showing up in the file lists for Windows computers. The important thing is that this has solved the SAMBA access issues with Finder.

So, for the end users who glaze over with the above technical explanation – Snow Leopard can now access Pangea normally, but will be creating strange files and folders (.DS_Store, .AppleDesktop, .AppleDouble, .Trashes, etc.) which will only be viewable by Windows clients on default.

Thank you for your patience with this, and I will remain optimistic that at some point the future I can re-enable the ‘veto file’ line. Enjoy!

Saturday, May 1, 2010

Reset Rearms on Windows 7

File download: https://skydrive.live.com/?cid=89aad82d547ec2c5&sc=documents&uc=1&id=89AAD82D547EC2C5%21231#

http://www.mydigitallife.info/2010/05/05/how-to-reset-available-remaining-rearm-count-in-windows-7/
(cached: http://www.webcitation.org/5tEfzv82h)

http://forums.mydigitallife.info/threads/16541-KB971033-WATu-and-activation-CLI-Commands
(cache: http://www.webcitation.org/5pOwYAi6y)

http://bramjnett.com/forums/145101-post1.html
(cache: http://www.webcitation.org/5pOwevh68)

http://technet.microsoft.com/en-us/library/dd772269.aspx

http://technet.microsoft.com/en-us/library/ff793406.aspx
(cached: http://www.webcitation.org/5tEfvb0Pz)



Reset Rearms
This will set the rearm count to 4.
Save the following in the root of the windows drive (eg: c:\resetrearm.cmd)
Code:
reg load HKLM\MY_SYSTEM "%~dp0Windows\System32\config\system"
reg delete HKLM\MY_SYSTEM\WPA /f
reg unload HKLM\MY_SYSTEM
You could do it directly with
Code:
echo reg load HKLM\MY_SYSTEM "%~dp0Windows\System32\config\system" & reg delete HKLM\MY_SYSTEM\WPA /f & reg unload HKLM\MY_SYSTEM > %SystemDrive%\resetrearm.cmd
Next boot off of Windows DVD. At opening menu press Shift+F10 to get cmd prompt. Locate Windows drive. In systems the hidden 100MB partition may show as c: and Windows on D: type:
Code:
d:\resetrearm
Exit and restart the computer. You may be prompted to enter a product key. If so hit cancel. Regardless you will have to enter a product key.
Open a command prompt, and use cslmgr /ipk (or slmgr /ipk) to enter a default key (from sources\products.ini) listed here:
http://forums.mydigitallife.info/thr...884#post122884
Ref
Last edited by WinFLP; 03-20-2010 at 11:15 AM.

----------------------------------------------------------------------------------------------

 GUIDE: How to really run Windows 7 forever without applying any cracks
Hi there,

Before applying the method I'm about to describe, I had installed several Windows 7 machines applying several crack flavors (RemoveWAT, Chew-WGA, etc). I can't complain, they worked wonderfullly for a few months, but after that the annoying messages returned. You know what I mean, those ones that pop up right before you log in and say things like "Your windows is illegal" or "Your license is counterfeited" or "We're going to annoy you with these messages everyday you damn pirate". After some reading I found out that the cracks were being de-activated by Microsoft via the "Windows Updates". Some people even had the exact KB number marked so we could uninstall it or prevent its download. I was not confortable with that, 'cause I simply didn't have the time to read each and every update before downloading. So what I did for a couple of times is download new versions of the cracks and re-apply them. This worked but only temporarily. It's when realized that this was going to be an eternal run and chase between the crackers and M$.

Then I luckily found a thread in this forum which uncovers great data about WPA. This method will leave your system eternally in an "Initial Grace Period", so you won't have to worry about patrolling "Windows Updates" or running .exe files and not knowing what they are doing on the background. Before listing the steps that I successfully followed there's something I want to make clear: the ideas for this Guide are not mine, not at all. I'm just collecting info based on a specific thread and this magic post (thanks to all the gurus).

This Guide is for:
- People who aren't happy applying cracks, .exe's and are tired of playing run and chase with M$.
- People who don't mind executing simple commands every 30 days / 120 days.
This Guide is not for:
- People who just want to apply a patch or crack and forget about the rest. This method will require you to do things recurrently.

THE GUIDE

1) Create a batch file with the following commands:
Code:
reg load HKLM\MY_SYSTEM "%~dp0Windows\System32\config\system"
reg delete HKLM\MY_SYSTEM\WPA /f
reg unload HKLM\MY_SYSTEM
To achieve this, run notepad as administrador and paste the code above. Then save it with name delwpa.bat as type "all files" on drive C:\ at the root level.
2) Restart the machine and press F8 right after the BIOS screen to get to the Advanced Boot Options.
3) Select Repair your Computer, select your Input language, enter your Login details and Open Command Prompt.
4) Type C: to go to the main drive. Then type dir to get the list of files where you should see the file delwpa.bat created in Step 1).
Execute the file by typing it:
Code:
delwpa.bat
The console should display messages saying that the commands were executed successfully. Close the console window and reboot the machine.
NOTE: When testing on a Virtual Machine the C: drive appeared as D:, but for a real machine it should normally be C: (as tested). Just find the drive with the delwpa.bat file.
5) Back on Windows: login and don't worry if the desktop shows a message like "This product is not genuine". Just ignore it.
Run Command Prompt as administrador, and execute:
Code:
slmgr /ipk D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV
Then perform a final reboot on your machine.
6) After the reboot, check that everything is alright by running a command prompt as administrator and executing:
Code:
slmgr /dlv
Wait for a few seconds and you should get a window with lots of data. This is what we're interested in:
License Status: Initial Grace Period
Time remaining: 30 days
Remaining windows rearm count: 4

And that's it! Just like a brand new windows. Now all you have to do is wait 30 days, execute a rearm and you'll be fine. This rearm will add another 30 days to the grace period. The command for a simple rearm is:
Code:
slmgr /rearm
(remember to always run the command prompt as administrator).

VERY IMPORTANT: Windows will let you do a rearm 4 times only, meaning that you will have a maximum of 120 days Grace period. After those 120 days you should follow the Guide again to reset the rearm count. If you decide to always keep the delwpa.bat file on your computer, then all you need is to follow steps 2-6.

So this Guide is basicaly a matter of timing. Create your alerts in Outlook or whatever is the program you use for tasks, and set reminders every 30 days for simple rearms, and every 120 days for resetting the rearm counts.

Hope it helps!

Tested on:
- Real and virtual machines x64, x86 (With previous RemoveWAT installations and Without any previous cracks installed)

Mc

Mimmo97 Blog Archive