Jump to content


Bad File Name


6 replies to this topic

#1 WillEllen

    Member

  • Members
  • PipPip
  • 11 posts

Posted 11 June 2010 - 06:03 PM

Got this message today before downloading of files starts:
"Bad file name or number in prjUpdater.mdlGeneral.createPath at line 114"

How to correct this?
Thanks, WillEllen

#2 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 11 June 2010 - 06:40 PM

I got the same pop-up before the download for .NET started.
Verification also failed for both DirectX and .NET

apup_DX_Jun10.log
Spoiler

apup_NET_Jun11.log
Spoiler

Edited by click-click, 11 June 2010 - 07:42 PM.


#3 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 11 June 2010 - 08:46 PM

I saw your post here and reran the DirectX download. I can confirm that I no longer get a verfication error for that component.

#4 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 11 June 2010 - 08:50 PM

.NET is still giving me problems though.

#5 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 11 June 2010 - 11:05 PM

ok. i will do an full download test for the .net package tonight

[]s

#6 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 12 June 2010 - 12:34 AM

i think that i've found the issue. this was the first thing being downloaded in that script. apup downloads things in reverse mode and this makes the download of the rti file the reason for the issue. i've re-write that part of the script, but monday this one will go to the bugtrack

by the way: will take something like 4h to complete the whole download of this package. but right now, no issues at all

[]s

#7 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 12 June 2010 - 01:43 PM

View PostCristiano, on 12 June 2010 - 12:34 AM, said:

i think that i've found the issue. this was the first thing being downloaded in that script. apup downloads things in reverse mode and this makes the download of the rti file the reason for the issue. i've re-write that part of the script, but monday this one will go to the bugtrack

by the way: will take something like 4h to complete the whole download of this package. but right now, no issues at all

[]s

Fixed now, dotnet.rti updated and Autopatcher is back to Official.

Thanks.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users