Writer's Block (Tobias Bruch) Mac OS

• Writer's Block (tobias Bruch) Mac Os 11
• Writer's Block (tobias Bruch) Mac Os X
• Writers Block (tobias Bruch) Mac Os X

Give yourself a pat on the back and pop the kettle on - you've earned it! I hope this tutorial has given you an insight into creating a novel on your Mac and please remember to share any top tips or other useful applications with our readers in the Comments section below! In the meantime, best of luck with writing your novel and I'll expect to see it in my local bookshop. Mac 275 Medium Angled Shading Brush. 4.7 out of 5 stars 6. Only 2 left in stock - order soon. SHANY Artisan's Easel – Elite Cosmetics Brush Collection, Complete Kabuki Makeup Brush Set with Standing Convertible Brush Holder, 18 pcs. 4.7 out of 5 stars 2,413.

A RAM drive (also called a RAM disk) is a block of random-access memory (primary storage or volatile memory) that a computer's software is treating as if the memory were a disk drive (secondary storage). It is sometimes referred to as a virtual RAM drive or software RAM drive to distinguish it from a hardware RAM drive that uses separate hardware containing RAM, which is a type of battery-backed solid-state drive.

Performance[edit]

The performance of a RAM drive is in general orders of magnitude faster than other forms of storage media, such as an SSD, hard drive, tape drive, or optical drive.^[1] This performance gain is due to multiple factors, including access time, maximum throughput, and type of file system.

File access time is greatly reduced since a RAM drive is solid state (no mechanical parts). A physical hard drive or optical media, such as CD-ROM, DVD, and Blu-ray must move a head or optical eye into position and tape drives must wind or rewind to a particular position on the media before reading or writing can occur. RAM drives can access data with only the memory address of a given file, with no movement, alignment or positioning necessary.

Second, the maximum throughput of a RAM drive is limited by the speed of the RAM, the data bus, and the CPU of the computer. Other forms of storage media are further limited by the speed of the storage bus, such as IDE (PATA), SATA, USB or FireWire. Compounding this limitation is the speed of the actual mechanics of the drive motors, heads, or eyes.

Third, the file system in use, such as NTFS, HFS, UFS, ext2, etc., uses extra accesses, reads and writes to the drive, which although small, can add up quickly, especially in the event of many small files vs. few larger files (temporary internet folders, web caches, etc.).

Because the storage is in RAM, it is volatile memory, which means it will be lost in the event of power loss, whether intentional (computer reboot or shutdown) or accidental (power failure or system crash). This is, in general, a weakness (the data must periodically be backed up to a persistent-storage medium to avoid loss), but is sometimes desirable: for example, when working with a decrypted copy of an encrypted file.

In many cases, the data stored on the RAM drive is created from data permanently stored elsewhere, for faster access, and is re-created on the RAM drive when the system reboots.

Apart from the risk of data loss, the major limitation of RAM drives is their limited capacity, which is constrained by the amount of RAM within the machine. Multi-terabyte-capacity persistent storage has become commoditized as of 2012, whereas RAM is still measured in gigabytes.

RAM drives use the normal RAM in main memory as if it were a partition on a hard drive rather than actually accessing the data bus normally used for secondary storage. Though RAM drives can often be supported directly from the operating system via special mechanisms in the operating system kernel, it is possible to also create and manage a RAM drive by an application. Usually no battery backup is needed due to the temporary nature of the information stored in the RAM drive, but an uninterrupted power supply can keep the entire system running during a power outage, if necessary.

Some RAM drives use a compressed file system such as cramfs to allow compressed data to be accessed on the fly, without decompressing it first. This is convenient because RAM drives are often small due to the higher price per byte than conventional hard drive storage.

History and operating system specifics[edit]

