ProTool Digi 003 new driver issues with Logic
I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.
I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.
Similar Messages
-
Has anyone else been having hard drive issues with 13" MacBook Pro barely a year old?
Has anyone else been having hard drive issues with 13" MacBook Pro barely a year old?
Yes, BUT...
... there are many problems that are really easy to eliminate by replacing the Hard drive, including ones that have nothing to do with actual Drive Hardware failure. These include corrupted install of Mac OS X, its EFI partition, clobbered partition tables, or the appearance of Bad Blocks in a critical area.
Any of these problems can sometimes be eliminated by re-initializing the entire drive and writing Zeroes, and re-installing from scratch. The trouble is, this process takes hours to complete, and is not guaranteed to be successful -- you may still need a new drive after all that effort.
I learned from my Plumber that consumers have no appetite for solutions that might work, and detest return visits for any related problems whatsoever. You or your friend may have had your drive replaced, not because it actually failed, but because the situation was troublesome, and the provider thought you would not tolerate anything less than a crisp, complete fix on the first attempt. And based on the cost of technician time, it may have even been cheaper that way. -
Audio driver issue with my HP Compaq DC7800 Convertibl​e Minitower
Hello,
I am having an Audio driver issue with my HP Compaq DC7800 Convertible Minitower desktop PC.
A few days ago I have formatted my desktop PC and installed a new Windows XP Service pack 3. As I needed driver for my device I have managed to find all drivers except the one for my audio device. As I saw I have integrated audio on my motherboard, but drivers that I have found on a support site of HP (drivers download) none of them work and there are too many (I have also needed to download drivers for other devices form intel site but this is another issue). So, now I was hoping that someone can help me to find (finally) and install audio device so I can finish with installation process. I would be veeeeeerrrry thankful for that Thanks in advance.
This question was solved.
View Solution.It does not matter . I have found the driver that I needed: ADI High-Definition (HD) Audio Driver - Sound Max
thx anyway -
Performance issues with Logic Pro 9
Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
ThanxHi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G -
I am having major issues with Logic 8 and want to reinstall.
I am having a lot of issues with Logic 8 and want to do a re-install. What is the procedure and what do I need to uninstall first. I need to be careful, because I don't want to affect my Logic 7.
Any suggestions?What problems?
The first thing to do is trash the preferences. As far as affecting Logic 7, once you install 8, 7 is "forgotten" about. I'm assuming your L8 is a real version, not a "borrowed from the interweb" one. -
Hi. I have set up the trial versions of Photoshop CC 2014 and Lightroom 5.6 (ie the Photography plan) on a desktop that I have added a new drive to with Windows 7. Everything works fine BUT it is an old computer and I'm thinking that it may pack up unexpectedly. These things happen. I want to sign up for the Photography plan but I also have a Windows Vista laptop, and that is old too so I may want to put the apps on a new desktop and a new laptop, having already installed on my desktop. That makes three activations. Am I allowed to do this? Cheers. Paul
You cannot have three activations. It's simply not technically possible. If and when the time comes, you simply deactivate/ sign out on one of the old systems and install on the new one. If the system goes belly up, you contact support to reset your account. No need to make it more complicated than that and overthink it.
Mylenium -
on windows 8 and itunes I have importing problems the DVD is only reading the music cd from 1.5x to 4.0x for 95% of the time, it does hit speeds of 30x for the other 5% of the time. Is it a driver issue with the DVD or is it a windows 8 issue?
No. You have no alternative but to plug it into a computer running iTunes and restore it.
-
Metronome click issue with Logic 8
Hello.
I'm having a strange issue with Logic 8 where the first click after hitting play or record is lower in volume than the rest of the clicks and sometimes isn't there at all - every subsequent click sounds fine. I have checked the metronome preferences and made sure the bar click is the same velocity as the beat click. I've double checked my entire configuration to see if there is a problem somewhere and everything seems to be right. I figured this might be just a bug but I wanted to post this to make sure.
Any ideas on how to fix this?
Here is the configuration I'm working with which has all the latest drivers and updates:
Mac Pro 3.2 GHz 8-core Intel
Mac OS 10.5.2
14 GB RAM
Logic Pro 8
Apogee Ensemble
Trilogy with the Intel wrapper (this might be pertinent)You need to add more RAM.
-
Focusrite Scarlett 2i2 clapping and crackling issues with Logic Pro x new iMac 27"
Hi, I have just purchased a brand new iMac and downloaded Logic Pro x, I also purchased the Focusrite Scarlett 2i2 interface. I have downloaded the drivers from the focusrite website and everything is set up, when I plug in guitar or mic I get really bad clapping and crackling to the point where the sound cuts out altogether. I have changed buffer size and sample rates and everything else I can think of but nothing seems to fix the problem. I also deleted the 2i2 drivers and logic and reinstalled them both but still have the same issue, when I record using the iMac built in mic everything is fine so it's deffinately something to do with the interface. I am waiting to hear back from Focusrite tech help. Does anyone else have this problem? Any help would be appreciated.
I'm having a similar issue which might indicate that the problem is not your interface.
Yesterday I migrated all my stuff from my 2009 iMac to a brand new iMac 27", and when I did a quick test to play back some old projects in Logic there was loads of annoying clicks and pops. My interface is a Roland Octa-Capture.
I also noticed some weird CPU spikes from time to time, which I never had on my older, much less powerful iMac... -
New NVIDIA Driver issue with Premiere pro
Laptop
Windows 7 pro x64
Intel Core i7 2.7ghz
16 gig ram
NVIDIA GTX675MX driver version 314.07 2013.2.18
Hello, I had to update the driver due to premiere stating I had an outdated driver. After installation everything seemed fine however today when I opened premiere my source and preview windows showed black, no video. My edits and source files were all still there. Sound from my clips played but no video. I have Mercury playback set to hardware. When I switch it to software the video images return. Has anyone else had an issue with this driver in Premiere pro and did you find a solution? I did a search and this seems to be an issue with drivers. Hope they fix it in the next update. Thanks.Thank you everyone, I just figured it out. For some reason in my NVIDIA Control panel-Manage 3d settings-Global settings Preferred Graphics processor drop down was set to Auto-Select. I switched it to the NVIDIA card and everything seems back to normal. Phew!
Harm, I used your system configuration guide to set up my system. That really helped take the confusion out of proper system configuration. Thank you for writing that. -
Anyone using a NEW intell iMac with Logic?
I've got many great responses on both sides to my question regarding my quest to determine which machine to use with Logic -- new Mac Pro (the ultimate) or new iMac (likely cover my bases for a long while and save major cash now). One point raised against iMac was fan noise smack dab in the middle of the listening field with the older iMacs. So a sub question to my original is this:
Are there any NEW intell iMac users out there who are using Logic? Is fan noise a problem? Generally, how do you like the iMac's feasibility as a music workstation with Logic? How many tracks/effects are you running and how is it working for you?Before those concerns are completely alleviated, go over to the iMac hardware forum and do a search for firewire issues. Like actual physical problems with the jacks on the 20" iMac and having drives just completely "disappear".
the reason you will find issues including firewire ones on the imac forum is because it is a forum for people with issues. it may or may not be the case that there is a subsantial issue with FW on the intel imacs, but obviously people who are having issues are going to pop up there making it seem like everyone is having an issue.
for certain types of music production, an imac would be completely unsuitable. but for others it will be ideal.
there drawback of having 800 and 400 FW bus shared is that if you have a 400 device it will slow down 800 devices to 400. that means it would be ideal for impiro to have either both FW drive and interface as 800's or not go to any further expense of getting an 800 hard drive to use for audio since he would not beneift from the speed.
not a great big deal IMO.
iMac DOES lack expandibility, but it doesn't lack horses. actually i would say (and have said) that impiro would do better with an older tower to allow for expandability because he doesn't need that many horses to do what he needs to do. and i certainly feel that it is unnecessary to spend money on a computer that would be better spent on other things relating to the move to computer based music mixing.
never-the-less, the kind of live musician-audio-based music impiro is going to be making is childs play for modern computers. he will be able to run loads of tracks and plug-ins before a new imac will even break a sweat. even with an interface and a FW drive on 1 bus running at 400. he just won't be able to run loads and loads.
and man....even if he decides to get more heavily into it and start buying third party cards and this that and the next thing he can look at the next computer being a tower. personally, i am changing my computer every 3 years or less - it'll take him at least that long to find the ceiling on a new imac. -
Hard drive issues with my macbook pro
I have replaced my hard drive twice in 2 months. The beach ball continues to spin and I am concerned that this new hard drive will fail like the others! I am not getting anywhere with Apple support. They continue to tell me it is just the hard drive. Can't believe it anymore. I am ******!!
Any help with the above would be greatly appreciated?
ThanksI want to know if someone else has had this issue?
Why would that matter? If you had it replaced twice in two months, it's highly unusual. If it happens a third time, Apple will probably take a commensurately unusual interest in your Mac. Perhaps they overlooked an underlying cause, such as a damaged cable connecting the drive to the logic board.
Whether it fails again tomorrow or ten years from now, if you value the information it contains, you need a backup strategy. All you need to buy is an external hard disk. They're very inexpensive.
The slow Mail performance you describe may have been a symptom of the disk's impending failure. -
Latency Issue with Logic 8 and Reason
Hello evryone,
I am using Logic 8 with Reason 3.0 and have a Digi 002 as my audio interface. I have set up an aux track in Logic with inputs being RW:L/R and outputs 1&2. When I open Reason after I have opened Logic and go to play an instrument in reason there is massive latency. I've tried messing with the plu-in delay compensation in Logic's prefs. and it didn't have any effect. When I use this set-up with Protools it works beautifully and I don't have any issues like this. Does anyone have any answers or suggestions. Thanks, E.MHi and thanks for the response. I forgot to mention in my previous post that I have indeed changed the buffer size time and time again and it has not helped. What is going on forum? This seems to be a common problem I am having with Logic. Why is it so easy to have a set up like this in PT but not in Logic. Ever since I bought this program I have had nothing but stupid little problems like this. Apple, what's going on with the design of this program. How can you have so many cool features and yet not have the most basic things work properly? I am at my wits end as I am wasting time with this product and am about to throw it out the window, trash it to other musicians/composers and go back to PT. Really, where is the Apple support team on this?
-
Having a strange issue with Logic, don't know what to do.
Aright, so I'm having a really weird problem with Logic. It all started about 20 minutes ago. I'm working with 12 midi tracks; all logic instruments. Every first Snare midi note plays extra soft and then every midi note after that plays at its correct velocity. Don't know why. I tried deleting the note and pasting a new and that didn't work so I saved and quit. I then took a look in my console and this is what came up:
11/7/11 12:21:53 AM
bootlog[43]
BOOT_TIME: 1320650503 0
11/7/11 12:22:12 AM
loginwindow[31]
USER_PROCESS: 31 console
11/7/11 12:29:13 AM
loginwindow[31]
DEAD_PROCESS: 31 console
11/7/11 12:29:15 AM
loginwindow[202]
USER_PROCESS: 202 console
11/7/11 1:32:51 AM
loginwindow[202]
DEAD_PROCESS: 202 console
11/7/11 1:32:52 AM
shutdown[2714]
SHUTDOWN_TIME: 1320654772 505951
11/7/11 1:33:14 AM
bootlog[46]
BOOT_TIME: 1320654783 0
11/7/11 1:33:17 AM
loginwindow[35]
USER_PROCESS: 35 console
11/7/11 8:18:59 AM
loginwindow[35]
DEAD_PROCESS: 35 console
11/7/11 8:19:06 AM
loginwindow[349]
USER_PROCESS: 349 console
11/7/11 8:28:02 AM
reboot[1018]
BOOT_TIME: 1320679682 95944
11/7/11 8:28:45 AM
bootlog[51]
BOOT_TIME: 1320679715 0
11/7/11 9:15:22 AM
loginwindow[40]
USER_PROCESS: 40 console
11/7/11 9:56:40 AM
loginwindow[40]
DEAD_PROCESS: 40 console
11/7/11 9:56:48 AM
loginwindow[242]
USER_PROCESS: 242 console
11/7/11 9:59:01 AM
reboot[835]
BOOT_TIME: 1320685141 69936
11/7/11 9:59:29 AM
bootlog[48]
BOOT_TIME: 1320685155 0
11/7/11 10:08:33 AM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 1:20:53 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 1:20:57 PM
shutdown[7541]
SHUTDOWN_TIME: 1320697257 332087
11/7/11 1:21:22 PM
bootlog[50]
BOOT_TIME: 1320697269 0
11/7/11 1:21:50 PM
loginwindow[39]
USER_PROCESS: 39 console
11/7/11 2:30:13 PM
loginwindow[39]
DEAD_PROCESS: 39 console
11/7/11 2:30:31 PM
shutdown[1377]
SHUTDOWN_TIME: 1320701431 300114
11/7/11 2:31:00 PM
bootlog[48]
BOOT_TIME: 1320701445 0
11/7/11 2:58:14 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 3:02:19 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 3:02:20 PM
shutdown[206]
SHUTDOWN_TIME: 1320703340 498493
11/7/11 3:02:42 PM
bootlog[48]
BOOT_TIME: 1320703352 0
11/7/11 4:33:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 5:57:24 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 5:57:24 PM
shutdown[404]
SHUTDOWN_TIME: 1320713844 888171
11/7/11 5:57:58 PM
bootlog[48]
BOOT_TIME: 1320713868 0
11/7/11 5:58:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 6:01:48 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 6:01:48 PM
shutdown[169]
SHUTDOWN_TIME: 1320714108 381468
11/7/11 11:48:22 PM
bootlog[48]
BOOT_TIME: 1320734891 0
11/7/11 11:48:45 PM
loginwindow[37]
USER_PROCESS: 37 console
11/8/11 4:19:03 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/8/11 4:19:03 AM
shutdown[641]
SHUTDOWN_TIME: 1320751143 318155
11/8/11 8:36:13 AM
bootlog[45]
BOOT_TIME: 1320766559 0
11/8/11 8:36:30 AM
loginwindow[34]
USER_PROCESS: 34 console
11/8/11 8:10:50 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/8/11 8:10:50 PM
shutdown[183]
SHUTDOWN_TIME: 1320808250 610564
11/8/11 8:12:08 PM
bootlog[48]
BOOT_TIME: 1320808315 0
11/8/11 8:12:22 PM
loginwindow[37]
USER_PROCESS: 37 console
11/8/11 9:44:19 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/8/11 9:44:20 PM
shutdown[385]
SHUTDOWN_TIME: 1320813860 87755
11/9/11 10:30:35 AM
bootlog[48]
BOOT_TIME: 1320859824 0
11/9/11 10:31:05 AM
loginwindow[37]
USER_PROCESS: 37 console
11/9/11 1:01:13 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/9/11 1:01:13 PM
shutdown[292]
SHUTDOWN_TIME: 1320868873 995966
11/9/11 1:02:02 PM
bootlog[48]
BOOT_TIME: 1320868909 0
11/9/11 1:02:15 PM
loginwindow[37]
USER_PROCESS: 37 console
11/9/11 3:13:01 PM
login[5975]
USER_PROCESS: 5975 ttys000
11/9/11 3:13:01 PM
login[5975]
DEAD_PROCESS: 5975 ttys000
11/10/11 5:32:55 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/10/11 5:32:55 AM
shutdown[6997]
SHUTDOWN_TIME: 1320928375 628779
11/10/11 8:41:31 PM
bootlog[45]
BOOT_TIME: 1320982876 0
11/10/11 8:42:42 PM
loginwindow[34]
USER_PROCESS: 34 console
11/10/11 9:29:47 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/10/11 9:29:48 PM
loginwindow[180]
USER_PROCESS: 180 console
11/10/11 9:30:20 PM
reboot[283]
BOOT_TIME: 1320985820 923753
11/10/11 9:31:10 PM
bootlog[45]
BOOT_TIME: 1320985858 0
11/10/11 9:31:43 PM
shutdown[98]
SHUTDOWN_TIME: 1320985903 450229
11/11/11 12:05:40 PM
bootlog[45]
BOOT_TIME: 1321038331 0
11/11/11 12:06:10 PM
loginwindow[34]
USER_PROCESS: 34 console
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 6:01:11 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/12/11 6:01:11 PM
shutdown[459]
SHUTDOWN_TIME: 1321146071 420746
11/12/11 9:39:44 PM
bootlog[45]
BOOT_TIME: 1321159171 0
11/12/11 9:40:04 PM
loginwindow[34]
USER_PROCESS: 34 console
11/12/11 10:59:25 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/12/11 10:59:25 PM
shutdown[190]
SHUTDOWN_TIME: 1321163965 560483
11/13/11 12:15:33 AM
bootlog[45]
BOOT_TIME: 1321168520 0
11/13/11 12:15:55 AM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 2:02:40 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 2:02:40 AM
shutdown[324]
SHUTDOWN_TIME: 1321174960 535970
11/13/11 10:54:04 AM
bootlog[45]
BOOT_TIME: 1321206832 0
11/13/11 10:54:19 AM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 11:02:13 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 11:02:13 AM
shutdown[154]
SHUTDOWN_TIME: 1321207333 741020
11/13/11 4:11:30 PM
bootlog[45]
BOOT_TIME: 1321225878 0
11/13/11 4:12:00 PM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 4:14:40 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 4:14:41 PM
shutdown[152]
SHUTDOWN_TIME: 1321226081 279428
11/13/11 4:15:01 PM
bootlog[45]
BOOT_TIME: 1321226090 0
11/13/11 4:15:18 PM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 4:54:48 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 4:54:48 PM
shutdown[178]
SHUTDOWN_TIME: 1321228488 443594
11/13/11 10:11:05 PM
bootlog[45]
BOOT_TIME: 1321247453 0
11/13/11 10:11:39 PM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 2:34:46 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 2:34:47 AM
shutdown[283]
SHUTDOWN_TIME: 1321263287 223296
11/14/11 11:02:03 AM
bootlog[45]
BOOT_TIME: 1321293712 0
11/14/11 11:03:19 AM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 5:14:25 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 5:14:25 PM
shutdown[345]
SHUTDOWN_TIME: 1321316065 545760
11/14/11 5:16:14 PM
bootlog[45]
BOOT_TIME: 1321316165 0
11/14/11 5:16:33 PM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 5:44:15 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 5:44:16 PM
shutdown[187]
SHUTDOWN_TIME: 1321317856 83312
11/15/11 12:48:10 AM
bootlog[45]
BOOT_TIME: 1321343279 0
11/15/11 12:48:38 AM
loginwindow[34]
USER_PROCESS: 34 console
11/15/11 3:26:19 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/15/11 3:26:19 AM
shutdown[365]
SHUTDOWN_TIME: 1321352779 718218
11/15/11 11:32:51 AM
bootlog[45]
BOOT_TIME: 1321381958 0
11/15/11 11:33:07 AM
loginwindow[34]
USER_PROCESS: 34 console
11/15/11 11:50:40 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/15/11 11:50:40 AM
shutdown[173]
SHUTDOWN_TIME: 1321383040 949601
11/15/11 3:13:03 PM
bootlog[48]
BOOT_TIME: 1321395171 0
11/15/11 3:13:16 PM
loginwindow[37]
USER_PROCESS: 37 console
11/15/11 3:28:56 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/15/11 3:28:56 PM
shutdown[169]
SHUTDOWN_TIME: 1321396136 717878
11/15/11 3:31:06 PM
bootlog[48]
BOOT_TIME: 1321396254 0
11/15/11 3:31:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/16/11 2:38:00 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/16/11 2:38:00 AM
shutdown[1961]
SHUTDOWN_TIME: 1321436280 560702
11/16/11 11:30:09 AM
bootlog[47]
BOOT_TIME: 1321468198 0
11/16/11 11:30:48 AM
loginwindow[36]
USER_PROCESS: 36 console
11/16/11 4:34:51 PM
loginwindow[36]
DEAD_PROCESS: 36 console
11/16/11 4:34:51 PM
shutdown[341]
SHUTDOWN_TIME: 1321486491 583341
11/16/11 4:36:11 PM
bootlog[48]
BOOT_TIME: 1321486559 0
11/16/11 4:36:34 PM
loginwindow[37]
USER_PROCESS: 37 console
11/16/11 9:59:04 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/16/11 9:59:05 PM
shutdown[371]
SHUTDOWN_TIME: 1321505945 161871
11/17/11 12:20:08 AM
bootlog[48]
BOOT_TIME: 1321514397 0
11/17/11 12:20:32 AM
shutdown[106]
SHUTDOWN_TIME: 1321514432 588785
11/17/11 12:21:30 AM
bootlog[48]
BOOT_TIME: 1321514481 0
11/17/11 12:21:45 AM
loginwindow[37]
USER_PROCESS: 37 console
11/17/11 12:39:52 AM
login[174]
USER_PROCESS: 174 ttys000
11/17/11 12:40:12 AM
login[174]
DEAD_PROCESS: 174 ttys000
11/17/11 12:40:15 AM
login[180]
USER_PROCESS: 180 ttys000
11/17/11 12:54:34 AM
login[180]
DEAD_PROCESS: 180 ttys000
11/17/11 2:28:30 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/17/11 2:28:30 AM
shutdown[331]
SHUTDOWN_TIME: 1321522110 593580
11/17/11 4:37:08 PM
bootlog[48]
BOOT_TIME: 1321573005 0
11/17/11 4:38:49 PM
loginwindow[37]
USER_PROCESS: 37 console
11/17/11 7:39:32 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/17/11 7:39:32 PM
shutdown[386]
SHUTDOWN_TIME: 1321583972 773529
11/18/11 1:41:17 AM
bootlog[48]
BOOT_TIME: 1321605668 0
11/18/11 1:41:40 AM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 3:48:55 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 3:48:55 AM
shutdown[355]
SHUTDOWN_TIME: 1321613335 819965
11/18/11 10:23:51 AM
bootlog[48]
BOOT_TIME: 1321637021 0
11/18/11 10:24:13 AM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 2:15:52 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 2:15:59 PM
shutdown[770]
SHUTDOWN_TIME: 1321650959 323280
11/18/11 2:16:33 PM
bootlog[48]
BOOT_TIME: 1321650971 0
11/18/11 2:16:52 PM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 6:30:25 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 6:30:27 PM
shutdown[1470]
SHUTDOWN_TIME: 1321666227 362936
11/18/11 6:31:47 PM
bootlog[38]
BOOT_TIME: 1321666248 0
11/18/11 6:32:34 PM
loginwindow[26]
USER_PROCESS: 26 console
11/18/11 8:24:46 PM
loginwindow[26]
DEAD_PROCESS: 26 console
11/18/11 8:24:56 PM
shutdown[205]
SHUTDOWN_TIME: 1321673096 424661
11/18/11 8:25:23 PM
bootlog[40]
BOOT_TIME: 1321673108 0
11/18/11 8:26:03 PM
loginwindow[26]
USER_PROCESS: 26 console
11/18/11 8:37:36 PM
loginwindow[26]
DEAD_PROCESS: 26 console
11/18/11 8:37:37 PM
loginwindow[210]
USER_PROCESS: 210 console
11/18/11 8:38:12 PM
reboot[264]
BOOT_TIME: 1321673892 663474
11/18/11 8:38:43 PM
bootlog[40]
BOOT_TIME: 1321673906 0
11/18/11 8:39:06 PM
loginwindow[27]
USER_PROCESS: 27 console
11/18/11 9:45:07 PM
loginwindow[27]
DEAD_PROCESS: 27 console
11/18/11 9:45:08 PM
shutdown[387]
SHUTDOWN_TIME: 1321677908 37081
11/18/11 10:20:09 PM
bootlog[40]
BOOT_TIME: 1321680000 0
11/18/11 10:20:44 PM
loginwindow[28]
USER_PROCESS: 28 console
11/18/11 11:56:22 PM
loginwindow[28]
DEAD_PROCESS: 28 console
11/18/11 11:56:22 PM
shutdown[328]
SHUTDOWN_TIME: 1321685782 469361
11/19/11 5:41:15 AM
bootlog[40]
BOOT_TIME: 1321706467 0
11/19/11 5:42:10 AM
shutdown[99]
SHUTDOWN_TIME: 1321706530 778985
11/19/11 5:49:24 AM
bootlog[40]
BOOT_TIME: 1321706956 0
11/19/11 5:49:52 AM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 12:35:11 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 12:35:11 PM
shutdown[658]
SHUTDOWN_TIME: 1321731311 570256
11/19/11 4:26:55 PM
bootlog[40]
BOOT_TIME: 1321745206 0
11/19/11 4:27:31 PM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 4:49:55 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 4:49:55 PM
shutdown[214]
SHUTDOWN_TIME: 1321746595 832157
11/19/11 4:50:36 PM
bootlog[40]
BOOT_TIME: 1321746619 0
11/19/11 4:51:00 PM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 6:34:58 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 6:34:58 PM
shutdown[266]
SHUTDOWN_TIME: 1321752898 862103
11/20/11 12:48:24 AM
bootlog[40]
BOOT_TIME: 1321775295 0
11/20/11 12:48:50 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 12:50:56 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 12:50:56 AM
shutdown[190]
SHUTDOWN_TIME: 1321775456 727774
11/20/11 12:51:57 AM
bootlog[40]
BOOT_TIME: 1321775508 0
11/20/11 12:52:15 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 2:44:47 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 2:44:48 AM
shutdown[287]
SHUTDOWN_TIME: 1321782288 27378
11/20/11 9:40:35 AM
bootlog[40]
BOOT_TIME: 1321807226 0
11/20/11 9:45:38 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 1:10:45 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 1:10:45 PM
shutdown[376]
SHUTDOWN_TIME: 1321819845 699702
11/20/11 2:47:41 PM
bootlog[40]
BOOT_TIME: 1321825653 0
11/20/11 2:48:05 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 3:18:25 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 3:18:25 AM
shutdown[738]
SHUTDOWN_TIME: 1321870705 862572
11/21/11 1:41:49 PM
bootlog[40]
BOOT_TIME: 1321908100 0
11/21/11 1:42:31 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 1:45:37 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 1:45:37 PM
shutdown[199]
SHUTDOWN_TIME: 1321908337 723401
11/21/11 1:46:42 PM
bootlog[40]
BOOT_TIME: 1321908393 0
11/21/11 1:47:01 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 2:47:30 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 2:47:31 PM
shutdown[221]
SHUTDOWN_TIME: 1321912051 100508
11/21/11 9:57:25 PM
bootlog[40]
BOOT_TIME: 1321937836 0
11/21/11 10:00:25 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 10:05:34 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 10:05:34 PM
shutdown[197]
SHUTDOWN_TIME: 1321938334 457516
11/21/11 10:05:55 PM
bootlog[40]
BOOT_TIME: 1321938345 0
11/21/11 10:06:14 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 10:36:32 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 10:36:32 PM
shutdown[249]
SHUTDOWN_TIME: 1321940192 772946
11/22/11 5:47:52 PM
bootlog[40]
BOOT_TIME: 1322009263 0
11/22/11 5:48:18 PM
loginwindow[29]
USER_PROCESS: 29 console
11/22/11 5:57:09 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/22/11 5:57:10 PM
shutdown[180]
SHUTDOWN_TIME: 1322009830 100353
11/22/11 5:57:52 PM
bootlog[40]
BOOT_TIME: 1322009862 0
11/22/11 6:03:27 PM
loginwindow[29]
USER_PROCESS: 29 console
11/22/11 8:17:23 PM
login[262]
USER_PROCESS: 262 ttys000
11/22/11 8:25:20 PM
login[262]
DEAD_PROCESS: 262 ttys000
11/22/11 10:02:20 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/22/11 10:02:20 PM
shutdown[501]
SHUTDOWN_TIME: 1322024540 841538
11/23/11 11:09:36 AM
bootlog[40]
BOOT_TIME: 1322071768 0
11/23/11 11:12:10 AM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 11:16:40 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 11:16:40 AM
shutdown[201]
SHUTDOWN_TIME: 1322072200 484093
11/23/11 11:17:01 AM
bootlog[40]
BOOT_TIME: 1322072211 0
11/23/11 11:17:22 AM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 11:57:01 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 11:57:01 AM
shutdown[219]
SHUTDOWN_TIME: 1322074621 710897
11/23/11 6:10:29 PM
bootlog[40]
BOOT_TIME: 1322097020 0
11/23/11 6:11:30 PM
shutdown[107]
SHUTDOWN_TIME: 1322097090 157202
11/23/11 6:11:48 PM
bootlog[40]
BOOT_TIME: 1322097100 0
11/23/11 6:12:07 PM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 6:43:45 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 6:43:45 PM
shutdown[212]
SHUTDOWN_TIME: 1322099025 671753
11/24/11 3:06:36 AM
bootlog[40]
BOOT_TIME: 1322129187 0
11/24/11 3:07:23 AM
loginwindow[29]
USER_PROCESS: 29 console
11/24/11 3:25:50 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/24/11 3:26:16 AM
shutdown[263]
SHUTDOWN_TIME: 1322130376 181854
11/24/11 3:41:59 PM
bootlog[40]
BOOT_TIME: 1322174510 0
11/24/11 3:42:29 PM
loginwindow[29]
USER_PROCESS: 29 console
11/24/11 5:41:41 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/24/11 5:41:44 PM
shutdown[182]
SHUTDOWN_TIME: 1322181704 304082
11/24/11 5:42:27 PM
bootlog[40]
BOOT_TIME: 1322181730 0
11/24/11 5:42:44 PM
shutdown[107]
SHUTDOWN_TIME: 1322181764 200841
11/25/11 1:06:30 AM
bootlog[40]
BOOT_TIME: 1322208382 0
11/25/11 1:07:20 AM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 2:02:05 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 2:02:05 AM
shutdown[243]
SHUTDOWN_TIME: 1322211725 412106
11/25/11 12:19:23 PM
bootlog[40]
BOOT_TIME: 1322248755 0
11/25/11 12:19:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 12:21:18 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 12:21:19 PM
shutdown[185]
SHUTDOWN_TIME: 1322248879 181508
11/25/11 12:21:40 PM
bootlog[40]
BOOT_TIME: 1322248891 0
11/25/11 12:21:58 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 2:31:25 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 2:31:25 PM
shutdown[388]
SHUTDOWN_TIME: 1322256685 817758
11/25/11 3:55:28 PM
bootlog[40]
BOOT_TIME: 1322261718 0
11/25/11 3:55:55 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 3:57:10 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 3:57:11 PM
shutdown[159]
SHUTDOWN_TIME: 1322261831 182162
11/25/11 5:12:01 PM
bootlog[40]
BOOT_TIME: 1322266311 0
11/25/11 5:12:20 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 5:22:48 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 5:22:48 PM
shutdown[196]
SHUTDOWN_TIME: 1322266968 596246
11/25/11 5:50:55 PM
bootlog[40]
BOOT_TIME: 1322268646 0
11/25/11 6:04:42 PM
loginwindow[29]
USER_PROCESS: 29 console
11/26/11 12:28:03 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/26/11 12:28:03 AM
shutdown[527]
SHUTDOWN_TIME: 1322292483 989128
11/26/11 9:56:40 AM
bootlog[40]
BOOT_TIME: 1322326592 0
11/26/11 10:16:17 AM
loginwindow[29]
USER_PROCESS: 29 console
11/26/11 10:18:14 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/26/11 10:18:14 AM
shutdown[203]
SHUTDOWN_TIME: 1322327894 987763
11/26/11 10:18:35 AM
bootlog[40]
BOOT_TIME: 1322327907 0
11/26/11 10:18:54 AM
loginwindow[29]
USER_PROCESS: 29 console
11/27/11 12:51:27 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/27/11 12:51:28 AM
shutdown[592]
SHUTDOWN_TIME: 1322380288 289445
11/27/11 8:33:25 PM
bootlog[40]
BOOT_TIME: 1322451196 0
11/27/11 8:34:08 PM
loginwindow[29]
USER_PROCESS: 29 console
11/27/11 8:35:39 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/27/11 8:35:39 PM
shutdown[158]
SHUTDOWN_TIME: 1322451339 576729
11/27/11 8:35:59 PM
bootlog[40]
BOOT_TIME: 1322451350 0
11/27/11 8:36:16 PM
loginwindow[29]
USER_PROCESS: 29 console
11/28/11 2:20:14 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/28/11 2:20:17 AM
shutdown[330]
SHUTDOWN_TIME: 1322472017 680079
11/28/11 11:32:31 AM
bootlog[40]
BOOT_TIME: 1322505141 0
11/28/11 11:33:01 AM
loginwindow[29]
USER_PROCESS: 29 console
11/28/11 6:34:50 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/28/11 6:34:50 PM
shutdown[473]
SHUTDOWN_TIME: 1322530490 514177
11/29/11 12:49:32 AM
bootlog[40]
BOOT_TIME: 1322552963 0
11/29/11 12:51:15 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 4:40:24 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 4:40:24 AM
shutdown[609]
SHUTDOWN_TIME: 1322566824 951691
11/29/11 9:00:52 AM
bootlog[40]
BOOT_TIME: 1322582442 0
11/29/11 9:01:10 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:44:53 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:44:53 AM
shutdown[176]
SHUTDOWN_TIME: 1322585093 264673
11/29/11 10:54:01 AM
bootlog[40]
BOOT_TIME: 1322589232 0
11/29/11 10:54:17 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 11:12:07 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 11:12:07 AM
shutdown[162]
SHUTDOWN_TIME: 1322590327 902267
11/29/11 8:32:30 PM
bootlog[40]
BOOT_TIME: 1322623940 0
11/29/11 8:32:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:35:59 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:35:59 PM
shutdown[188]
SHUTDOWN_TIME: 1322627759 382014
11/29/11 9:36:59 PM
bootlog[40]
BOOT_TIME: 1322627810 0
11/29/11 9:39:05 PM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:39:35 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:39:35 PM
shutdown[158]
SHUTDOWN_TIME: 1322627975 625235
11/29/11 9:42:45 PM
bootlog[40]
BOOT_TIME: 1322628157 0
11/29/11 9:43:17 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 2:15:04 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 2:15:04 AM
shutdown[440]
SHUTDOWN_TIME: 1322644504 701322
11/30/11 3:26:41 PM
bootlog[40]
BOOT_TIME: 1322691992 0
11/30/11 3:27:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 3:29:39 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 3:29:40 PM
shutdown[188]
SHUTDOWN_TIME: 1322692180 264860
11/30/11 3:30:15 PM
bootlog[40]
BOOT_TIME: 1322692207 0
11/30/11 3:30:41 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 3:52:12 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 3:52:12 PM
shutdown[194]
SHUTDOWN_TIME: 1322693532 474756
11/30/11 9:18:14 PM
bootlog[40]
BOOT_TIME: 1322713080 0
11/30/11 9:18:46 PM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 5:57:47 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 5:57:47 AM
shutdown[869]
SHUTDOWN_TIME: 1322744267 855950
12/1/11 9:52:39 AM
bootlog[40]
BOOT_TIME: 1322758350 0
12/1/11 9:53:01 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 10:24:02 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 10:24:03 AM
shutdown[234]
SHUTDOWN_TIME: 1322760243 279103
12/1/11 10:24:22 AM
bootlog[40]
BOOT_TIME: 1322760253 0
12/1/11 10:24:41 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 10:41:30 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 10:41:31 AM
shutdown[240]
SHUTDOWN_TIME: 1322761291 172303
12/1/11 10:48:01 AM
bootlog[40]
BOOT_TIME: 1322761671 0
12/1/11 10:50:46 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 11:44:03 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 11:44:03 AM
shutdown[244]
SHUTDOWN_TIME: 1322765043 549953
12/2/11 12:51:18 AM
bootlog[40]
BOOT_TIME: 1322812270 0
12/2/11 12:51:49 AM
loginwindow[29]
USER_PROCESS: 29 console
12/2/11 2:06:17 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/2/11 2:06:17 AM
shutdown[245]
SHUTDOWN_TIME: 1322816777 845146
12/2/11 10:48:28 AM
bootlog[40]
BOOT_TIME: 1322848098 0
12/2/11 10:48:50 AM
loginwindow[29]
USER_PROCESS: 29 console
12/3/11 1:49:58 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/3/11 1:49:59 AM
shutWhy did you put up with all those issues for a year?
-
Driver issue with GTX470 and GTX570 in CS5.03
So we have two different video cards as we can't find the GTX470 easily anymore.
Both computers when the video card driver is updated to a newer version the video is displayed weird.
The rest of the hardware is the same on both computers Core i5 3.3ghz, 8gb ram, msi motherboard, and RT.X2 matrox card.
This also happens on Preview and Program as well, unless the video is stopped, but while playing it always does this.
I was able to fix the problem by going to an older version of the drivers. The GTX570 is using 275.33, and the GTX470 is using 280.26.
I haven't really had too much time to mess around with the video drivers on the GTX570 as I needed to get the computer up and running ASAP so I just grabed an older driver off of nvidia's website. Which is the reason the GTX570 drivers are older than the GTX470.
Now is this an issue with the RT.X2 card or something with premiere?
The GTX570 system is a clean install.
I manually added the GTX570 to the cuda support list in order to get it to work on CS5.03The problem lies with Matrox itself: Matrox has never provided bug-free drivers to begin with. Every single driver release from them fixed one problem but created a new problem - and yet they still failed to fully fix the same problem that plagues their drivers for ages.
Maybe you are looking for
-
Can't download game and browse web at same time
I'm hoping someone can help me with this problem. For about a month now, I'm unable to download a game from Big Fish Games and browse the web at the same time. I've contacted BFG, but so far their only suggestion was to upgrade from i.e. 6 to i.e.
-
Table fields to match pdf form
I found this on my formscentral help file. Note: Some types of form fields aren't supported when you import a PDF form. For example, text fields with formatting applied, such as numeric or percentage fields, are converted to plain text fields. And, s
-
Table Colspan? (Very Urgent!!!)
Hello, I have a site finished that I need to upload tonight. When I started, my graphics guy sent me all the images sliced up with photoshop. PS also generated the table code for it and thats what I used. Now, I need to update the nav bar with new na
-
Subject does not show in subscribed ical calender
I am subscribed to two iCal calanders which are published thru .Mac. Since two weeks one of them does show there is an event with the associated time but there is no subject of the event visible. I checked the original calender and everything seems t
-
Adobe PDF Toolbar Not Showing In Firefox
I installed CS5 Master Collection in Windows 7 64 and Adobe PDF toolbar installed automatically in IE8 but not in Firefox latest version. Would somebody please tell me what to do to install in Firefox? Thanks a lot!