Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Software Troubleshooting
TC header Windows header Troubles
Message
<blockquote data-quote="Alexdr" data-source="post: 630339" data-attributes="member: 62084"><p>Is editing a post restricted to a certain amount of time after which the post is originally posted? If so, sorry for bumping. All I wanted to add is that in using UBCD, memtest x86 found no errors after 3 passes (just did it because why not). Also, in running testdisk which loads me into the PartedMagic OS environment, it seems that all 3 partitions are "intact". I.e. the bios one, the recovery one, and then the one with all of my data. I can even access all of my data from here. Therefore, the big question remains, despite the recovery partition seemingly being fine, despite my filesystem seemingly being fine, despite the bios section seemingly being fine (actually, I don't know how the bios partition should look, but, there is no garbled data), why does it give me the "No bootable media" screen on start-up? (I think I can access the system's personal recovery partition, I've yet to try. Maybe it'll yield different results than running the disc's recovery module, however, if anything, one would thing the ones from the disc, which certainly aren't corrupted, would yield "at least as good as" results as those in the recovery partition).</p><p>It'll be nice if I can figure this all out on my own, then, maybe, my thread could serve as some use to people in the future who deal with this issue. Afterall, I would hate for this to turn out like that (one of the few true) XKCD comic where the last post in the thread on an issue was in 2004 with no resolution.</p><p>As an addendum:</p><p>To those who are using Veracrypt, maybe I'm misinformed, however, I thought Veracrypt was backwards compatible with TrueCrypt volumes. However, in attempting to use the latest VeraCrypt to mount an encrypted drive/volume using a SATA-to-USB (trying every combination of settings), yielded error 7763. However, in using the last 7.1a TrueCrypt software it worked immediately with simple auto-mount no-pre-boot-authentication (since it was a drive with a system partition, I assumed to do this).</p></blockquote><p></p>
[QUOTE="Alexdr, post: 630339, member: 62084"] Is editing a post restricted to a certain amount of time after which the post is originally posted? If so, sorry for bumping. All I wanted to add is that in using UBCD, memtest x86 found no errors after 3 passes (just did it because why not). Also, in running testdisk which loads me into the PartedMagic OS environment, it seems that all 3 partitions are "intact". I.e. the bios one, the recovery one, and then the one with all of my data. I can even access all of my data from here. Therefore, the big question remains, despite the recovery partition seemingly being fine, despite my filesystem seemingly being fine, despite the bios section seemingly being fine (actually, I don't know how the bios partition should look, but, there is no garbled data), why does it give me the "No bootable media" screen on start-up? (I think I can access the system's personal recovery partition, I've yet to try. Maybe it'll yield different results than running the disc's recovery module, however, if anything, one would thing the ones from the disc, which certainly aren't corrupted, would yield "at least as good as" results as those in the recovery partition). It'll be nice if I can figure this all out on my own, then, maybe, my thread could serve as some use to people in the future who deal with this issue. Afterall, I would hate for this to turn out like that (one of the few true) XKCD comic where the last post in the thread on an issue was in 2004 with no resolution. As an addendum: To those who are using Veracrypt, maybe I'm misinformed, however, I thought Veracrypt was backwards compatible with TrueCrypt volumes. However, in attempting to use the latest VeraCrypt to mount an encrypted drive/volume using a SATA-to-USB (trying every combination of settings), yielded error 7763. However, in using the last 7.1a TrueCrypt software it worked immediately with simple auto-mount no-pre-boot-authentication (since it was a drive with a system partition, I assumed to do this). [/QUOTE]
Insert quotes…
Verification
Post reply
Top