Morteza-1992
کاربر سایت
جزئیات جدید از UPDATE Xbox Live | آخرین UPDATE در June-20-2012
- Thread starter Police _ 110
- تاریخ آغاز
احتمالش که کمتر میشه ولی ممکنه بازم ماکرو lt روی دستگاه رو شناسایی کنه در ضمن 3 ساله که کسی رو بن نکرده
soltane7posh
کاربر سایت
ما که صبر میکنیم که امنیت کامل رو سی 4 تایید کنه آخه لایو بریم چیکار یه پی اس میزدیم که 2013 الان هیچکی نیست تو پی اس پس همون آفلاین فعلا میزنیم 
poma
کاربر سایت
دوستانی که زبانشون خوبه ببینید چی میگه؟
Nothing is wrong with LT+. If you read the LTU/PCB post, you'll see it notes that LTU is based on LT+ v3.0. LT+ will still exist on its own and will still be updated if/when needed for drives that can use it. LTU is simply for drives that absolutely require the PCB (DG-16D5S and DLN10N), but can also be used for DG-16D4S+new PCB if so desired. But if you have a DG-16D4S (with original board or v1.0/v1.1 PCB), you can just keep on using it with LT+. When necessary, any changes made or features added to LTU will also be mirrored to LT+ and vice-versa
Nothing is wrong with LT+. If you read the LTU/PCB post, you'll see it notes that LTU is based on LT+ v3.0. LT+ will still exist on its own and will still be updated if/when needed for drives that can use it. LTU is simply for drives that absolutely require the PCB (DG-16D5S and DLN10N), but can also be used for DG-16D4S+new PCB if so desired. But if you have a DG-16D4S (with original board or v1.0/v1.1 PCB), you can just keep on using it with LT+. When necessary, any changes made or features added to LTU will also be mirrored to LT+ and vice-versa
Carnage
کاربر سایت
این پست ربطی به آپدیت نداره و توضیح ادمین C4evaspeaks در مورد فیرمور جدید LTU هست . این فیرمور با LT+ 3 تفاوتی نداره و فقط برای درایو هایی ساخته شده که LT+ 3 روی اون ها عمل نمی کرد و در واقع بیس اصلی LTU همون LT+ 3 هست . این فریمور برای درایو هایی مثل Lite-on DG-16D5S و Hitachi DLN10N مناسبه .
Hossein505
کاربر سایت
poma
کاربر سایت
درود، پندار عزیز چه قدر خوب میشد شما که زبانت خوبه پستهای جدید C4 رو با ترجمه میگذاشتی اینجا که انقدر سوال بیجا نشه. البته تا همینجا هم کلی زحمت کشیدی. ممنون. اگه وقت کری این هم ترجمه کن.
I purposely don't attest to whether any particular update is safe or not until it's 100% factual. The standard practice is checking if backups work offline and on LIVE across the different drives and fw's, as well as with xk3y. Those initial tests help to rule-out different things that would signify an update is potentially unsafe, but cannot account for any changes on a system level between the 360 and the drive itself that might be deemed unsafe. That latter portion (the "LIVE logs") is strictly done by c4eva. People have the choice of whether they wish to go ahead and update based on the fact that nothing appears wrong and that backups still work, or to wait for the thumbs-up from c4eva. If or when he does a log is entirely up to his discretion. In most cases though, any changes that affect backups, fw, or detectability which would make it unsafe are usually caught during the basic tests and analysis — well before a LIVE log is even done.
I purposely don't attest to whether any particular update is safe or not until it's 100% factual. The standard practice is checking if backups work offline and on LIVE across the different drives and fw's, as well as with xk3y. Those initial tests help to rule-out different things that would signify an update is potentially unsafe, but cannot account for any changes on a system level between the 360 and the drive itself that might be deemed unsafe. That latter portion (the "LIVE logs") is strictly done by c4eva. People have the choice of whether they wish to go ahead and update based on the fact that nothing appears wrong and that backups still work, or to wait for the thumbs-up from c4eva. If or when he does a log is entirely up to his discretion. In most cases though, any changes that affect backups, fw, or detectability which would make it unsafe are usually caught during the basic tests and analysis — well before a LIVE log is even done.
Carnage
کاربر سایت
خواهش می کنم دوست عزیز خوشحال میشم بتونم کمک کنم .
در اینجا ادمین میگه که اولین قدم برای تایید امنیت آپدیت ها چک کردن اینه که آیا بک آپ ها در حالت آفلاین و آنلاین با داشبورد جدید کار می کنن یا نه ، ولی این کار فقط تغییرات انجام شده در آپدیت رو نشون میده و نمیشه فهمید که در خود دستگاه و درایو اون چه تغییراتی انجام شده . برای تایید 100 درصد امنیت آپدیت C4eva شخصا Live Log ها رو انجام میده و این کار رو جز اون کس دیگری نمی تونه انجام بده . مردم هم می تونن ریسک کنن و فقط با دونستن اینکه دیسک ها اجرا میشه آپدیت کنند و یا منتظر تایید C4eva بمونن . زمان انجام Live Log ها هم کاملا به خودش بستگی داره .
گفته شده در اکثر مواقع اگه تغییری انجام شده باشه که فیرمور و دیسک ها رو تحت تاثیر قرار داده باشه در تست های اولیه و قبل از انجام شدن Live Log ها مشخص میشه .
کاربرانی که این گفتگو را مشاهده می‌کنند
Google