Removing the DELETE permission from the USERS group on a file / folder prevents deletions, moves, and renaming critical file data. That's what everyone asks for.
Unfortunately, it also prevents the deletion of TEMP files generated by editing Word, Excel, etc. documents with those folder permissions. If you are accustomed to right clicking those folders and creating new files and sub folders, you will also be prevented from renaming them.
Add the CREATOR OWNER user and allow modifications there.
The TEMP files are a by product of the CREATOR, despite the file being edited by someone else. They will now be deleted appropriately. The creator will be able to add and name files or folders any way they choose. All other users will be prevented from deleting, renaming, and moving that data.
The caveat is the creators CAN delete them.
Diary of technical happenstance, simple Internet accessible scratchpad, and brain dump to save myself later
Friday, March 31, 2006
Sunday, March 12, 2006
DCOM error, event ID 10021
Where do the 10 or so errors in the System event log without much infor come from? A9E69610-B80D-11D0-B9B9-00A0C922E750 is the application ID for the IIS Admin service, and you probably find an event referencing the fact that you disabled it for securtiy reasons later in the log.
Go to Administrative Tools | Component Services | Computers | My Computers | DCOM config. Right click IIS Admin Service to access properties and set the securitie values to default. Errors go away.
If you find message boxes poping before being able to access this form, I am guessing at this point it is the result of some sort of registry cleanup tool. I am currently concerned about people betting the farm on CCleaner.
Go to Administrative Tools | Component Services | Computers | My Computers | DCOM config. Right click IIS Admin Service to access properties and set the securitie values to default. Errors go away.
If you find message boxes poping before being able to access this form, I am guessing at this point it is the result of some sort of registry cleanup tool. I am currently concerned about people betting the farm on CCleaner.
Sprint AirCard 580
When installing a Sprint AirCard 580 in a laptop with BlueTooth enabled devices, you may run into "No Device" errors in the Sprint application.
It seems the Sprint AirCard likes to use com port 7 (COM7). Your Toshiba based implementation of BlueTooth appear to use as many as 12 com ports above 3. This means it likes to assume control of 7, what your AirCard is trying to use.
I found disabling the BlueTooth COM7 in device manager allows the AirCard to be recognized and function, and doesn't kill the BlueTooth mouse my executive marketing guy likes.
It seems the Sprint AirCard likes to use com port 7 (COM7). Your Toshiba based implementation of BlueTooth appear to use as many as 12 com ports above 3. This means it likes to assume control of 7, what your AirCard is trying to use.
I found disabling the BlueTooth COM7 in device manager allows the AirCard to be recognized and function, and doesn't kill the BlueTooth mouse my executive marketing guy likes.
Saturday, February 04, 2006
EliveCD Elightenment Debian resolution problem
There are plenty of posts around the web indicating you can resolve resolution problems in Debian by editing the etc/X11/XF86Config-4 file. I'm betting someone telling you what file to edit really doesn't help much. You wouldn't be reading this otherwise.
When running the EliveCD installed to hard disk, the Elightenment enviroment looked fabulous, but all the applications ran at very low resolutions. The problem occurs in both E16 and E17, and from liveCD and HD installs. After enableing randr (left click upper left corner | modules | Randr | enabled), I found the highest available resolution on the configuration menu was 640X480. During a reboot in verbose mode (F2 during cool Elive splash screens) I found XFree86 server using 640X480. So how do you change it?
Here's a real example that actually works:
snippet of the original etc/X11/XF86Config-4 file:
Section "Screen"
snippet of file with modifications:
Section "Screen"
I prevously tried modifying startup variables in GRUB like vga=788 instead of 791, depth=16 instead of 24, using the eliveCD graphics problems startup, etc. but none seem to make a difference.
Incidentally, I am running it on a PII 350mhz with 192MB RAM and the video card is a cheapo on-board AGP SIS6326 job. If I wasn't tied to MS by my office and my daughters' school, I would happily convert to this platform.
Hope this helps.
When running the EliveCD installed to hard disk, the Elightenment enviroment looked fabulous, but all the applications ran at very low resolutions. The problem occurs in both E16 and E17, and from liveCD and HD installs. After enableing randr (left click upper left corner | modules | Randr | enabled), I found the highest available resolution on the configuration menu was 640X480. During a reboot in verbose mode (F2 during cool Elive splash screens) I found XFree86 server using 640X480. So how do you change it?
Here's a real example that actually works:
snippet of the original etc/X11/XF86Config-4 file:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"Depth 1EndSubSection
Modes "640x480"
snippet of file with modifications:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"Depth 24EndSubSection
Modes "1280x1024" "1024x768" "800x600" "640x480"
SubSection "Display"Depth 1
Modes "640x480"
EndSubSection
I prevously tried modifying startup variables in GRUB like vga=788 instead of 791, depth=16 instead of 24, using the eliveCD graphics problems startup, etc. but none seem to make a difference.
Incidentally, I am running it on a PII 350mhz with 192MB RAM and the video card is a cheapo on-board AGP SIS6326 job. If I wasn't tied to MS by my office and my daughters' school, I would happily convert to this platform.
Hope this helps.
Wednesday, January 25, 2006
NEC 2400 IPX PMS integration
To move the PMS output from a serial port to the LAN see ASYDL.
ASYDL, SYS 1, INDEX 897, bit 0 = 1
ASYDL, SYS 1, INDEX 897, bit 4 = 0
Bit 4 is used for ACK/NAK control and is invalid when integrating with a Flagler / LMS system. Your results may vary.
Ethereal running on a hub card port is very revealing when troubleshooting conversation for the first time. L records and responses can be viewed in clear text.
ASYDL, SYS 1, INDEX 897, bit 0 = 1
ASYDL, SYS 1, INDEX 897, bit 4 = 0
Bit 4 is used for ACK/NAK control and is invalid when integrating with a Flagler / LMS system. Your results may vary.
Ethereal running on a hub card port is very revealing when troubleshooting conversation for the first time. L records and responses can be viewed in clear text.
Subscribe to:
Posts (Atom)