rietveld Posted January 19, 2021 Share Posted January 19, 2021 (edited) Not sure if anyone else has noticed this? If I boot the Adamlink V MIB software via ADE it works perfectly but If I boot a physical disk of this program it goes to the Config screen as normal but as soon as I go into terminal mode it says "lost carrier" and freezes. The physical disk is an exact copy that I made using the ADE. Edited January 19, 2021 by rietveld Quote Link to comment Share on other sites More sharing options...
rietveld Posted January 23, 2021 Author Share Posted January 23, 2021 fixed Quote Link to comment Share on other sites More sharing options...
NIAD Posted January 23, 2021 Share Posted January 23, 2021 What was the issue in case others run into the same problem? Quote Link to comment Share on other sites More sharing options...
rietveld Posted January 23, 2021 Author Share Posted January 23, 2021 4 hours ago, NIAD said: What was the issue in case others run into the same problem? Port defaults to the Orphaware 68 just changed modem and video to mi1 and mi2 very werid that the ADE disk was configured but the config did not copy over to the physical copy Quote Link to comment Share on other sites More sharing options...
Tekman Posted January 24, 2021 Share Posted January 24, 2021 That is odd. It should be an exact copy with config and all. What copy program do you use? Quote Link to comment Share on other sites More sharing options...
rietveld Posted January 24, 2021 Author Share Posted January 24, 2021 2 hours ago, Tekman said: That is odd. It should be an exact copy with config and all. What copy program do you use? I used File Manager Quote Link to comment Share on other sites More sharing options...
NIAD Posted January 24, 2021 Share Posted January 24, 2021 If AL5 writes the config to a specific block or blocks (say 159) and not to a file, File Manager may have only copied the used blocks that it sees via reading the directory from the image file to the disk. if this is the case, AL5 would use a default config until you edit it and then save it to disk. Best practice when copying stuff with the Adam is to use the Block Copy function and copy the entire block range... 000-159 for disk and 000-255 for data pack. Adjust accordingly for larger sized drives / media. Quote Link to comment Share on other sites More sharing options...
rietveld Posted January 24, 2021 Author Share Posted January 24, 2021 2 hours ago, NIAD said: If AL5 writes the config to a specific block or blocks (say 159) and not to a file, File Manager may have only copied the used blocks that it sees via reading the directory from the image file to the disk. if this is the case, AL5 would use a default config until you edit it and then save it to disk. Best practice when copying stuff with the Adam is to use the Block Copy function and copy the entire block range... 000-159 for disk and 000-255 for data pack. Adjust accordingly for larger sized drives / media. I did not do a block copy just BACKUP so that seems to be where I went wrong Quote Link to comment Share on other sites More sharing options...
NIAD Posted January 25, 2021 Share Posted January 25, 2021 8 hours ago, rietveld said: I did not do a block copy just BACKUP so that seems to be where I went wrong It's a strong possibility, but I did not test it out myself.. only basing what I said about using the Block Copy option from years of experience. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.