The first software RAM drive for microcomputers was invented and written by Jerry Karlin in the UK in 1979/80. The software, known as the Silicon Disk System was further developed into a commercial product and marketed by JK Systems Research which became Microcosm Research Ltd when the company was joined by Peter Cheesewright of Microcosm Ltd. The idea was to enable the early microcomputers to use more RAM than the CPU could directly address. Making bank-switched RAM behave like a disk drive was much faster than the disk drives - especially in those days before hard drives were readily available on such machines.

The Silicon Disk was launched in 1980, initially for the CP/M operating system and later for MS-DOS. Due to the limitations in memory addressing on Atari 8-bit, Apple II series and Commodore computers, a RAM drive was also a popular application on the Atari 130XE, Commodore 64 and Commodore 128 systems with RAM Expansion Units and on Apple II series computers with more than 64kB of RAM. Apple Computer supported a software RAM drive natively in ProDOS: on systems with 128kB or more of RAM, ProDOS would automatically allocate a RAM drive named /RAM.

IBM added a RAM drive named VDISK.SYS to PC DOS (version 3.0) in August 1984, which was the first DOS component to use extended memory. VDISK.SYS was not available in Microsoft's MS-DOS as it, unlike most components of early versions of PC DOS, was written by IBM. Microsoft included the similar program RAMDRIVE.SYS in MS-DOS 3.2 (released in 1986), which could also use expanded memory.^[2] It was discontinued in Windows 7. DR-DOS and the DR family of multi-user operating systems also came with a RAM disk named VDISK.SYS. In Multiuser DOS, the RAM disk defaults to the drive letter M: (for memory drive). AmigaOS has had a built in RAM drive since the release of version 1.1 in 1985 and still has it in AmigaOS 4.1 (2010). Apple Computer added the functionality to the Apple Macintosh with System 7's Memory control panel in 1991, and kept the feature through the life of Mac OS 9. Mac OS X users can use the hdid, newfs (or newfs hfs) and mount utilities to create, format and mount a RAM drive.

A RAM drive innovation introduced in 1986 but made generally available in 1987^[3][4] by Perry Kivolowitz for AmigaOS was the ability of the RAM drive to survive most crashes and reboots. Called the ASDG Recoverable Ram Disk, the device survived reboots by allocating memory dynamically in the reverse order of default memory allocation (a feature supported by the underlying OS) so as to reduce memory fragmentation. A 'super-block' was written with a unique signature which could be located in memory upon reboot. The super-block, and all other RRD disk 'blocks' maintained check sums to enable the invalidation of the disk if corruption was detected. At first, the ASDG RRD was locked to ASDG memory boards and used as a selling feature. Later, the ASDG RRD was made available as shareware carrying a suggested donation of 10 dollars. The shareware version appeared on Fred Fish Disks 58^[5] and 241.^[6] AmigaOS itself would gain a Recoverable Ram Disk (called 'RAD') in version 1.3.^[7]

Many Unix and Unix-like systems provide some form of RAM drive functionality, such as /dev/ram on Linux, or md(4)^[8] on FreeBSD. RAM drives are particularly useful in high-performance, low-resource applications for which Unix-like operating systems are sometimes configured. There are also a few specialized 'ultra-lightweight' Linux distributions which are designed to boot from removable media and stored in a ramdisk for the entire session.

Dedicated hardware RAM drives[edit]

There have been RAM drives which use DRAM memory that is exclusively dedicated to function as an extremely low latency storage device. This memory is isolated from the processor and not directly accessible in the same manner as normal system memory.

An early example of a hardware RAM drive was introduced by Assimilation Process, Inc. in 1986 for the Macintosh. Called the 'Excalibur', it was an external 2MB RAM drive, and retailed for between $599 and $699 US. With the RAM capacity expandable in 1MB increments, its internal battery was said to be effective for between 6 and 8 hours, and, unusual for the time, it was connected via the Macintosh floppy disk port.^[9][10]

