Article View: pl.comp.pecet
Article #1274050Re: Gniazdo M2
From: PiteR
Date: Thu, 08 Feb 2024 06:43
Date: Thu, 08 Feb 2024 06:43
22 lines
1606 bytes
1606 bytes
in <news:uq16ef$1l4rs$1@dont-email.me> user Eneuel Leszek Ciszewski pisze tak: > > W dniu 7 lut 2024 o 19:05, PiteR pisze: > > >> Jaki dysk do gniazda M2, - SATA czy NVMe? Instrukcja płyty > >> głównej > > Wg supportu Acera mój laptop na Intelu (qpiony chyba 08 lutego > 2017 roku w Media Expert) nie może obsłużyć NVMe nie wierzę > > Dysk SATA ma dwa wycięcia K + M a dysk NVMe ma klucz M. > > K czy B? B https://ibb.co/3mDJHfH
Technical Details
Message-ID:
<XnsB1124468785BAPanElektronik@127.0.0.1>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.chmurka.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mailReferences:
<upvl51$1clul$1@dont-email.me> <XnsB111B81EDB86APanElektronik@127.0.0.1> <uq16ef$1l4rs$1@dont-email.me>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.chmurka.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: PiteR <email@fauszywy.pl>
Newsgroups: pl.comp.pecet
Subject: Re: Gniazdo M2
Date: Thu, 08 Feb 2024 06:43:29 GMT
Organization: Monsters Inc
Lines: 22
Message-ID: <XnsB1124468785BAPanElektronik@127.0.0.1>
References: <upvl51$1clul$1@dont-email.me> <XnsB111B81EDB86APanElektronik@127.0.0.1> <uq16ef$1l4rs$1@dont-email.me>
Reply-To: email@fauszywy.pl
MIME-Version: 1.0
Injection-Info: dont-email.me; posting-host="f95cbeeaebcb1edbec5f7cfe6708a958"; logging-data="1963067"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+xjxGgzxvlUcZKSVTzBa/89mjMbsqKEXk="
User-Agent: Xnews/05.08.12 Mime-proxy/1.4.c.4 (Win32)
Cancel-Lock: sha1:SO2+YvuvVmIWe2vg2hfBSFhCWkw=
X-Face: C^HRLBcK33&VX0Qvc-lhx|on0=gvcaNz:XzFo<N*<NW-J7+.OAwPPq?tZV@^~]M/Y9<3Sq8(qjx+>U[W(jeT{Td+ntPt5kGq85XTTd+as}aWNH7\EM|<G,9y>usf*Sy2?FEE*Psd-E]Xp&"_:$bhxl|*V3&{{N?cF(!Z*7OcD<oCG+63W+Ji%;
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit