Link Manager Issue

Hi,
Difference in hyper link b/w managed link table & portal end.
Eg: In managed link table there is link "http://www.abc.com" & even dlinkstate is Valid, but when i check in portal end for that link its showing hyper link as "http://www.xyz.com"
Even i have refreshed & recomputed links from Managed links Administration page its not working.
What should i change so that in portal it will show hyper link as "http://www.abc.com".....
Any suggestion
Edited by: 838623 on Sep 1, 2011 11:05 AM

Hi
My 2 cents on this :
The result set is generated by IdocScript function (loadDocLinks) during page generation for LinkManager and this could be the reason why you are seeing the issue mentioned below .
Thanks
Srinath

Similar Messages

Premiere Pro CC and Dynamic Link Manager Issues

I have a previously purchased copy of Adobe Production Premium CS5 installed on my computer as well as a subscription to CC with a few apps installed.
I had a project opened in Premiere Pro CC, off of an external hard drive, and as I was working on it, trying to open it in Speedgrade. I decided to install Audition. However, it prompted me to close the dynamic link manager. Once I did, my project began messing up. As I tried to open the program, my sequences and merged clips disappeared and I don't know what to do. My semester project is due tomorrow. Premiere won't let me open the file (neither cs5 and CC) and the ones that do open have all the clips but no sequence nor merged clips that I previously had. I did notice that the dynamic link is no longer opened in task manager after restarting and restoring the system(with the ejected hard drive). How do I reopen it? And, will it solve the problem?

Thank You, Jim -
Unfortunately that specifically did not work.
Based on another comment sent to me, here is what did.
In PProCC
File > Adobe Dynamic Link > New After Effects Composition
In AECC
From that composition created from PPro, I imported the project (aep) initially created in AECC from another team member. Saved the file.
Back in PProCC
File > Adobe Dynamic Link > Import After Effects Composition
Magic.

Dynamic Link Manager Stopped Working - New CC Apps

As I expectedthe new CC apps seem to have issues when installing on systems where the user profile is used elsewhere other than c: drive.
I know this becuase As soon as I created a new user on the c: drive and logged on and launched the apps they worked fine.
I have an SSD for OS and Applications, and a RAID 0 Array for the User profile on Win7
Is there any known fix for this issue?
( Im not willing to change any part of my hard drive configuration to fix compatibillity with these new CC Apps. )
Dissapointed this was not dealt with. Im sure im not the only user who is under the circumstances.

Hello,
No this had never occured the same way in CS6, Other instances of this have occured with CS6 like not being able to open PSD's in AE. But nothing where the Dynmaic Link manager would stop working.
I realize this issue is caused by my storgae setup becuase as I stated above, when I create a new win7 user and luanched the CC Apps( After Effects, Premirere Pro, Photoshop). they work fine. ( this is becuase the user profile for the user remains on the C: drive)
Where as my main user for my machine differs, in that the user profile exists on my D: drive ( for sake of capacity )
All of the Apps work fine with the new user and user profile on the C: drive, but this is not really an option for me as the SSD im using will not be able to store my large amount of user files ( documents, downloads, appdata, pictures, etc.. )
-Schoolpost

Dynamic Link Manager repeatedly crashes when trying to launch CC applications

Whenever I try to launch most CC applications, the application locks up and becomes unusable for a few minutes. When it locks up varies slightly between applications (Premiere Pro and After Effects locks up when launching, Photoshop locks up shortly after presenting the main window, ect.). I checked the console after noticing this was happening repeatedly, and saw the following message repeated once a second (with an iterating instance number):
10/27/13 3:56:13.725 PM com.apple.launchd.peruser.501[258]: ([0x0-0x5b05b].com.adobe.dynamiclinkmanager.application[537]) Job appears to have crashed: Abort trap: 6
10/27/13 3:56:13.773 PM ReportCrash[514]: Saved crash report for dynamiclinkmanager[537] version 7.0.0 (7.0.0.0) to ~/Library/Logs/DiagnosticReports/dynamiclinkmanager_2013-10-27-155613_lrflew.crash
I uploaded the log file mentioned in the console here: http://pastebin.com/iWBiykSP
I am using a Macbook Pro Retina, 15-Inch, Late 2013 running Mac OS X Mavericks (10.9).
Is anybody else having similar issues? Is there an update I don't know about for the Dynamic Link Manager that fixes this issue? Should I submit a bug report for this?

