URI /webwork2/Testing2/instructor/setmaker/ In WeBWorK::ContentGenerator::go called at line 353 of /opt/webwork/webwork2/lib/WeBWorK.pm In WeBWorK::ContentGenerator::content called at line 194 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm In WeBWorK::Template::template called at line 490 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm In WeBWorK::ContentGenerator::Instructor::SetMaker::body called at line 152 of /opt/webwork/webwork2/lib/WeBWorK/Template.pm In WeBWorK::Utils::Tasks::renderProblems called at line 1309 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator/Instructor/SetMaker.pm In WeBWorK::PG::new called at line 262 of /opt/webwork/webwork2/lib/WeBWorK/Utils/Tasks.pm In WeBWorK::PG::Local::new called at line 52 of /opt/webwork/webwork2/lib/WeBWorK/PG.pm The information below can help locate the source of the problem. We select an NPL Problem Direectory, such as 270/setDerivatives6InverseTrig, and click the "View Problems" button then get the following httpd-error.log entry: Invalid offset: MDT\n * in WeBWorK::PG::Local::new called at line 52 of /opt/webwork/webwork2/lib/WeBWorK/PG.pm\n * in WeBWorK::PG::new called at line 262 of /opt/webwork/webwork2/lib/WeBWorK/Utils/Tasks.pm\n * in WeBWorK::Utils::Tasks::renderProblems called at line 1309 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator/Instructor/SetMaker.pm\n * in WeBWorK::ContentGenerator::Instructor::SetMaker::body called at line 152 of /opt/webwork/webwork2/lib/WeBWorK/Template.pm\n * in WeBWorK::Template::template called at line 490 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::content called at line 194 of /opt/webwork/webwork2/lib/WeBWorK/ContentGenerator.pm\n * in WeBWorK::ContentGenerator::go called at line 353 of /opt/webwork/webwork2/lib/WeBWorK.pm and the following web page error details: Error messages Saying that tho, I suppose it ain't too bad if the graph at "Tom's Hardware Guide" is anything to go by.The nf file has the only reference to "MDT" that we know of: Only got around 8500 after a clean install with no other apps loaded (not OCed). Still getting crap "3DMark" scores as well. I'll suppose I'll just have to wait until "Nvidia" release the 41.03s for "W98SE" (that's if they decide it's worthwhile). So my "Nview" problem must definately be a problem with the 40.72 Dets (as some will have already determined). I figure I may have to do a clean install of "Windows".Ĭlick to expand.I don't know what that's supposed to tell me!:|Īnyway, I finally gave up trying to figure out why I coudn't get my damn "Geforce 4" working properly, so I decided to do a clean installation of "Windows" (Jeez, I hate doing that).Īfter installing "WIndows" on the freshly formatted C:\ partition I installed the 40.72 dets and the latest "WDM" driver and "MyViVo" software and everything is as it should be with regard to recording the audio while capturing video. I haven't tried tried installing the WDM driver or video capture software yet, so I don't know if my other problem is fixed yet. I have also used various "Nvidia" file/registry removal and registry cleaning tools as well (DD, NVCleaner, Detonator 30.xx To 40.xx Fix, RegCleaner, RegClean etc) in between installin different drivers.Īnyway, I installed the 40.72 "Detonators" again only to find out that the "Nview" now doesn't work. I ended up going back to the last WHQL version (30.82 IIRC) and tried various versions of the WDM driver (v1.08, v1.11, v1.12 and v1.16), but the problem still existed so I nuked them so I could try out the 40.72 once again. I have tried various different "WDM" drivers, as well as the "Leadtek" and "Detonator" display drivers (uninstalling and what not in between of course). I have been having problems with the ViVo on my "Leadtek Ti4200 128MB" for some time (no sound captured in videos for some reason).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |