So all we need to do now is get Asus, Gigabyte, MSI, etc to adopt it. :-) Actually, if I have time this weekend, I may throw together a php script on the IAVIT web site to allow us to record this ourselves. I can probably still get the specs for the last PC I built by opening it up and measuring everything. Three problems with this: 1. The mobo is no longer being manufactured so having this info would be of little use. 2. My wife is now using the PC and she would not take kindly to me taking it back even temporarily. 3. I promised a lot of other people a lot of other stuff related to IAVIT. My backlog is huge. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: Thursday, November 01, 2012 12:14 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Protocol for specifying mobo topology in text format (was: newegg's shuttle barebones systems?) Hi, That seems to work for me. Dave On 11/1/12, John G. Heim wrote:

So here's my rough idea for specifying mobo topology in text format.

1. The mobo is oriented according to how it would appear in an ATX tower case. The ports are in the back. The top is the edge toward the top of the case. I don't know about laptop/embedded systems mobos. That will take some work. The "front" of a switch, for example, is difficult to define. But at least its fairly eeasy for regular mobos.

2. Each connector is specified by its nearest distance from any 2 orthoganal edges. It can be distance from back/bottom, back/top, front/bottom, or front/top. The distance from the back is a positive number. The distance from the front is a negative number. Distance from the bottom is positive. Distance from the top is negative.

So for example, most mobos have a PCI slot near the bottom back of the mobo. You could give its location as 1/1.4 cm. That would mean its nearest point is 1 cm from the back and 1.4 cm from the bottom. You could also give it as -15.3/-10.2 cm. That would mean its nearest point is 15.3 cm from the front and 10.2 cm from the top.

Optionally, a manufacturer can give 2 sets of numbers specifying opposite cornders of a connector. 1.0/1.4, -15.3/-10.2 would mean the connector is located in a rectangle with one corner located 1.0 cm from the back and 1.4 cm from the bottom and the opposite corner is located 15.3 cm from the front and 10.2 cm from the top.

3. Pins on a header block are numbered from left to right and top to bottom. A header with 2 rows of 5 pins would be 1,32,3,4,5 on the top row and 6,7,8,9,10 in the second row. This is true regardless of the orientation of the header block. If its 5 rows of 2 columns, the pins would be numbered 1 2, 3 4, 5 6, 7 8, 9 10.

To specify the pins for the connection, you simply give the numbers. For example if the power LED has to be connected to the rightmost pins on a header block containing 2 rows of 5 pins, you'd say the power LED connector is on pins 5 & 10.

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: Thursday, November 01, 2012 11:14 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] newegg's shuttle barebones systems?

Hello,

I wouldn't mind finding the good samaratin how did you do this?

As for a standard protocol I'm all for it, it sounds great!

Thanks. Dave.

...

I hate to always give the same answer to all questions but I have been contemplating starting a project through the International Association of Visually Impaired Technologists (www.iavit.org) to deal with this

On 11/1/12, John G. Heim wrote: problem.

...

I was thinking of trying to develop a protocol for specifying motherboard connections in an accessible format and then getting manufacturers to include it in their docs.

But I think the only other solution is to get sighted assistance. Last time I built a machine, some good Samaritan in England (I'm in Wisconsin) talked me through making the connections. He downloaded the manual and sent me email explaining how to connect everything. That was awesome but it was a slow, difficult process.

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: Thursday, November 01, 2012 9:18 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] newegg's shuttle barebones systems?

Hi,

I can get most of it, but I'd like to get all. The snafus are the CPU, getting it in right, and the leads and specifically the power button.

Thanks. Dave.

On 11/1/12, Scott Granados wrote:

...

Just to add to the noise thread, before I jumped on the Mac band wagon my last few machines were water cooled. I'll admit noise wasn't a concern for me it just happened that water cooling had the benefit of being damn near silent. Mac's interestingly are very quiet but you don't have the learning experience and gain the skills you do by building your own machine.

On Oct 31, 2012, at 3:24 PM, vic.pereira@ssc-spc.gc.ca wrote:

...

On the topic of noise there is always a bit of a trade off. If you want to use smaller boxes with processors that have multiple cores they will run very warmly. The fans will be pushing as much air to cool the system as one in a larger case. Towers tend to be quieter due to the fact they have a lot of vacant space. Low profile systems will be noisier and even rack mounted systems, because the fans need to work hard to keep things cool and sometimes smaller fans need to be used. If these are operating at higher RPMs and have smaller channels to push out that warm air it will make noise.

Vic

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ben Mustill-Rose Sent: Wednesday, October 31, 2012 1:49 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] newegg's shuttle barebones systems?

I agree with John, but to add a couple of points: Shuttles aren't overly small anymore in comparison to what you can build. It's possible in fact probable that you'll be buying shuttle specific parts which will make it harder in the future wen one of them dies.

I treated myself to a new system earlier in October actually and I built it all myself; the only thing I haven't been able to connect is the leds on the front; I'm sure that if I had the inclination I could sit down with my keyring light probe and get it sorted though. Personally I find it a really fun experience.

Cheers, Ben.

...

I have avoided buyng a bare bones system because you can't know how noisy it will be or how hard it will be to work on. When I build a machine, I buy the mainboard, CPU and RAM from newegg and buy a case from a local computer shop where they let me see how easily I can open it up and how loud it is.

Its pretty easy to assemble a PC except for connecting the cables from

On 10/31/12, John G. Heim wrote: the

...

case to the mainboard. Installing CPU, RAM, and hard disk isn't too difficult. Some of the wires from the case to the mainboard plug in only one way. But I usually have to get sighted assistance to connect the LEDs, reset and power buttons, front panel audio, etc. Last time I built a machine, I got a good Samaritan on the web to send me a text description of the specs for connecting those wires. Then I did it myself.

If you don't want to go through all that (and honestly, I wouldn't blame you), maybe buying a barebones system from a local computer shop would be a good compromise.

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: Tuesday, October 30, 2012 7:19 PM To: blind-sysadmins Subject: [Blind-sysadmins] newegg's shuttle barebones systems?

Hello,

Has anyone bought any of these barebones systems from newegg? If so, what did you think pro conn of them?

Thanks. Dave.

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins