georgebaileyster

A Commodore PET aka Metal Mickey within built in datasette complete with dot matrix printer no less. Ltaer progressed to the CBM Scientific with built in tool chip. Then a NEC APC with duel high density 8" floppy drives and duel prossesor 3D graphics card was running CBM which was far superior to MSDOS and I kept that running until I got an Apricot 486DX2 server. BTW they all still run today.

If you need one now in the UK AOL give them away free when you sign up for their 8mb broadband service....

The usual problem here is the solder points on the monitor plug normaly located under panel at the rear of the keyboard i.e. the panel where your buttons are normally found between the base of the screen and keyboard. This panel is separate from the rest of the and the favorite place being in front of the right hand hinge. It is problem which normally results from leaving the unit in standby or hibernate mode withe lid closed.To keep the things thin they normally make the plug in two sections which results in ultra fine solder joints and the heat generated in standby with the lid closed will weaken the joints until ultimatly one or two give way to a microscopic gap thus no screen display.To correct this, open the screen fully i.e. laid back against the table. Remove the back plate as described above and locate the plug. CAREFULLY remove it. Place some thick card over the screen - the flap from a corrugated box will do just fine - this protect the screen. Place a bulldog clip of appropriate size to hold the top and bottom sections of the plug together and with an extremely fine and low wattage soldering iron, carefully re-seat each joint in turn. As a note, Samsung P4 laptops were the worst offenders for this problem..

Different memory types and speeds should NEVER be mixed on the same board.Even if they do both run your data integrity is at serious risk of corruption.The beeps your hearing are BIOS post codes for which you need the relevent reference chart from BIOS manufacturer. You will need the version and revision numbers also which should be displayed at boot. You must, however lissen carefully as there are some which are very hard to tell apart for instance long and short combinations, pauses etc. If the RIMM was the last thing to be added then by default it should be first thing to be removed.

OK, it had to happen sooner or later i guess, time to shed some light on just how long I've been in the IT / Comms arena.... On these ;bad guys' as you call them was Autocad for instance and the office solution comprise of Wordstar, Dbase and Supercalc which could integrate for the likes of mail merge etc.... These three sat quite happily on the boot disk and you still had plenty of room for data storage..... If you were super rich you also had colour monitor, external hard drive and 3D graphics card... And just so can really call me Grandpa (I am anyway, twice over) this thing you call VoIp was working perfectly well in 1973 on Arpanet with toll quality in 3.5k of bandwidth..... Oh how our siblings just love to re-invent the wheel; What was wrong with the round one anyway???? http://forums.xisto.com/no_longer_exists/404.png

I suppose the main point to your frustrastion is simply MAC OS is, underneath, Linux; it is the ultimate distro on its own so why bother producing one for it?????They do produce open source variants of much of their core parts such as the media server etc. and no doubt the OS as well. It would be worth digging on the website and see what you can find. Its been a few years since I last developed server systems for Linux so can't give you the precise site address, but hey, look on the upside, you may just have as much fun using apple opensource on a pc running a different version of Linux/Unix....

Firstly remember KISS - keep it simple stupid - you don't need anything fancy here and the software is genuinly free. A basic server with redundant storage and power supply i.e. a simply RAID storage system to preserve data and operations should one drive fail and a second power supply for the same reasons.The server should run on Linux - Red Hat basic would more than suffice and is one of the oldest and most trusted distributions - no need for the paid for version either. Run on Ethernet TCP/IP with switches in the main departments and one distributed i.e. one switch to connect the nurses stations. The switches should have an uplink port included - KISS again - The server should be set for DHCP so the clients recieve their IP addresses automatically.The main for you here is to calculate the cable runs which you can only do from a physical survey of the site. ALways remeber that cables should run in straight lines only, not diagonal short cuts, and rememebr to include the distances travelled up and down walls.......The software is also free, either check sourceforge or google for 'free hospital software linux' there are some very good all incompasing packages out there if you do your home work.Your network diagram comes from the above and your site survey.Hope this gets you started.....

What you need to do is try this:-Check the manual for your router (probably in PDF format on the disc supplied)Find the default IP address of the box and the default username and passwordNote these down and in your browser address tab type the IP address example 192.168.0.xLog into the unit and switch off the DHCP server somtimes will be 'automacally assign IP addresses' or variations of that natureIf your printer is not equiped with a network port and needs the USB connection, assign an IP address this port on the switch in line with other computers on your networkSave the changes and log outSwitch the unit off and and on just to make sure it updates itself correctly, then you can assign the printer on your computers to a network printer which (if its behaving itself) windows will be able to locate automatically.Best of luck.

If I understand you correctly, you are trying to prevent stored print jobs from running at later time? The easiest thing in this case is simply ensure the printer swithed off before starting the machines. When all the systems are booted fully wait a couple of minutes and then check the machine as you described in your post and delete all print jobs in the queue.When you have done this, simply switch the printer back on. Should do the trick. The problem is the amount of memory in the printer itself, the jobs won't disappear from the windows side until the printer confirms the job is completed.

Obviously there is no way to be certain, but from experience this issue would propagate from a contractor or technician working at the exchange and not paying attention to detail. You should find out where your exchange is located and go and speak (nicely) to the senior engineer. Ask him to check your line on the switch (physical connection on the exchange equipment).No doubt he will check the computer and it will say all is OK, but if he physically goes to see he will no doubt find the wires are crossed and or hooked together. Thus the computer will always 'think' both lines are OK.Hope this is of some assistance, but without knowing precisely what equipment Telstra use these days its the best start point.