Thread: Addressing file corruption after yanking the cable too soon [ver. 2022.01]
View Single Post
Old 01-14-2023, 05:03 PM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Quote:
Originally Posted by JawadLeLogeur View Post
Now the folder won't appear and neither will some of the files as viewed from KOReader once the UBSMS sessions is terminated.
Oh, thought you were talking about Nickel's library view (as we... don't have a library view ^^).

So, what *exactly* do you see in Explorer (ideally, I'd prefer a full recursive command line listing, but, barring that, a screenshot would be helpful, assuming your Explorer is setup to show file extensions).

----

While I doubt this will change anything in this particular case, yes, I wholeheartedly agree with @mergen3107: never report a bug against old code .
NiLuJe is offline   Reply With Quote