I came across this post while searching for a sollution to my problem. I came a cross a lot of posts like this and they all seem to have a common theme with Adobe CC paid beta. Granted I wrote a prolific rant I cannot seem to spell check, go to the last paragraph [the short version] and it will explain how to solve this. grrrr....
I noticed that CC keeps forgeting who I am, asking me to log in, updating, changing prefernce, not remembering my cloud settings, it has been awfull. I like the new features, but I feel like Adobe is restting all my macros and pressets every other month.
That is what led me to my conclusion of what is going wrong. Every time I wanted to put After Effects dynamic link Premiere would hang. I had to force close it via Windows 8. I first suspecting Windows 8 to be the problem, I turned off my UAC, I turned off my start screen, ran as admin, even tested it with the admin account. That worked. I tested it with another account., that worked. So everything worked but the account I needed to work. DARN YOU MICROSOFT!!! **fist shaking**
I then thought, "crap, what if they deleted this feature?" "No, they couldn't, this feature is the primary reason why I bought the softwear instead of trying to rip it off (poor college student first job card) Still I found the money to buy the software for this feature, now it is gone???!!!
That is when it occured to me, this was exactly like the crack versions I used of 5???
Hmmm ..
I turned off all my adobe services, rebooted, cleared cache, everything, what the hell.
Then it came to me, what if it thinks i am not who I say I am. After ...
[Short Version] Log out of Creative Cloud then back in.] If you have any issues that seem random make this your first step. Adobe as botch this granted, I believe in them, I think they should extend the $19.99 discount fo another year because of it and the fact we would still be willing to pay that. seriously Adobe, get the poop together or start compinsating your customers.

The Ultimate Guide to Resolving Profile and Device Manager Issues

