|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
#11
|
|||
|
|||
|
tried v17.1 to begin with (will do key cd and v27 if successful i thought) i loaded ImgBurn and selected BMW NaviSoft 17_1.img as source image set mode to write set write speed to 1x put in known new cdr checked sectors reported 16,127 mode 2/form1 but got failed cdr and noticed in the TOC is reported Track 01 (mode2 form 2) |
| Sponsored Links | |
|
|
|
|
#12
|
|||
|
|||
|
Write at a speed supported by the media, not at 1x. ImgBurn will show you what the supported write speeds are. Burn too slow and you make errors.
|
|
#13
|
|||
|
|||
|
tried speed x2, x3, x4 and still get failed on verify. gone thro' cds like anything
is there anyway of checking the speed (i did notice on one burn that the write speed was x4 hence my setting to that the next time). clearly i havent grasped how to do this. this there a idiots guide cos thats what i need i think. |
|
#14
|
|||
|
|||
|
ImgBurn shows you the speeds supported by your media.
When you insert a blanck CD, and ImgBurn is in Write mode, look at the right hand window of ImgBurn. Mine shows: Disc Information: Status: Empty Erasable: No Free Sectors: 359,847 Free Space: 736,966,656 bytes Free Time: 79:59:72 (MM:SS:FF) Supported Write Speeds: 16x, 24x, 40x, 48x So I would never use 1x, 2x, 3x or 4x for my CDs. |
|
#15
|
|||
|
|||
|
hi jochen - i dont seem to have the supported write speed bit on mine
|
|
#16
|
|||
|
|||
|
Then look on the CD box to see what it says, or look on the CD itself, or experiment using the knowledge you have gained from my previous 2 posts.
|
|
#17
|
|||
|
|||
|
I tried to burn v17.1 using a different pc and this time i did see the write speeds however set to the lowest however the cd still failed 'on verify'.
what was interesting was that i noticed that it was imgburn reported mode 2/form 1 before burning but after burning it was mode 2/form 2. I have spent a long time reading various posts on this site and bimmerboard. The v17 (for that matter v18-v22) image is proving difficult to get hold of. This post have caught my attention ttp://www.xoutpost.com/navigation-system/24896-mk3-dead-help-please.html?highlight=dead because it refers to the same issue in terms of imgburn changing to mode 2/form 2; reference to post 30 which might be my problem? KiwiJochen you said in post 14 you had a mode2cdmaker.exe do you still have it and this might allow a correct image file to be generated If anyone has upgraded a mkiii up to v22 recently (and then to the final update level of sw3 1/63) and could share their experience i would most appreciate hearing from you. Any heads up on links to get image files would be great also. |
|
#18
|
|||
|
|||
|
Quote:
Make sure you are using an unaltered OS image. mode2cdmaker is really hard to use, I replaced it with MagicISO and that was much easier. I upgraded loads of Mk3s to 3-1/63. I crashed a couple until I learnt they had to be Mode2/Form1, and then after I made Mode2/Form1 images with ImgBurn I never had any trouble. |
|
#19
|
|||
|
|||
|
i plan to go straight from my v16.2 to v22.1 then on to v29?
two questions still unanswered: 1. will this do a complete reload of the old memory map OS and then upgrade to the new memory map OS? 2. will it ask for a cd key at any point? Last edited by ssd; 11-20-2008 at 01:32 PM. |
![]() |
| Bookmarks |
|
|
|
|