I have some services and scheduled tasks that call a Batch file under windows. The scheduled tasks cannot access network drives that the assigned user has defined, but luckily there is a “mount” pendant within Windows as well.
To mount a network share within the Batch script use:
net use t: \\server\share /persistent:no
The authentication is taken from the user that is assigned to the task.
If this not enough use
net use t: \\server\share /persistent:no /user:user@domain password
To unmount the share use
net use t: /delete
Share This
Under Windows 2k and XP exists no keyboard shortcut in cmd.exe to copy and past text. You need not only use your mouse but hit the proximity icon in the top left and choose edit|mark, edit|copy and so on.
cmd has a special mode named QuickEdit which can be enabled via the following command
REG.EXE add HKCU\Console /v QuickEdit /t REG_DWORD /d 1 /
all new cmd windows will now be in QuickEdit mode. Text can be selected with the left mouse button, copied via right mouse button and pasted via right mouse button.
Found on a msdn blog. Thanks!
Share This
A Microsoft employee describes installing Vista on his Dell Machine as a “personal hell”:
It said “Copying files 0%”. And there it stayed. I left for half an hour, came back and it had copied files but was at “Expanding files 1%”. I went to bed, woke up the next morning expecting to see a shiny new Vista to play with. Instead it said “Expanding files 24%”. I thought it had hung, but no: every few minutes the drive would spin up, and every 15 minutes the percentage would go up by 1. I estimated it would take 30 hours to expand the files at this rate, so I left it running all weekend. After a total of about 40 hours, I saw a login prompt. I logged in, and sat looking at the Vista background for eons, and went to work (the weekend being over and all). When I came home the machine had black-screened.
Read the full text here.
The weirdest thing i found in the comments:
I tried an install of Vista recently to try it out as a media center machine. I couldn’t see any of the machines on my network, until I remembered I’d need to change the workgroup name.
I did that, and Vista told me that I would need to reboot in order for the workgroup name change to take effect.
Are. They. F-ing. Kidding. Me?
After all this years, Windows needs to reboot after changing the workgroup… Welcome in 2007. *sigh*
Share This