In 2002, Cenatek produced the Rocket Drive, max 4 GB, which had four DIMM slots for PC133 memory, with up to a maximum of four gigabytes of storage. At the time, common desktop computers used 64 to 128 megabytes of PC100 or PC133 memory. The one gigabyte PC133 modules (the largest available at the time) cost approximately $1,300 (equivalent to $1,848 in 2019). A fully outfitted Rocket Drive with four GB of storage would have cost $5,600 (equivalent to $7,960 in 2019).^[11]

In 2005, Gigabyte Technology produced the i-RAM, max 4 GB, which functioned essentially identically to the Rocket Drive, except upgraded to use the newer DDR memory technology, though also limited to a maximum of 4 GB capacity.^[12]

For both of these devices, the dynamic RAM requires continuous power to retain data; when power is lost, the data fades away. For the Rocket Drive, there was a connector for an external power supply separate from the computer, and the option for an external battery to retain data during a power failure. The i-RAM included a small battery directly on the expansion board, for 10-16 hours of protection.

Both devices used the SATA 1.0 interface to transfer data from the dedicated RAM drive to the system. The SATA interface was a slow bottleneck that limited the maximum performance of both RAM drives, but these drives still provided exceptionally low data access latency and high sustained transfer speeds, compared to mechanical hard drives.

In 2006, Gigabyte Technology produced the GC-RAMDISK, max 8GB, which was the second generation creation for the i-RAM. It has a maximum of 8 GB capacity, twice that of the i-RAM. It used the SATA-II port, again twice that of the i-RAM. One of its best selling points is that it can be used as a boot device.^[13]

In 2007, ACard Technology produced the ANS-9010 Serial ATA RAM disk, max 64 GB. Quote from the tech report: The ANS-9010 'which has eight DDR2 DIMM slots and support for up to 8 GB of memory per slot. The ANS-9010 also features a pair of Serial ATA ports, allowing it to function as a single drive or masquerade as a pair of drives that can easily be split into an even faster RAID 0 array.'^[14]

In 2009, Acard Technology produced the ACARD ANS-9010BA 5.25 Dynamic SSD SATA-II RAM Disk, max 64GB. It uses a single SATA-II port.

Both variants are equipped with a CompactFlash card interface located in the front panel, allowing non-volatile data being stored on the RAM drive to be copied on the CompactFlash card in case of power failure and low backup battery. Two pushbuttons located on the front panel allows the user to manually backup / restore data on the RAM drive. The CompactFlash card itself is not accessible to the user by normal means as the CF card is solely intended for RAM backup and restoration. Note that the CF card's capacity has to meet / exceed the RAM module's total capacity in order to effectively work as a reliable backup.

In 2009, DDRdrive, LLC produced the DDRDrive X1, which claims to be the fastest solid state drive in the world. The drive is a primary 4GB DDR dedicated RAM drive for regular use, which can back up to and recall from a 4GB SLC NAND drive. The intended market is for keeping and recording log files. If there is a power loss the data can be saved to an internal 4GB ssd in 60 seconds, via the use of a battery backup. Thereafter the data can be recovered back in to RAM once power is restored. A host power loss triggers the DDRdrive X1 to back up volatile data to on-board non-volatile storage.^[15][16]

See also[edit]

• Cache (computing), an area to store transient copies of data being written to, or repeatedly read from, a slower device

References[edit]