The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
Hello,
I have been plagued with Profile Manager and Device Manager issues since day one.
I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
(Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile and Device Manager may need a Code Signing Certificate.
The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
I shall outline a sensible strategy:
1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
2. Start the server fom the clone and shut down ALL services.
3. It may be sensible to set up a root user access.
4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
Erase database:
sudo /usr/share/devicemgr/backend/wipeDB.sh
7. Note your Directory (diradmin) password for later if you want to re-use it.
8. Open Open Server Admin and demote OD Master to Standalone Directory.
9. In Terminal delete the old Certificate Authority
sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
This step is crucial because else re-building you OD Master will fail.
9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
11. Go back to Workgroup Manager and re-import users and groups.
NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
If the home directory has not been defined you cannot login from a network account.
13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
sudo serveradmin stop devicemgr
sudo serveradmin start postgres
sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
sudo serveradmin start devicemgr
14. You can now switch back on your services, including Profile Manager.
In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
16. Check that Apple Push Notifications are set.(you easily check if they are working later)
17. You may want to re-boot OS Server from the clone now.
18. After re-boot open Server App and check that your server is running well.
19. Delete all profiles in System Preferences -> Profiles.
19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name should read "Trust Profile for...) and underneath in green font "Verified".
21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
Now enjoy Profile and Device Manager !
Regards,
Twistan

HI
1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
also make sure that u have the message processing role
Hope it clarifies ur doubt and resolve ur prob
Regards
Prakhar

Power Mac G5 DP1.8GHz - Bad Logic Board or Power Management Issue?

I have a Power Mac G5 DP1.8GHz/1.5GB/80GB which I bought non-working. It has not yet been disassembled or examined by a certified tech. This is it's issue (which replicates): the computer powers on. It makes a single warning tone, then the LED flashed at least 15 times (too fast to count). Then the posting chord is heard. Hard drive spins up. Then nothing (no video). Won’t boot from any disk. I have changed the RAM and tested the RAM banks with known-to-be-good RAM from another DP1.8GHz G5. The warning tone stopped once or twice after this switch, but then it didn’t chime. I changed the PRAM battery, but not with as new one. However, after installing the used one and then resetting the PMU, it displayed video briefly for the first time. While installed in the other 1.8GHz G5, the hard drive was formatted, given a clean install of OS X 10.4.11, and then moved into this computer where is never mounts. The computer is not accessible through TDM.
Do I have a bad logic board? Bad CPUs? A power managment issue? A RAM issue?

Through my own trial and error troubleshooting, I have found the CPUs to be in good working order and the logic board passes the Apple Service Diagnostic every time. Despite the installation of numerous pairs of modules that worked in another DP1.8GHz, the computer has a RAM issue-it gives the "no good RAM" tone most of the time when it powers up (after a PMU reset it does not). Also the computer boots from disk or into Open Firmware but the disk utility can't see either hard drive so I may have a bad SATA controller.

Color Management issues with Illustrator

Can someone help me figure out the color management issues I'm getting when printing on an Epson 3880 from Illustrator?
The image comes out severely red as evident on the face. I'm not getting the same problem when printing from Photoshop, even though I set same paper profile in printing dialog box.
I attached two printed picture (one from Photoshop CC, and one from Illustrator CC) that I took with my iphone so that you can see the printed result. Even when I try to simulate same thing using illustrator soft proofing process, the soft proof does not show me anything close to how it gets printed out. And I tried all device simulations to see if any would match it. Im using CMYK SWOP v2 for Color space in both programs.

Dougfly,
Only an hour wasted? Lucky you. Color is an incredibly complex subject. First, forget matching anything to the small LCD on the back of your camera. That's there as a basic guide and is affected by the internal jpg algorithm of your camera.
2nd, you're not really takeing a color photo with your digital camera, but three separate B&W images in a mosaic pattern, exposed thru separate red, green and blue filters. Actual color doesn't happen until that matrix is demosaiced in either your raw converter, or the in-camera processor (which relies heavily on camera settings, saturation, contrast, mode, etc.)
Having said the above, you can still get very good, predictable results in your workflow. I have a few color management articles on my website that you might find very helpful. Check out the Introduction to Color Management and Monitor and Printer Profiling. In my opinion, a monitor calibration device is the minimum entry fee if you want decent color.
http://www.dinagraphics.com/color_management.php
Lou

DYnamic link manager error

i have
an error which pops up everytime i open ae cs5. its part of production premium student windows 64-bit. it has worked fi ne but i started to get errors, ive attached a pic
all of the other programs still work

This can occur if After Effects is failing to communicate with the Dynamic Link manager because the communication is blocked---usually by overly aggressive firewall settings.
See this document:
http://kb2.adobe.com/cps/857/cpsid_85711.html

Charm - how manage issues after go live phase

Hi all,
ny customer use Charm Implementation project for managing roll-outs of new countries in his SAP ECC Landscape.
Now Test Phase is going to end and he asks himself: "how can I manage issues after go live in Charm?"
If I have to create additional TRs for bug fixing in the weeks after go-live can I manager them in Charm?
I know there is the function for create TR direct in Talsk List, is this the correct way?
In other words, do I manage issues after go-live out of Change Documents using Task list?
As you know, Is there any best practices from SAP od from elsewhere?
Thanks o lot
Giovanni Lippolis

Hi Miguel, Bob and Jansi,
thanks for you contributions.But I realize I didn't explained myself completly.
My situation is similar to what Bob described,
I'm not in an ideal world (do you remember Clint Eastwood and Kevin Costner), and I think neither you.
But, in my case there are not open TR to be recovered in project, but I suppose I'll have to open some TR (I hope a few) for fixing bug that will happen in production in the days post roll-out.
So I wouldn't like to manage there fix in a maintenance project, because the reason of these bugs is in TR imported in roll-out.
What I would like to do is to regress project to the Test phase (I don't need new CR and NC!) and open few Test Messages for fixing bugs.
I'suppost It should be possilble.In your opinion?
Ideas?
Thnks a lot.
Giovanni
So what

Colour Management Issue with PS CS3 and Leopard 10.5.2

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

>It was working perfectly in Tiger with the monitor profile.
You were lucky.
the monitor profile is so Photoshop can display your images correctly.
the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
you need to read up on color management:
http://www.gballard.net/psd.html
http://digitaldog.net/

Colour Management issue With Leopard and PS CS3

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

You need to use the correct printer profile for the paper you're using. If the printer didn't come with any pre-built profiles, check Canon's web site to see if they have any profiles available for your printer that you can download.
Printer profiles are very specific. You can't take take a profile for glossy Epson paper and expect it to work very well for Canon glossy paper.

Colour Management Issues with Leopard and Photoshop CS3

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

I'm having exactly the same problem, only my printer is a Canon Pixma iX4000. The colour is all bleached out, it looks exactly like when you've accidentally printed an RGB file on a CMYK printer, and at first I thought that was what I had done, but it isn't. This is very frustrating, I've spent all day going through the manuals, recalibrating etc, but no luck. This is a brand new Mac Pro and printer, but if its not going to print what I see on screen it's just expensive junk.
I wasn't sure if the problem was Leopard or the printer or CS3...

How do I close Adobe Dynamic Link Manager & Adobe Media Core to install After Effects?

when i try and install the after effects cc it tells me to close the following programmes: after effects, adobe dynamic link manager and adobe media core.
How do i close the last 2??

You can also restart your computer to make sure that everything has been quite that needs to be. Restarting before and after installing major software is a good idea in general, anyway.

WARNING: Canon Pro Printers and CS4 – Serious Colour Management Issue

Over the last four days (and over fifty prints) I have undertaken extensive and meticulous tests to identify the cause of a problem; namely that targets for profiling a new printer (a Canon Pro9000), printed with ‘no colour management’, were printing far too dark and with what appeared to be a colour cast.
I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3.
Furthermore, colour managed prints (using the same accurate profile made in CS2), printed in CS2 and CS4, show subtle differences. This may not be an issue except in the most critical applications.
It is likely that the problem will not be confined to the two Canon printers above since many other Canon printers share the same driver architecture.
Reading posts and discussions on other websites would seem to indicate that this problem is also manifest with some Epson printers and may also effect Mac OSX 10.5.
I have to conclude, therefore, that Photoshop CS4 cannot be replied upon to print targets of sufficient accuracy to produce reliable profiles for a colour managed workflow.
The fact that this is only just being reported can be attributed to four factors:
That many CS4 users are continuing to use profiles made under older versions of Photoshop and have yet to make new profiles using CS4.
Some users may not immediately notice a problem, or may ascribe it to other causes.
Some users may take the line of least resistance and use a previous version of Photoshop to work around the problem.
Some users are still using the older versions of Photoshop not effected.
Eric Chan (of Adobe) has stated on another website that CS4 implemented some new APIs for printing and that this has given rise to some "minor glitches". If Eric Chan is correct, and Adobe changed the APIs in Photoshop CS4, this begs question of whether Adobe sufficiently tested CS4 before release ? If Adobe did not test their software, and therefore failed to identify this critical problem, this would suggest negligence on Adobe’s part. If Adobe identified the problem but then did not inform users that a potentially serious colour management issue existed this would suggest wilful or gross negligence.
It is not good enough to say that Adobe simply followed the ‘conventional’ path and ‘followed the rules’ regarding API implementation. The experience of end users does not correspond to a “minor glitch” and, in my case, has been extremely costly in terms of time (over five days in all), lost revenues, and materials. Furthermore, why should Adobe's customers be forced to use their valuable time diagnosing problems clearly of Adobe's creation – and actually admitted.
In UK law providers of goods and services (and this includes software) have to supply them as “fit for purpose”. Clearly, in terms of colour management, CS4 is not fit for purpose. Neither can Adobe hide behind its labyrinthine licensing terms since any exclusions would be ruled unlawful under the UK’s ‘Unfair Contract Terms’ Act.
My strong and unequivocal recommendation is that representatives from Adobe, Apple, and the printer manufacturers meet together – with the utmost urgency – and provide a rapid and complete solution. It is simply not good enough to pass this ‘over the wall’ saying “it’s not our problem”. It is. Adobe's, Apple's, and the printer manufacturers'. Please solve it. And quickly.
Identify the problem clearly, make it and the solution/s public; and publicise it widely and thoroughly.

Dear DYP.
Thank you for your concern.
"What fixes have you tried?"
If I may quote from my post above:
"I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3"
These tests took place over three weeks and involved over five days of work and the replacement of the printer on Canon's recommendation (although the printer is clearly not at fault).
Please note that I am using Mac OSX 10.4.11.
"What driver versions are you using?"
Pixma iP4500 6.9.3 (also 6.9.1, 6.9.2 and the driver supplied on the CD).
Pro 9000 4.8.7 (also 4.7.3, 4.8.4 and the driver supplied on the CD).
"Yes it is frustrating but in a lot of cases it is fixable as I and others have clear reported, on this and the LR forums."
I have not found any fix on any website referring to Canon printers, despite exhaustive searches (this includes Canon's European and US websites which are mute on the issue).
The ReadMe file supplied with the installation disc of CS4 refers to problems with "some Canon printers" when printing with the 'Printer Manages Color' but does not identify using 'No Color Management' nor Epson printers as having issues.
I hope this post answers your questions.
Clearly all users of CS4 need to be warned of this problem which is likely to effect other printers. I believe that I am assisting others by issuing this warning. It is done, not to cause mischief, but in the spirit of a public service. CS4 users can then treat their printing results from CS4 with caution, and then conduct their own tests. I have presented a workaround which is to use a prior version of CS4.

MEDIA MANAGER ISSUES?? PLEASE READ BEFORE POSTING

We have created several Media Manager specific threads for your issues that are "stickied" at the top of this board. These are :
Media Manager Installation Issues
Media Manager Design Issues
Media Manager Audio Playback Issues
Media Manager Video Playback Issues
Media Manager General (Other) Issues
Please post your Media Manager issues in the correct corresponding thread so that our FSC employees can identify and begin to resolve some of the problems being experienced by our Media Manager customers.
Thank You!!
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer that solved your issue as the accepted solution.

I can understand your point of view and I respect it in regards to Small Basic being a learning language. None the less, let me make a suggestion that would be more ageeable, I think, to different kinds of people. Why not make different versions
of this new language: version 1 for beginners that I heard would be out by the end of this year,
version 2 for intermediates and version 3 for more advanced programmers. All this would culminate to the Visual Basic language. These 3 versions would smoothe out the gap between SB and Visual Basic. Your new programmers would
evolve at the same time your versions would come out and Microsoft would have a long term policy of loyal programmers.

Link Manager Issue

Similar Messages

Maybe you are looking for