Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > aus.computers > #56471 > unrolled thread
| Started by | felix <me@nothere.invalid> |
|---|---|
| First post | 2016-12-21 18:20 +1100 |
| Last post | 2016-12-30 15:40 +1100 |
| Articles | 9 on this page of 89 — 13 participants |
Back to article view | Back to aus.computers
Windose 10 felix <me@nothere.invalid> - 2016-12-21 18:20 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-21 18:36 +1100
Re: Windose 10 jonz <johnhhhinton7@gmail.com> - 2016-12-21 03:13 -0800
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-22 05:59 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 06:49 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 07:50 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 08:16 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 08:32 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 09:46 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 10:04 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 11:48 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 07:33 +1000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 08:41 +1100
Re: Windose 10 Frank Slootweg <this@ddress.is.invalid> - 2016-12-22 16:08 +0000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-23 06:09 +1100
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-24 07:54 +1100
Re: Windose 10 "John" <dj34d@gmail.com> - 2016-12-22 11:34 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-21 22:30 +1100
Re: Windose 10 not@telling.you.invalid (Computer Nerd Kev) - 2016-12-21 21:46 +0000
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 09:48 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 10:06 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 11:49 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:13 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 14:42 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:12 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-21 22:06 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:08 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 14:44 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 21:05 +1100
Re: Windose 10 Frank Slootweg <this@ddress.is.invalid> - 2016-12-22 16:21 +0000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 17:47 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-23 10:52 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 17:49 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-23 17:57 +1100
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-23 19:11 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:29 +1100
Re: Windose 10 not@telling.you.invalid (Computer Nerd Kev) - 2016-12-23 11:28 +0000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-24 05:46 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-24 07:19 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:47 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:46 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:50 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-25 07:34 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:59 +1100
Re: Windose 10 Grumpy Tech <grumpytech07@gmail.com> - 2016-12-24 21:09 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-25 00:06 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-25 16:57 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-25 17:49 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 00:26 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 08:21 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 09:36 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:16 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:27 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:43 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:50 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 12:36 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 12:57 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-26 12:02 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 12:51 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-26 11:52 +1000
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-27 18:26 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-25 09:30 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-22 21:30 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 00:07 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-23 09:13 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-28 20:35 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-29 04:52 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 21:15 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:27 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:34 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:53 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 23:41 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:54 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 11:01 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 11:04 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 13:27 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-30 16:08 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 17:32 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-30 19:26 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-30 23:54 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 17:35 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 21:09 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 21:07 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:53 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:52 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-30 11:43 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 13:25 +1100
Re: Windose 10 Grumpy Tech <grumpytech07@gmail.com> - 2016-12-30 14:15 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 15:40 +1100
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-30 17:35 +1100 |
| Message-ID | <ecmdgpFc9klU2@mid.individual.net> |
| In reply to | #57041 |
On Friday, 30 Dec 2016 1:27 PM, felix wrote: > On Friday, 30 Dec 2016 11:04 AM, felix wrote: >> On Friday, 30 Dec 2016 11:01 AM, felix wrote: >>> On Friday, 30 Dec 2016 5:54 AM, Rod Speed wrote: >>>> >>>> >>>> "felix" <me@nothere.invalid> wrote in message >>>> news:eckekqFsba7U1@mid.individual.net... >>>>> On Thursday, 29 Dec 2016 10:53 PM, felix wrote: >>>>>> On Thursday, 29 Dec 2016 10:34 PM, felix wrote: >>>>>>> On Thursday, 29 Dec 2016 10:27 PM, felix wrote: >>>>>>>> On Thursday, 29 Dec 2016 9:15 PM, felix wrote: >>>>>>>>> On Thursday, 29 Dec 2016 4:52 AM, Je�us wrote: >>>>>>>>>> On Wed, 28 Dec 2016 20:35:20 +1100, felix >>>>>>>>>> <me@nothere.invalid> wrote: >>>>>>>>>> >>>>>>>>>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>>>>>>>>> Stupid windows 10 has spat it's dummy. I'll have to >>>>>>>>>>>> reinstall :( (from >>>>>>>>>>>> an image of the drive) >>>>>>>>>>>> >>>>>>>>>>> I restored the drive from an image, and since it was several >>>>>>>>>>> moths old, >>>>>>>>>>> had to do umpteen updates, and some sofware installations. >>>>>>>>>>> the good news >>>>>>>>>>> is all the hardware is ok >>>>>>>>>> News? No, that isn't news. It was already established the >>>>>>>>>> hardware was >>>>>>>>>> fine. >>>>>>>>> >>>>>>>>> a thousand pardons your worship. I shall rewrite it just for >>>>>>>>> you.. >>>>>>>>> >>>>>>>>> "I restored the drive from an image, but since it was several >>>>>>>>> moths old, I had to do umpteen updates, and some sofware >>>>>>>>> installations. and as had been previously determined, there >>>>>>>>> are no hardware issues, fortunately. and may I just take this >>>>>>>>> opportunity to express my profound gratitude to Geebus for his >>>>>>>>> invaluable contributions in solving this very difficult and >>>>>>>>> often perplexing issue, and without whose assistance it may >>>>>>>>> never have been solved" >>>>>>>>> >>>>>>>>> better? >>>>>>>>> >>>>>>>> >>>>>>>> looks like I spoke too soon after all. I've been trying to >>>>>>>> format the drive that the faulty installation was on, but I >>>>>>>> can't get any computer to see it, either in an external USB >>>>>>>> case, or installed directly in a PC. seems it must be faulty. >>>>>>>> but because it can't be seen I can't do any diagnostics on it >>>>>>>> >>>>>>> >>>>>>> Acronis can find it but it can't format it >>>>>>> >>>>>> >>>>>> anyone know how I can test/check this drive? >>>>>> >>>>> >>>>> I was able for format it in a windows 7 machine, but when I put it >>>>> in the win10 PC I get the error message "mbr error 1". >>>> >>>> Which suggests that you arent formatting it properly. >>>> >>>> How did you format it ? >>> >>> I had created the partition as GPT so I changed it to MBR and now I >>> can boot. but how do I format a drive that win10 doesn't see? >> >> >> it's ok. disk management I guess > > finally got it sorted out. it now puts a nice picture of two giraffes instead of that black screen with the blue window, which I always hated. > seems partitioning in GPT was the problem. maybe the bios couldn't > handle it? > >> >>> >>> I've had nothing but trouble with windoze10!. life was so much >>> simpler/easier with XP you just put a drive in and it would find it >>> and ask you to format it >>> >>>> >>>>> I'm trying to find how to fix it. if the second drive is not >>>>> installed the computer will boot fine. >>>> >>>> >>> >>> >> >> > > -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-30 21:09 +1100 |
| Message-ID | <ecmq2kFf60hU1@mid.individual.net> |
| In reply to | #57041 |
"felix" <me@nothere.invalid> wrote in message news:ecluvtF9922U3@mid.individual.net... > On Friday, 30 Dec 2016 11:04 AM, felix wrote: >> On Friday, 30 Dec 2016 11:01 AM, felix wrote: >>> On Friday, 30 Dec 2016 5:54 AM, Rod Speed wrote: >>>> >>>> >>>> "felix" <me@nothere.invalid> wrote in message >>>> news:eckekqFsba7U1@mid.individual.net... >>>>> On Thursday, 29 Dec 2016 10:53 PM, felix wrote: >>>>>> On Thursday, 29 Dec 2016 10:34 PM, felix wrote: >>>>>>> On Thursday, 29 Dec 2016 10:27 PM, felix wrote: >>>>>>>> On Thursday, 29 Dec 2016 9:15 PM, felix wrote: >>>>>>>>> On Thursday, 29 Dec 2016 4:52 AM, Je�us wrote: >>>>>>>>>> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>>>>>>>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall >>>>>>>>>>>> :( (from >>>>>>>>>>>> an image of the drive) >>>>>>>>>>>> >>>>>>>>>>> I restored the drive from an image, and since it was several >>>>>>>>>>> moths old, >>>>>>>>>>> had to do umpteen updates, and some sofware installations. the >>>>>>>>>>> good news >>>>>>>>>>> is all the hardware is ok >>>>>>>>>> News? No, that isn't news. It was already established the >>>>>>>>>> hardware was >>>>>>>>>> fine. >>>>>>>>> >>>>>>>>> a thousand pardons your worship. I shall rewrite it just for you.. >>>>>>>>> >>>>>>>>> "I restored the drive from an image, but since it was several >>>>>>>>> moths old, I had to do umpteen updates, and some sofware >>>>>>>>> installations. and as had been previously determined, there are no >>>>>>>>> hardware issues, fortunately. and may I just take this opportunity >>>>>>>>> to express my profound gratitude to Geebus for his invaluable >>>>>>>>> contributions in solving this very difficult and often perplexing >>>>>>>>> issue, and without whose assistance it may never have been solved" >>>>>>>>> >>>>>>>>> better? >>>>>>>>> >>>>>>>> >>>>>>>> looks like I spoke too soon after all. I've been trying to format >>>>>>>> the drive that the faulty installation was on, but I can't get any >>>>>>>> computer to see it, either in an external USB case, or installed >>>>>>>> directly in a PC. seems it must be faulty. but because it can't be >>>>>>>> seen I can't do any diagnostics on it >>>>>>>> >>>>>>> >>>>>>> Acronis can find it but it can't format it >>>>>>> >>>>>> >>>>>> anyone know how I can test/check this drive? >>>>>> >>>>> >>>>> I was able for format it in a windows 7 machine, but when I put it in >>>>> the win10 PC I get the error message "mbr error 1". >>>> >>>> Which suggests that you arent formatting it properly. >>>> >>>> How did you format it ? >>> >>> I had created the partition as GPT so I changed it to MBR and now I can >>> boot. but how do I format a drive that win10 doesn't see? >> >> >> it's ok. disk management I guess > > finally got it sorted out. seems partitioning in GPT was the problem. > maybe the bios couldn't handle it? Very likely. >> >>> >>> I've had nothing but trouble with windoze10!. life was so much >>> simpler/easier with XP you just put a drive in and it would find it and >>> ask you to format it >>> >>>> >>>>> I'm trying to find how to fix it. if the second drive is not installed >>>>> the computer will boot fine. >>>> >>>> >>> >>> >> >> > > > -- > I plan on living forever. So far so good! >
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-30 21:07 +1100 |
| Message-ID | <ecmpvbFf50lU1@mid.individual.net> |
| In reply to | #57032 |
"felix" <me@nothere.invalid> wrote in message news:eclmf4F7ha6U1@mid.individual.net... > On Friday, 30 Dec 2016 5:54 AM, Rod Speed wrote: >> >> >> "felix" <me@nothere.invalid> wrote in message >> news:eckekqFsba7U1@mid.individual.net... >>> On Thursday, 29 Dec 2016 10:53 PM, felix wrote: >>>> On Thursday, 29 Dec 2016 10:34 PM, felix wrote: >>>>> On Thursday, 29 Dec 2016 10:27 PM, felix wrote: >>>>>> On Thursday, 29 Dec 2016 9:15 PM, felix wrote: >>>>>>> On Thursday, 29 Dec 2016 4:52 AM, Je�us wrote: >>>>>>>> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>>>>>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall >>>>>>>>>> :( (from >>>>>>>>>> an image of the drive) >>>>>>>>>> >>>>>>>>> I restored the drive from an image, and since it was several moths >>>>>>>>> old, >>>>>>>>> had to do umpteen updates, and some sofware installations. the >>>>>>>>> good news >>>>>>>>> is all the hardware is ok >>>>>>>> News? No, that isn't news. It was already established the hardware >>>>>>>> was >>>>>>>> fine. >>>>>>> >>>>>>> a thousand pardons your worship. I shall rewrite it just for you.. >>>>>>> >>>>>>> "I restored the drive from an image, but since it was several moths >>>>>>> old, I had to do umpteen updates, and some sofware installations. >>>>>>> and as had been previously determined, there are no hardware issues, >>>>>>> fortunately. and may I just take this opportunity to express my >>>>>>> profound gratitude to Geebus for his invaluable contributions in >>>>>>> solving this very difficult and often perplexing issue, and without >>>>>>> whose assistance it may never have been solved" >>>>>>> >>>>>>> better? >>>>>>> >>>>>> >>>>>> looks like I spoke too soon after all. I've been trying to format the >>>>>> drive that the faulty installation was on, but I can't get any >>>>>> computer to see it, either in an external USB case, or installed >>>>>> directly in a PC. seems it must be faulty. but because it can't be >>>>>> seen I can't do any diagnostics on it >>>>>> >>>>> >>>>> Acronis can find it but it can't format it >>>>> >>>> >>>> anyone know how I can test/check this drive? >>>> >>> >>> I was able for format it in a windows 7 machine, but when I put it in >>> the win10 PC I get the error message "mbr error 1". >> >> Which suggests that you arent formatting it properly. >> >> How did you format it ? > > I had created the partition as GPT so I changed it to MBR and now I can > boot. > but how do I format a drive that win10 doesn't see? Using anything else than can see it. > I've had nothing but trouble with windoze10!. life was so much > simpler/easier with XP you just put a drive in and it would find it and > ask you to format it Not always. >>> I'm trying to find how to fix it. if the second drive is not installed >>> the computer will boot fine.
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-30 05:53 +1100 |
| Message-ID | <ecl4deF365mU1@mid.individual.net> |
| In reply to | #57021 |
"felix" <me@nothere.invalid> wrote in message news:eckbpkFrl22U1@mid.individual.net... > On Thursday, 29 Dec 2016 10:34 PM, felix wrote: >> On Thursday, 29 Dec 2016 10:27 PM, felix wrote: >>> On Thursday, 29 Dec 2016 9:15 PM, felix wrote: >>>> On Thursday, 29 Dec 2016 4:52 AM, Je�us wrote: >>>>> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> wrote: >>>>> >>>>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall :( >>>>>>> (from >>>>>>> an image of the drive) >>>>>>> >>>>>> I restored the drive from an image, and since it was several moths >>>>>> old, >>>>>> had to do umpteen updates, and some sofware installations. the good >>>>>> news >>>>>> is all the hardware is ok >>>>> News? No, that isn't news. It was already established the hardware was >>>>> fine. >>>> >>>> a thousand pardons your worship. I shall rewrite it just for you.. >>>> >>>> "I restored the drive from an image, but since it was several moths >>>> old, I had to do umpteen updates, and some sofware installations. and >>>> as had been previously determined, there are no hardware issues, >>>> fortunately. and may I just take this opportunity to express my >>>> profound gratitude to Geebus for his invaluable contributions in >>>> solving this very difficult and often perplexing issue, and without >>>> whose assistance it may never have been solved" >>>> >>>> better? >>>> >>> >>> looks like I spoke too soon after all. I've been trying to format the >>> drive that the faulty installation was on, but I can't get any computer >>> to see it, either in an external USB case, or installed directly in a >>> PC. seems it must be faulty. but because it can't be seen I can't do >>> any diagnostics on it >>> >> >> Acronis can find it but it can't format it >> > > anyone know how I can test/check this drive? Do that with that drive in a different system.
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-30 05:52 +1100 |
| Message-ID | <ecl4bqF35o2U2@mid.individual.net> |
| In reply to | #57019 |
"felix" <me@nothere.invalid> wrote in message news:ecka8mFr9etU1@mid.individual.net... > On Thursday, 29 Dec 2016 9:15 PM, felix wrote: >> On Thursday, 29 Dec 2016 4:52 AM, Je�us wrote: >>> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> wrote: >>> >>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall :( (from >>>>> an image of the drive) >>>>> >>>> I restored the drive from an image, and since it was several moths old, >>>> had to do umpteen updates, and some sofware installations. the good >>>> news >>>> is all the hardware is ok >>> News? No, that isn't news. It was already established the hardware was >>> fine. >> >> a thousand pardons your worship. I shall rewrite it just for you.. >> >> "I restored the drive from an image, but since it was several moths old, >> I had to do umpteen updates, and some sofware installations. and as had >> been previously determined, there are no hardware issues, fortunately. >> and may I just take this opportunity to express my profound gratitude to >> Geebus for his invaluable contributions in solving this very difficult >> and often perplexing issue, and without whose assistance it may never >> have been solved" >> >> better? >> > > looks like I spoke too soon after all. I've been trying to format the > drive that the faulty installation was on, but I can't get any computer to > see it, either in an external USB case, or installed directly in a PC. > seems it must be faulty. but because it can't be seen I can't do any > diagnostics on it You previously said that it could be seen fine on a different system and since you can see it using a linux live CD on that system, you must be doing something wrong.
[toc] | [prev] | [next] | [standalone]
| From | Jeßus <j@j.org> |
|---|---|
| Date | 2016-12-30 11:43 +1100 |
| Message-ID | <u9bb6c56lmr9442at279u337kvc8t59ev6@j.net> |
| In reply to | #57017 |
On Thu, 29 Dec 2016 21:15:34 +1100, felix <me@nothere.invalid> wrote: >On Thursday, 29 Dec 2016 4:52 AM, Je?us wrote: >> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> wrote: >> >>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall :( (from >>>> an image of the drive) >>>> >>> I restored the drive from an image, and since it was several moths old, >>> had to do umpteen updates, and some sofware installations. the good news >>> is all the hardware is ok >> News? No, that isn't news. It was already established the hardware was >> fine. > >a thousand pardons your worship. I shall rewrite it just for you.. > >"I restored the drive from an image, but since it was several moths old, I had to do umpteen updates, and some sofware installations. and as had been previously determined, there are no hardware issues, fortunately. and may I just take this opportunity to express my profound gratitude to Geebus for his invaluable contributions in solving this very difficult and often perplexing issue, and without whose assistance it may never have been solved" > >better? A little.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-30 13:25 +1100 |
| Message-ID | <ecluslF9922U2@mid.individual.net> |
| In reply to | #57035 |
On Friday, 30 Dec 2016 11:43 AM, Je�us wrote: > On Thu, 29 Dec 2016 21:15:34 +1100, felix <me@nothere.invalid> wrote: > >> On Thursday, 29 Dec 2016 4:52 AM, Je?us wrote: >>> On Wed, 28 Dec 2016 20:35:20 +1100, felix <me@nothere.invalid> wrote: >>> >>>> On Wednesday, 21 Dec 2016 6:20 PM, felix wrote: >>>>> Stupid windows 10 has spat it's dummy. I'll have to reinstall :( (from >>>>> an image of the drive) >>>>> >>>> I restored the drive from an image, and since it was several moths old, >>>> had to do umpteen updates, and some sofware installations. the good news >>>> is all the hardware is ok >>> News? No, that isn't news. It was already established the hardware was >>> fine. >> a thousand pardons your worship. I shall rewrite it just for you.. >> >> "I restored the drive from an image, but since it was several moths old, I had to do umpteen updates, and some sofware installations. and as had been previously determined, there are no hardware issues, fortunately. and may I just take this opportunity to express my profound gratitude to Geebus for his invaluable contributions in solving this very difficult and often perplexing issue, and without whose assistance it may never have been solved" >> >> better? > A little. Sheesh! ya don't want much, do ya.. -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | Grumpy Tech <grumpytech07@gmail.com> |
|---|---|
| Date | 2016-12-30 14:15 +1000 |
| Message-ID | <o44n08$p55$2@gioia.aioe.org> |
| In reply to | #57035 |
On 30/12/2016 10:43 AM, j@j.org wrote: > On Thu, 29 Dec 2016 21:15:34 +1100, felix <me@nothere.invalid> >>>> I restored the drive from an image, and since it was several >>>> moths old, had to do umpteen updates, and some sofware >>>> installations. the good news is all the hardware is ok >>> News? No, that isn't news. It was already established the >>> hardware was fine. >> >> a thousand pardons your worship. I shall rewrite it just for you.. >> >> "I restored the drive from an image, but since it was several moths >> old, I had to do umpteen updates, and some sofware installations. >> and as had been previously determined, there are no hardware >> issues, fortunately. and may I just take this opportunity to >> express my profound gratitude to Geebus for his invaluable >> contributions in solving this very difficult and often perplexing >> issue, and without whose assistance it may never have been solved" >> >> better? > > A little. > What no thanks for my and other peoples efforts to help you, you ungrateful sod.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-30 15:40 +1100 |
| Message-ID | <ecm6qiFap4pU8@mid.individual.net> |
| In reply to | #57046 |
On Friday, 30 Dec 2016 3:15 PM, Grumpy Tech wrote: > On 30/12/2016 10:43 AM, j@j.org wrote: >> On Thu, 29 Dec 2016 21:15:34 +1100, felix <me@nothere.invalid> > >>>>> I restored the drive from an image, and since it was several >>>>> moths old, had to do umpteen updates, and some sofware >>>>> installations. the good news is all the hardware is ok >>>> News? No, that isn't news. It was already established the >>>> hardware was fine. >>> >>> a thousand pardons your worship. I shall rewrite it just for you.. >>> >>> "I restored the drive from an image, but since it was several moths >>> old, I had to do umpteen updates, and some sofware installations. >>> and as had been previously determined, there are no hardware >>> issues, fortunately. and may I just take this opportunity to >>> express my profound gratitude to Geebus for his invaluable >>> contributions in solving this very difficult and often perplexing >>> issue, and without whose assistance it may never have been solved" >>> >>> better? >> >> A little. >> > What no thanks for my and other peoples efforts to help you, you > ungrateful sod. Oh, how could I have been so remiss!! a thousand and one pardons, your honour. -- I plan on living forever. So far so good!
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | aus.computers
csiph-web