1. ^Kind, Tobias. 'RAMDISK Benchmarks'(PDF). University of California. Retrieved 2019-03-21.
2. ^Zbikowski, Mark; Allen, Paul; Ballmer, Steve; Borman, Reuben; Borman, Rob; Butler, John; Carroll, Chuck; Chamberlain, Mark; Chell, David; Colee, Mike; Courtney, Mike; Dryfoos, Mike; Duncan, Rachel; Eckhardt, Kurt; Evans, Eric; Farmer, Rick; Gates, Bill; Geary, Michael; Griffin, Bob; Hogarth, Doug; Johnson, James W.; Kermaani, Kaamel; King, Adrian; Koch, Reed; Landowski, James; Larson, Chris; Lennon, Thomas; Lipkie, Dan; McDonald, Marc; McKinney, Bruce; Martin, Pascal; Mathers, Estelle; Matthews, Bob; Melin, David; Mergentime, Charles; Nevin, Randy; Newell, Dan; Newell, Tani; Norris, David; O'Leary, Mike; O'Rear, Bob; Olsson, Mike; Osterman, Larry; Ostling, Ridge; Pai, Sunil; Paterson, Tim; Perez, Gary; Peters, Chris; Petzold, Charles; Pollock, John; Reynolds, Aaron; Rubin, Darryl; Ryan, Ralph; Schulmeisters, Karl; Shah, Rajen; Shaw, Barry; Short, Anthony; Slivka, Ben; Smirl, Jon; Stillmaker, Betty; Stoddard, John; Tillman, Dennis; Whitten, Greg; Yount, Natalie; Zeck, Steve (1988). 'Technical advisors'. The MS-DOS Encyclopedia: versions 1.0 through 3.2. By Duncan, Ray; Bostwick, Steve; Burgoyne, Keith; Byers, Robert A.; Hogan, Thom; Kyle, Jim; Letwin, Gordon; Petzold, Charles; Rabinowitz, Chip; Tomlin, Jim; Wilton, Richard; Wolverton, Van; Wong, William; Woodcock, JoAnne (Completely reworked ed.). Redmond, Washington, USA: Microsoft Press. pp. 907–909, 948–951. ISBN1-55615-049-0. LCCN87-21452. OCLC16581341. (xix+1570 pages; 26 cm) (NB. This edition was published in 1988 after extensive rework of the withdrawn 1986 first edition by a different team of authors. [1]Archived 2018-10-14 at the Wayback Machine)
3. ^Perry S. Kivolowitz (January 26, 1987). 'Overhead And Implementation Notes of ASDG RRD'. Newsgroup: comp.sys.amiga. Archived from the original on December 3, 2013.
4. ^Perry S. Kivolowitz (January 21, 1987). 'ASDG Recoverable Ram Disk News'. Newsgroup: comp.sys.amiga. Archived from the original on January 22, 2011. Retrieved September 23, 2014.
5. ^'README for disk 58'.
6. ^'README for disk 241'.
7. ^'Workbench Nostalgia: The history of the AmigaOS Graphic User Interface (GUI): Release 1.3'. Archived from the original on 2014-10-24. Retrieved 2014-09-30.
8. ^md(4) – FreeBSD Kernel Interfaces Manual
9. ^Groth, Nancy (January 27, 1986). 'Apple-Compatible Wares Introduced'. InfoWorld. 8 (4): 56. Retrieved 19 August 2020.
10. ^'What's New: Excalibur Adds Speed and Memory to Mac'(PDF). Byte Magazine. 11 (5): 38. May 1986. Retrieved 19 August 2020.
11. ^Mike Chin (2002-11-13). 'Blast off with Cenatek's Rocket Drive'. Silent PC Review. Archived from the original on 2018-02-03. Retrieved 2018-02-03.
12. ^Geoff Gasior (2006-01-25). 'RAM disk without the fuss'. The Tech Report. Archived from the original on 2018-10-05. Retrieved 2018-10-05.
13. ^Geoff Gasior (2006-06-06). 'Gigabyte boosts i-RAM speed capacity'. The Tech Report. Archived from the original on 2018-10-05. Retrieved 2018-10-05.
14. ^Geoff Gasior (2009-01-20). 'Solid-state storage from another angle'. The Tech Report. Archived from the original on 2018-10-05. Retrieved 2018-10-05.
15. ^'DDRdrive X1: Solid-State Storage Redefined'. DDRdrive LLC. 2014. Archived from the original on 2018-08-17. Retrieved 2018-10-05.
16. ^Geoff Gasior (2009-03-04). 'DDRdrive hits the ground running'. PC Perspective. Archived from the original on 2018-10-05. Retrieved 2018-10-05.

External links[edit]

• Unix shell command line to create a RAM disk on Mac OS X

[Disclaimer: I hate to be spied on and I happen to work for Adobe. I'm not speaking on behalf of Adobe, but only express my own opinion below. All tests below were done on a Windows XP Professional system with both IE and Firefox installed. I have not verified the information on Mac OS X installations. To debug/sniff HTTP requests I used a Windows version of tcpdump and I also used the excellent Charles tool. The purpose of this post is to show what information is being sent to *.adobe.com and/or *.2o7.net. This post does not address the strange looking 192.168.xxx URL issue. ]

It all started with this uneasysilence.com article. Dan claimed that his copy of Adobe InDesign CS3 was spying on him. When starting the application it would make several HTTP requests to a host named '192.168.112.2o7.net' (that's an 'o' in '2o7' and not the digit '0'). The story was picked up quickly by news-sites and blogs around the world. You can see the extent of the spread via this Technorati-search. Dan and others feared that Adobe was secretly transmitting his serial-number to the 2o7.net host whenever he launched the application locally [Correction: Dan himself never stated that he was afraid that the serial number was transferred. However in comments on other sites that picked up the story, people were afraid that this was the case. Dan, sorry for the error.].

What's going on here?

Some CS3 applications include a feature that's called 'Start Page'. When one of those CS3 applications is launched, you'll get an initial window that allows you to access some often used features directly from this 'Start Page'. Below is the start page for Fireworks CS3:

The 'Start Page' is a Flash application. The 'Open a Recent Item', 'Create New', 'Extend' and 'Getting Started' portions are controlled by the application (Fireworks) itself (the loaded Flash file, will call out to the core application and ask it for the list of 'Recent items' for example). The bottom right content (with the 'Fw' logo) is constructed dynamically. This area will show different information depending on whether you have the trial-version or full-version of Fireworks installed (you can see the different versions right here in your browser by selecting one of the following links: trial version or full version). In order to get that Flash content from the web, the application will make the following request to Adobe's servers (I had to wrap some of the long lines in the following request dump and for others below):

That request will return a short 2 KByte SWF (Flash) file. That loaded Flash file will make another request to Adobe's servers and download a 'fw_customize.xml' file with the following content:

and then it will load yet another SWF-file using the following request:

That 2nd loaded SWF file then becomes active and makes a number of other web-requests that define the information that is being displayed on the 'Start Page'.

And that 2nd SWF is also responsible for requests that started the initial outcry on uneasysilence.com.

Adobe (like lots of other companies) uses some Omniture technologies to find out how its web-site and web-services are being used. When browsing the Adobe web-site (and lots and lots of other sites) 'events' are being sent to omniture's servers ('192.168.112.2o7.net' in this case) in order to track your path through the site. Analyzing those aggregated events later on gives Adobe a picture on how users navigated the site, what was interesting to them and what was not. That's standard practice and helps Adobe to change its site to meet its customers needs. There are lots of companies out there offering tracking solutions and even Google provides a framework (Google Analytics) that provides detailed reports on how a web-site is being used.

The SWF executes three HTTP GET requests to a host named '192.168.112.2o7.net'. The first request downloads the crossdomain.xml file. The 'crossdomain.xml' file is part of the security features of Flash (you can read more about it here on Adobe's site). Next it will make two more (almost) identical requests to the same server. Here's the first one of them:

Let's take a look at this request and examine what is being sent to 192.168.112.2o7.net. The beginning portion of the URL '/b/ss/mxcentral/1/F.3-fb/s' is static content, which means each copy of Fireworks CS3 that contacts the 2o7.net server will begin exactly with the same path (the 'mxcentral' portion is actually derived from the information that was downloaded by requesting http://www.adobe.com/startpage/om_acct_nm.txt).

Let's move on to 's1199292440907': some commenters suspected that this is the serial number of the application. Well, I'm afraid that's pretty far-fetched and is NOT true. The string simple consists of the letter 's' and the current time stamp in seconds. To verify that I used perl and asked it to print the current timestamp soon after making the request:

https://bestdload897.weebly.com/color-beat-fyolk-mac-os.html. C:>

Let's move on to the remaining portion that follows the '?'. Given that some automated process on the server '192.168.112.2o7.net' will read the information from that request, I believe developers wanted to make extra sure they can identify the beginning and the end of the submitted information. I have to assume that '[AQB]' and '[AQE]' are beginning- and end-markers (hence the 'B' and 'E') for the information that's submitted. So, the receiving server will extract the portion between those markers for analysis purposes.

The portion saying '&purl=mm&pccr=true&' is again 'constant', it is baked into the 2nd SWF file that was downloaded earlier on. I verified that by dumping the SWF contents using swfdump from the swftools package.

The last portion is 'c2=fw&c3=9.0&c4=win&c5=en&c6=full&c7=&c8=FW& c9=fw_9.0_win_en_full__FW' and as far as I can tell, this just defines the application ('fw'), version number ('9.0'), platform ('win'), language ('en'), trial or full version ('full'), again the application ('FW') and a compound string with all the previous items concatenated ('fw_9.0_win_en_full__FW').

No other information is transferred to Adobe and/or *.2o7.net. Based on my analysis, I don't see any evidence that serial-numbers are being sent to to either *.adobe.com or *.2o7.net.

It's interesting and unfortunate at the same time that this issue surfaced 2 days after Adobe shut down for the holiday break. That did not allow Adobe people to react fast enough before the story rippled through the blogosphere. A lot of FUD is being spread without people actually looking at the facts. Adobe's John Nack tried to stay on the top of the issue and I'm absolutely certain that he will post follow-up information on his blog once he managed to track down the responsible parties at Adobe and/or Omniture. Please subscribe to John Nack's RSS feed if you're interested in the final resolution to this issue.

Tobias – you were the first person I thought of when I read about this. I wondered if you would have a take on the issue that you could share publically. Very interesting. Thanks for doing the legwork and sharing out on it. I wasn't too concerned, I have a properly licensed CS3 and am not fearful of how I use it. However, I am always interested in how the guts of stuff works. I appreciated reading this.

– Chris

Tobias-

For the record I never made any direct or indirect accusation that Adobe was spying on serial numbers. I simply pointed out that Adobe programs were calling out to a service noted for behavioral analytic monitoring. Zombie outbreak slot machine. Also, I pointed out that it was in a way that tried to mask that it was pinging out.

I would ask that you correct the post. If this needs more discussion feel free to email me.

[Dan, I corrected the mistake and added some more information to the first paragraph. I hope this clears things up – thanks!]

My concern is that I had no idea that Adobe had equipped some CS3 applications with a Call Home function that was turned on by default. It should damned well be turned off by default. I want my computer to communicate with the outside world only when I tell it to. And once I have an application installed and activated, I never want it to communicate with the outside world again.

InDesign CS3 on my Mac has a similar screen to the screen from Fireworks. I thought it was handy, but slow. But now, I'm turning it off — and I'm considering turning off my modem before I launch Adobe's applications.

My concern arises from two horrible experiences last summer with Adobe's update checker, which was calling home and downloading updates without my permission. In Acrobat Reader 8 on the Mac, the preferences for the update checker are well hidden, and I think intentionally hidden to discourage people from turning off the function. I won't go into details, and I cheerfully admit to a couple of blunders, but I lost the use of Photoshop CS3 Extended and InDesign CS3 for a couple of weekends while searching the ‘net looking for a fix to the havoc wreaked by the updates downloaded by the updater.

Sometimes there is a fine line between exercising legitimate curiosity and becoming a Peeping Tom. I think Adobe is starting to cross that line and needs to step back.

Tobias, thanks for a well researched and clearly explained piece.

I note that Dan was keen for you to correct your (unintentional) mistake.

I wonder if he has considered that if he himself had hestitated to write his first article until he had put some time and effort into researching the facts, he would hot have caused unnecessary concern and thereby wasted many people's time.

One of the unfortunate aspects of easy access to the internet is the way in which ‘writers' anxiously try to fill their blogs/whatever with little more than idle gossip.

@James: I'm with you, James. I'm equally upset about the situation and I want to make sure that we do everything to regain your and others confidence that we do the Right Thing ™. As mentioned earlier on, I hate to spied upon as much as everybody else. However, in this case I would not call it spying, but providing up-to-date information with negative side-effects.

There are tons of applications out there which phone-home to check whether there's an update to the software you installed. I find this valuable at times and annoying if it is not done right. My Logitech software telling me 'There's an update' without telling me what the update is about, falls into the annoying category. Some other software showing me the release notes for all the versions between my installed version and the current version and whether those updates are security-related or not, falls into the valuable category. https://me-ahead-go-hate-on-hater-bp-slotsinspire-and.peatix.com.

I think there's value in getting up-to-date information from the web via Adobe's start page feature: if we find a severe security error in the application (god forbid) and we wanted to inform you about a related update, the start page could serve as the vehicle to transport this information.

I'm sorry to hear about your troubles with a past Reader update. You have my email address now, should you have problems in the future, please don't hesitate to contact me.

@Mike: Thanks for your kind words!

I've not even been able to install CS3 … and nobody at Adobe seems to know what the problem is. By the way, I've learned that there are a lot of people holding CS3 DVDs they can't install. Adobe is wasting time (? skills/expertise) in collecting information, whilst some of us are left holding $200 useless DVDs

KAa – if you have a DVD of CS3 that you can't install and Adobe's customer support can't help you, why are you holding on to it and not return it for a refund? I know I would send it back if I and tech-support would not be able to install.

I'd be happy to do a screen-sharing session with you to see if we together can manage to get it installed. Please send email to thoellri-at-adobe.com and let's setup a quick online meeting.

And for the records: I had some email exchange with KAa and offered to assist him with his CS3 installation. We were scheduled to 'meet' today (Sunday) to determine what's wrong with the installer. KAa tried it last night again and successfully installed CS3 then. No need to meet.

You are an engineer and Adobe and had to research it ?!?! Don't you know what you are putting into your own products?!?!?

Klause –

1) I have 6500 colleagues all over the world and I don't know what everybody of them is up to.
2) We are split up into multiple divisions and while everybody knows what each division is roughly doing, we certainly don't know intricate details about each of them.
3) My personal work is completely unrelated to the subject at hand.
4) The news broke over the christmas/new years shutdown and people who knew about these areas had better things to do.
5) I wanted to investigate the problem as everybody else outside of the company would see it.

Hope that explains it – let me know if you have more questions.

Tobias

PS: Next time leave a valid email address …

An interesting side issue to the Omniture issue is the appearance of the following in my Firefox status bar when I access the Washington Post online:

'Read omniture.secure.miisolutions.net'

Reading this url clearly slows down my access to this site, sometimes grinding to a complete stop until I reload the page.
I have a registered copy of Adobe Photoshop and Dreamweaver on my computer – could that somehow get involved in my newsreading habits???

Thanks for your comments Wardropper! I've seen similar situations with my browser as well, especially when using something like AdBlock to block certain ad/tracking sites.

There is absolutely no correlation between the installation of Photoshop/Dreamweaver and the weird browsing behavior. Those two applications or parts thereof are not being used (run) at all when you browse through Firefox.

Cheers – Tobias

Thank you for the reassurance, Tobias.
Much appreciated.

Karl Marx anyone?

Writer's Block (tobias Bruch) Mac Os 11

Leave a Reply

Writer's Block (tobias Bruch) Mac Os X

Writers Block (tobias Bruch) Mac Os X