|
ENGLISH VERSION |
|
 |
| Links | | | Forum | | | Kommentare | | | News melden |
|
| Chat | | | Umfragen | | | Newsticker | | | Archiv |
|
| amiga-news.de Forum > Suche | [ - Suche - Neue Beiträge - Registrieren - Login - ] |
|
||||||
|
Markus_Bieler
Nutzer
22.01.2003, 22:12 Uhr [ - Direktlink - ] |
Thema: Wer hat lust meine HP zu testen?
Brett: Amiga, AmigaOS 4 Geht jetzt auch mit IB und AWeb. Wird deine Seite irgendwo noch als Spiegel abgeölegt, könnte sein dass dann 24 std. abzuwarten sind. Markus |
|||||
|
Markus_Bieler
Nutzer
21.01.2003, 23:58 Uhr [ - Direktlink - ] |
Thema: Wer hat lust meine HP zu testen?
Brett: Amiga, AmigaOS 4 Jetzt hab ichs mal mit dem PC und IE versucht, und lande auf der neuen Seite von Dir (ohne Icons auf der linken Seite) Wieder den Amiga benutzt, den cache gelöscht (frisch formatiert) und den Proxy-Server ausgeschaltet und ich lande trotdem auf der Seite mit dem Counter-Fehler. Was denn??? Markus |
|||||
|
Markus_Bieler
Nutzer
21.01.2003, 22:43 Uhr [ - Direktlink - ] |
Thema: Wer hat lust meine HP zu testen?
Brett: Amiga, AmigaOS 4 Die Seite funktiniert mit AWEB II V3.4. Der Counter existiert aber jetzt immernoch und gibt eine Fehlermeldung raus. (Internal Server Error, melden sie sich bei info@gratiscounter.de). Markus |
|||||
|
Markus_Bieler
Nutzer
12.01.2003, 23:35 Uhr [ - Direktlink - ] |
Thema: Maurice Gibb gestorben (Bee Gees)
Brett: Get a Life Florida / USA Gestern mit Herzatacke ins Spital eingeliefert worden und heute bei einer Notopperation gestorben. Markus |
|||||
|
Markus_Bieler
Nutzer
07.01.2003, 00:27 Uhr [ - Direktlink - ] |
Thema: Amiga-PC Netzwerk Fehler
Brett: Amiga, AmigaOS 4 Das Netz läuft. Ich hab alles, was mit VPN zutun hatte, gelöscht (aufs Risiko hin, dass W98 neu installiert weren müsste) und siehe da, nach einem restart erschien der A4000T im Netzwerk. Markus |
|||||
|
Markus_Bieler
Nutzer
31.12.2002, 23:20 Uhr [ - Direktlink - ] |
Thema: Amiga-PC Netzwerk Fehler
Brett: Amiga, AmigaOS 4 Mein samba Einstellungen: # Samba config file created using SWAT # from a4000t (192.168.0.3) # Date: 2002/12/31 22:28:16 # Global parameters [global] workgroup = VENCEREMOS netbios name = A4000T server string = A4000T Server interfaces = 192.168.0.3/24 security = SHARE log file = /samba/log/log.%m max log size = 50 announce as = win95 socket options = load printers = No os level = 0 dns proxy = No remote announce = 192.168.0.255/pckruecke guest account = pcguest [homes] comment = Home Directories writeable = Yes guest ok = Yes browseable = No [printers] comment = All Printers path = /usr/spool/samba printable = Yes [ALL] comment = A4000T path = /sys writeable = Yes guest ok = Yes Ich habe interfaces schon geändert auf /24, da die SWAT anleitung noch von Samba 2.0.3 ausging, ich aber 2.0.7 habe. Beim PC (win98) ist meines erachtens auch alles richtig gesetzt. Der router (192.168.0.1) und der A2000 (192.168.0.4) sind noch nicht am HUB angeschlossen. Stören somit noch nicht. Ich versuchs morgen mal mit dem a2000 <-> a4000t |
|||||
|
Markus_Bieler
Nutzer
30.12.2002, 23:33 Uhr [ - Direktlink - ] |
Thema: Amiga-PC Netzwerk Fehler
Brett: Amiga, AmigaOS 4 Sorry das ich mich erst jetzt wieder melde. Der Amiga hat IP 192.168.0.3 Der PC hat IP 192.168.0.2 (Der ADSL-Router wird haben 192.168.0.1) (Der zweite Amiga wird haben 192.168.0.4) Ich will aber zuerst das Netz zwischen dem A4000T + dem PC zum laufen bringen. Ein ping vom pc aus ergab keine Fehler (0% Verlust) bei vier gesendten und empfangen Packets. Die Antwortzeit lag im Schnitt bei 2ms Kanns sein, das port 139 beim PC irgednwie gesperrt ist? Jetzt erhalkte ich die Meldung "error connecting to 192.168.0.2:139 (Connection reset by peer) Connection to 192.168.0.2 failed" Markus |
|||||
|
Markus_Bieler
Nutzer
30.12.2002, 00:32 Uhr [ - Direktlink - ] |
Thema: Hilfe mit Picasso II
Brett: Amiga, AmigaOS 4 1. Kabel überprüfen 2. wird die picassoII heiss oder tritt der Fehler gleich beim aufstarten schon auf? 3. Monitordaten korrekt eingegeben? 4. Picasso mal in einem anderen Zorroslot versuchen. Ich hoffe das hilft weiter. Markus |
|||||
|
Markus_Bieler
Nutzer
30.12.2002, 00:19 Uhr [ - Direktlink - ] |
Thema: Amiga-PC Netzwerk Fehler
Brett: Amiga, AmigaOS 4 Woran kanns liegen? anpingen geht ja. Amiga mit ariadne, PC mit 3Com Etherlink XL PCI 3C900-COMBO Amiga 192.168.0.3, pc 192.168.0.2, Neuer Shell-Prozeß 6 6.Workbench:> cd miami: 6.Workbench:Internet/Miami> miamiping 192.168.0.2 PING 192.168.0.2 (192.168.0.2): 56 data bytes 64 bytes from 192.168.0.2: icmp_seq=0 ttl=128 time=3.717 ms 64 bytes from 192.168.0.2: icmp_seq=1 ttl=128 time=2.168 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=128 time=2.127 ms 64 bytes from 192.168.0.2: icmp_seq=3 ttl=128 time=2.042 ms 64 bytes from 192.168.0.2: icmp_seq=4 ttl=128 time=2.083 ms 64 bytes from 192.168.0.2: icmp_seq=5 ttl=128 time=2.063 ms 64 bytes from 192.168.0.2: icmp_seq=6 ttl=128 time=2.07 ms 64 bytes from 192.168.0.2: icmp_seq=7 ttl=128 time=2.077 ms 64 bytes from 192.168.0.2: icmp_seq=8 ttl=128 time=1.983 ms 64 bytes from 192.168.0.2: icmp_seq=9 ttl=128 time=2.027 ms 64 bytes from 192.168.0.2: icmp_seq=10 ttl=128 time=2.035 ms 64 bytes from 192.168.0.2: icmp_seq=11 ttl=128 time=2.011 ms 64 bytes from 192.168.0.2: icmp_seq=12 ttl=128 time=2.025 ms 64 bytes from 192.168.0.2: icmp_seq=13 ttl=128 time=2.018 ms 64 bytes from 192.168.0.2: icmp_seq=14 ttl=128 time=2.159 ms 64 bytes from 192.168.0.2: icmp_seq=15 ttl=128 time=2.046 ms 64 bytes from 192.168.0.2: icmp_seq=16 ttl=128 time=2.053 ms 64 bytes from 192.168.0.2: icmp_seq=17 ttl=128 time=2.065 ms 64 bytes from 192.168.0.2: icmp_seq=18 ttl=128 time=2.179 ms --- 192.168.0.2 ping statistics --- 19 packets transmitted, 19 packets received, 0% packet loss round-trip min/avg/max = 1.983/2.155/3.717 ms 6.Workbench:Internet/Miami> miamiping 192.168.0.3 PING 192.168.0.3 (192.168.0.3): 56 data bytes 64 bytes from 192.168.0.3: icmp_seq=0 ttl=255 time=0.978 ms 64 bytes from 192.168.0.3: icmp_seq=1 ttl=255 time=0.793 ms 64 bytes from 192.168.0.3: icmp_seq=2 ttl=255 time=0.804 ms 64 bytes from 192.168.0.3: icmp_seq=3 ttl=255 time=0.814 ms 64 bytes from 192.168.0.3: icmp_seq=4 ttl=255 time=0.811 ms 64 bytes from 192.168.0.3: icmp_seq=5 ttl=255 time=0.819 ms --- 192.168.0.3 ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 0.793/0.836/0.978 ms 6.Workbench:Internet/Miami> samba:bin 6.WORK:samba/bin> smbclient -L pckruecke added interface ip=192.168.0.3 bcast=192.168.0.255 nmask=255.255.255.0 Failed to set socket option TCP_NODELAY (Error Connection reset by peer) write_socket_data: write failure. Error = Broken pipe write_socket: Error writing 76 bytes to socket 3: ERRNO = Broken pipe error connecting to 192.168.0.2:139 (Connection reset by peer) smbclient -L pckruecke cli_establish_connection: failed to connect to A4000T<00> (192.168.0.2) Error writing 76 bytes to client. -1. Exiting 6.WORK:samba/bin> smbclient -L pckruecke added interface ip=192.168.0.3 bcast=192.168.0.255 nmask=255.255.255.0 Failed to set socket option TCP_NODELAY (Error Connection reset by peer) write_socket_data: write failure. Error = Broken pipe write_socket: Error writing 76 bytes to socket 3: ERRNO = Broken pipe Failed to set socket option TCP_NODELAY (Error Connection reset by peer) write_socket_data: write failure. Error = Broken pipe write_socket: Error writing 76 bytes to socket 4: ERRNO = Broken pipe error connecting to 192.168.0.2:139 (Connection reset by peer) cli_establish_connection: failed to connect to A4000T<00> (192.168.0.2) Error writing 76 bytes to client. -1. Exiting 6.WORK:samba/bin> [ Dieser Beitrag wurde von Markus_Bieler am 30.12.2002 editiert. ] |
|||||
|
Markus_Bieler
Nutzer
22.12.2002, 02:41 Uhr [ - Direktlink - ] |
Thema: Drucker (HPIIIp) spinnt
Brett: Amiga, AmigaOS 4 Welches Betriebsystem hast du installiert? Hast TurboPrint installiert? falscher Druckertreiber? Markus |
|||||
|
Markus_Bieler
Nutzer
22.12.2002, 02:36 Uhr [ - Direktlink - ] |
Thema: OS3.9 und BB2
Brett: Amiga, AmigaOS 4 Ich hatte das gleiche Problem. Du musst nur Turboprint nicht mehr resetfest machen. TP patched die exec.library und beim nochmaligen Start (warmboot) meldet setpatch dann einen checksumfehler in der exec.library und diverse programme funktionieren nicht mehr. Mein System A4000T / PicassoIV / Ariadne / Multiface / OS3.9 + BB2 + TP7.06 Ein Umstieg auf Studio druckertreiber ist vielleicht auch empfehlendswert. Markus |
|||||
|
Markus_Bieler
Nutzer
08.12.2002, 02:18 Uhr [ - Direktlink - ] |
Thema: Der Bildschirm bleibt schwarz...
Brett: Amiga, AmigaOS 4 Sind die neusten Graphukkartentreiber installiert? Ich hab mal was von Problemen mit CGX und OS3.9 gehört. Markus |
|||||
|
Markus_Bieler
Nutzer
08.12.2002, 02:06 Uhr [ - Direktlink - ] |
Thema: Forum Amiga unterteilen
Brett: Forum und Interna Erfasst. Ich bins leid aus vielen Themen die relevanten herauszufiltern. Eine Splittung käme mir entgegen :-) Markus |
|||||
|
Markus_Bieler
Nutzer
07.12.2002, 03:35 Uhr [ - Direktlink - ] |
Thema: Nec CDR-210 SCSI1 2x und Oktagon2008
Brett: Amiga, AmigaOS 4 Natürlich meinte ich den RDB von der Platte, die wird ja auch als erstes gescannt. Das eine normale CD keinen RDB hat weiss ich auch. Ich hab mal das Archiv runtergeladen, werds morgen versuchen. Danke für die Hilfen :-) Markus [ Dieser Beitrag wurde von Markus_Bieler am 07.12.2002 editiert. ] |
|||||
|
Markus_Bieler
Nutzer
07.12.2002, 00:30 Uhr [ - Direktlink - ] |
Thema: Forum Amiga unterteilen
Brett: Forum und Interna Hi alle, Könnte man nicht das Forum amiga unterteilen in Harware/Software Probleme Und BlaBla (Morph gegen OS4.0) MfG Markus |
|||||
|
Markus_Bieler
Nutzer
07.12.2002, 00:22 Uhr [ - Direktlink - ] |
Thema: Nec CDR-210 SCSI1 2x und Oktagon2008
Brett: Amiga, AmigaOS 4 Wollte grad meine alten A2000 wiederbeleben, und ihm gleichzeitig ein CD-laufwerk spndeieren. Der A2000 löuft tadellos, bis auf das CD Laufwerk. Der SCSI-Bus bleibt beim CD-ROM höngen. Ich vermute weil dieses Laufwerk kein Parity versteht. Wie schalte ich beim Oktagon2008 Parity aus? Oder kann mans Softwaremässig im RDB tun? Markus :-( |
|||||
|
Markus_Bieler
Nutzer
01.12.2002, 22:30 Uhr [ - Direktlink - ] |
Thema: MC 68010
Brett: Amiga, AmigaOS 4 AMIGA (tm) TECHNICAL NOTE 29-Mar-86 Upgrading an AMIGA A1000 with a Motorola MC68010L8 by Thad Floryan For quite awhile now, I've been experimenting using an MC68010L8 in place of the MC68000 in my Amiga. The benefits of the MC68010 are great, but several "problems" with the MC68010 upgrade have held me back from recommending this simple enhancement to everyone. Now, the final quirk has been solved, and I am recommending the upgrade to everyone! This document has several parts, ALL of which must be read and understood by anyone wishing to perform the upgrade or contract for someone to perform the upgrade for you. Additionally, there are several files which accompany this technical note: CHOP.BAS CHOP.C DeciGEL DeciGEL.asm DeciGEL.make The several parts of this document are: I. The MC68010 hardware upgrade II. The MC68010 software upgrade III. Copy of Motorola's MC68000 Micro Minutes MM-444-02, entitled "Advantages of Upgrading an MC68000 to an MC68010". IV. Side notes V. Trademark notices ---------------------------------------------------------------------- ---- ** DISCLAIMER ** The modification and details described in this technical note are provided "as is", without warranty of any kind, either expressed or implied, inclu- ding, but not limited to, the implied warranties of fitness for a particu- lar purpose. The entire risk as to the results and performance of the mo- dification is assumed by you. In no event will I, Thaddeus P. Floryan Jr, be liable for direct, indirect, incidental or consequential damages resul- ting from the use or application of this information. ---------------------------------------------------------------------- ---- I. The MC68010 hardware upgrade The MC68010 is pin-for-pin compatible with the MC68000 installed in all Amiga Model A1000 PCs. The hardware upgrade consists of replacing the MC68000 with the MC68010. ** CAUTION ** The internals of the Amiga are sensitive to static and are fragile; working on a computer is not like working on your car. Also, opening the Amiga will void your warranty. It may be worth your peace of mind to contract an experienced technician for the hardware part of this upgrade. Common sense and a good mechanical aptitude are essential. Take your time and do not rush; restrain your excitement for later, after the MC68010 is installed. To open the Amiga, the five screws on the underside of the case must be removed. Releasing the cover can be tricky; examine the left side of the case near the power switch (front side corner) and also 10 inches further back along the seam and note the tabs: push in until they separate, then lift the cover up toward the right side of the case and release the tabs there. The metal RFI shield covers the entire PC board and must be removed to gain access to the MC68000. Remove all the screws along its edge, and also straighten out the tabs which protrude upwards through the shield, then lift and remove the shield; be sure to note where each screw is supposed to be located as there are several types of screws. The disk drive must also be removed since it sits over one edge of the MC68000. First unplug the two cables (power and signal) after noting the orientation so that they can be replaced correctly later. Now remove all screws fastening the disk drive and lift it up and out: NOTE that the wires to the LED are still fastened; these do not need to be removed if you turn the drive upside down and lay it on a thick book alongside the right side of the Amiga case. Pry the MC68000 out and replace it with a MC68010L8. Reverse all the previous steps to reassemble the Amiga; the tabs which protrude through the RFI shield need not be twisted back into place. Reconnect all the cables to the Amiga. Powerup the Amiga and boot with your usual Kickstart and Workbench disks. Verify that the system appears to be working as normal. Now, either from the Workbench or CLI, startup the CALCULATOR tool, and perform the operation: " 9 * 3 = ". There should be a software failure; this indicates the MC68010 is running correctly because the CALCULATOR supplied with V1.1 uses a "MOVE SR,ea" instruction which is invalid in user-mode with a MC68010. Reboot the Workbench and proceed now to section II, software upgrade. If you do not experience the symptoms as described above, there may be several reasons: 1. you re-installed the MC68000 instead of the MC68010, 2. the MC68010 is "dead", or 3. something else inside the Amiga has been damaged. At this point, you are on your own. My advice is to re-install the MC68000 and verify that your system works again; if it does, then your MC68010 chip may be bad. If your system still does not operate with the MC68000 back in, then you gotta heap of trouble. Re-read the DISCLAIMER above, and seek competent technical service. ---------------------------------------------------------------------- ----- II. The MC68010 software upgrade Beginning with V1.1 of Kickstart and Workbench, Commodore-Amiga "officially" supports operation of the MC68000, MC68010 and MC68020 CPU chips in the Amiga Model A1000 per: "With the exception of the Calculator, software in the 1.1 release is compatible with the 68010 and 68020 processors. Application programmers wishing to take advantage of such products should be sure to use the Exec GetCC() function to get the processor condi- tion codes. (GetCC() handles the differences between the proces- sors such as the fact that "MOVE SR," is an invalid user mode operation in the 68010 and 68020.) In addition, programmers should be sure to NOT use the upper 8 bits of a pointer for storing unrelated information, since the 68020 uses all 32 bits for addressing. = For those doing systems work, Exec maintains flags in the AttnFlags field of ExecBase which describe the type of processor in your machine. Exec's coldstart procedure will update certain library entry vectors as neccessry to maintain compatibility. If you write code that uses the Supervisor() function, keep in mind that your stack frame is processor dependent. Use the SuperState() function for processor independent supervisor mode entry. = V1.1 ROMWack will correctly display information for 68010/68020 address and bus errors. " OK, as you can see, simply by having installed the MC68010, you will be able to use most Amiga system software without any problems. But, the CALCULATOR and other programs loaded with libraries using "MOVE SR,ea" will cause your system to go to lunch with the Guru. This is the reason I haven't encouraged people to upgrade their Amigas until now; only a knowledgeable person would have been able to either live with the occasional problem, or rebuild the software to not use the "MOVE SR,ea" instructions. So what happened all of a sudden to change my mind? Simply that one clever person has developed a short and elegant software solution that prevents the "MOVE SR,ea" instructions from crashing your system. "How," you may ask, "is this done?". It's done by inserting a "wedge" that intercepts instruction privilege violations, examining the offending instruction for the presence of "MOVE SR,ea" and, if found, replacing that instruction in memory with a "MOVE CCR,ea" and resuming at the point of failure. Since the only valid use of the system status register (SR) in a user-mode program would be to get the condition codes, the assumption made by the "wedge" is a reasonable one. And, it works! I've been testing ALL the cases that failed previously with the MC68010 in the Amiga and they ALL perform correctly now. I have included 5 programs with this technical note: CHOP.BAS public domain, author: Anonymous CHOP.C public domain, author: J S Plegge DeciGEL public domain, author: Scott Turner DeciGEL.asm public domain, author: Scott Turner DeciGEL.make public domain, author: Scott Turner DeciGEL is the "wedge" program that needs to be placed in the "c" directory of your workbench disk; DeciGEL.asm is the Assembler source file, and the DeciGEL.make is an EXECUTE file that will recreate DeciGEL from DeciGEL.asm. If you don't have the Amiga Assembler, you can simply download DeciGEL and use it immediately. It is best to include a line in "s/startup-sequence" on your Workbench disk that will call DeciGEL. For example: echo "Workbench disk. Release 1.1" echo " " echo "Use Preferences tool to set date" echo " " DeciGEL . . The CHOP.BAS and CHOP.C programs are used if you download DeciGEL and use the progam directly, without rebuilding. The CHOP programs must be used to make SURE the DeciGEL program is exactly 168 bytes long. You can determine the size of DeciGEL on your system by using the CLI's LIST program. If the size is greater than 168 bytes, CHOP will allow you to truncate (or chop) the file to 168 bytes. CHOP.BAS operates with ABasiC (not AmigaBASIC), and CHOP.C is the source of a "C" program; use either one as appropriate for your needs. With the MC68010 installed and DeciGEL "wedged", your Amiga should operate anywheres from 4% to 50% faster depending on what you're doing. Note that the "Boing!" demo will not be faster since its timing is synchronized to the vertical framing of the monitor's clocking which is FIXED per NTSC TV standards! The biggest benefits of the MC68010 upgrade will occur with heavy number-crunching applications, such as spread sheets and Mandelbrot picture generations. Enjoy! ---------------------------------------------------------------------- ---- III. M68000 MICRO MINUTES (c) Motorola MM-444-02 Advantages of Upgrading an MC68000 to an MC68010 There are several ways a system's performance can be upgraded. Some are software related, such as lowering operating system overhead, obtaining better quality language compilers, wisely designing application programs, and coding applications more efficiently. Others are hardware related, such as adding memory, improving I/O channel data rates, increasing mass storage speed and capacity, reducing memory access times, and upgrading the system processor's clock frequency. When considering an MC68000 system upgrade to higher performance, the obvious thought is to redesign for a higher frequency MC68000. For example, a current MC68000 system running at 10 MHz could be redesigned to run at 12.5 MHz, thereby increasing system throughput by 25%. The "obvious solu- tion", however, is not necessarily the most appropriate or cost-effective once several factors are taken into consideration and alternative solutions examined. The speed-up of a system clock will not be effective unless the system's memory access time is also improved. The performance of the MC68000 is strictly limited by the bus speed, and if no improvement in memory speeds are available, then an increase in system clock speed will lead to negligible improvement in the overall result. A 10 MHz processor running with no "wait states" utilizes a 400 nS bus cycle (4 clocks x 100 nS/clock). This same bus cycle timing, however, leads to a wait cycle on a 12.5 MHz processor (4 clocks x 80 nS/clock + 80 nS of idle time). Thus, the bus performance is exactly the same, but the faster processor is idled for one complete clock cycle. Since a decrease in the bus cycle time provides a directly proportional increase in processor throughput (until, of course, the memory cycle becomes faster than the fastest processor bus cycle), the 12.5 MHz processor has no relative performance advantage over the 10 MHz system. The bottom line, then, is that in order to be effective, a higher speed processor must run with fewer or the same number of "wait states". This normally requires a redesign of the memory subsystem to improve the memory access time. Referring to the MC68000 Data Manual (ADI-814-R4), the memory access re- quirements for the various speed processors can be examined. The effective memory access time (Taccs) of the MC68000 to a memory array (from assertion of Address Strobe [-AS] to data valid) is: Taccs = Tch + 2Tcyc - Tchs1 - Tdic1 + (n * Tcyc) where: Tch is the clock high time (system dependent) Tcyc is the clock period of the processor clock Tchs1 is the delay time from the rising edge of the clock to the assertion of address strobe Tdic1 is the data input set-up time prior to the falling edge of the clock n is the number of wait cycles in the system Assuming a symmetric clock (50% duty cycle), the memory speed required for a no "wait-state" bus cycle for a 19 Mhz MC68000 processor is 185 nS (50 + 200 - 55 -10 + 0). This bus speed can be easily realized with readily available 150 nS dynamic RAMs and careful system design. However, with the same assumptions, the memory speed required for a no "wait-state" bus cycle on a 12.5 Mhz processor is reduced to 135 nS (40 + 160 - 55 - 10 + 0) which presents an obvious problem to the cost-conscious system designer -- lack of cost-effective, large capacity 100 nS RAMs! Memory access times are not the only difficulty encountered with the faster clock speeds. In a similar vein, the design of an efficient 12.5 MHz system is more difficult than that of a 10 MHz system, since more careful attention must be paid to the physical design of the board in order to account for the higher frequency signals present, and the increased sensitivity to transient phenomena. A "painless" alternative means to EFFECTIVELY increase system performance is to upgrade to the MC68010 processor. The MC68010 at equal clock fre- quencies will run from 8% to 50% faster than an MC68000 without any user code changes. The speed-ups are due to several microcode enhancements: many 32-bit operations, conditional branches, multiply, divide and other miscellaneous instructions run faster. Systems which use memory management can have dramatic improvements with slight operating system changes utilizing a few new MC68010 instructions such as "Move to/from Address Space" (MOVES). Systems may see a significant improvement if they heavily utilize multiply, divide and looping operations. Loops run from 23% to 80% faster once the microcode sets up the automatic "loop mode". Such loops benefit particular functions such as block moves, character matching and general string manipulation operations, and multiple-precision binary and packed BCD arithmetic. The new MC68010 multiply is 14 clocks faster, and the divide is 32 clocks faster than the MC68000. Programs utilizing (or with the potential of utilizing) such operations can obtain an increase in perfor- mance easily exceeding 10%. An additional "plus" of the MC68010 is the provision of a clear path for the upgrade of current operating systems to full virtual operating systems utilizing the sophisticated virtual memory processing capabilities of the MC68010 (which is the same virtual environment offered by the 32-bit MC68020). Since the MC68010 is pin-for-pin compatible with the MC68000, *NO* hardware redesign is necessary. Only very minor software changes may have to be made depending on operating system conventions. The MC68010 differs from the MC68000 in that: 1) a generic "vector word" has been added to the MC68010 stack frame; and 2) the MC68000's "MOVE SR,ea" has been made a privileged operation. Easy software solutions for these two minor differences are: 1) any routines which build exception stacks (e.g. those which dispatch a routine via an RTE instruction) are modified to account for the four word stack frame (the MC68000 uses a three word stack frame); and 2) an exception handler is added to provide for privilege violations generated by the execution of the "MOVE SR,ea" instructions in the USER state (local Motorola representatives can supply a debugged handler to suit the requirements of any OS). Major operating systems have been ported from the MC68000 to the MC68010 in less than a single day, reflecting the trivial changes required in the super- visory level code. The bottom line is, by upgrading an MC68000 system to an MC68010 system, an increase in system performance is obtained which is equal to that which a system redesign from 10 MHz to 12.5 MHz would provide, but with signifi- cantly less design cost and effort. The "speed-only" upgrade could only achieve, at best, a 25% system improvement, and only if the system memory access time is significantly improved. The MC68010 upgrade offers from 8% to 50% improvement. Note that the speed gained by changing to the MC68010 is achieved with NO change in memory speeds, NO board redesign, and NO higher speed parts installed in the system as would be required to upgrade a system to a 12.5 MHz part. ---------------------------------------------------------------------- ----- SIDE NOTES: (1) Commodore-Amiga has provided for the four word stack frame in Exec. (2) the DeciGEL program is the privilege violation exception handler. ---------------------------------------------------------------------- ----- Amiga is a registered trademark of Commodore Business Machines, Inc. |
|||||
|
Markus_Bieler
Nutzer
29.11.2002, 03:11 Uhr [ - Direktlink - ] |
Thema: MC 68010
Brett: Amiga, AmigaOS 4 Der Gewinn den man erzielt mit einem 68010 ist so marginal, dass der verlust an Software, die nicht mehr läuft schmerzlicher ist. Der 68010 hat ein paar wenige Befehle nicht mehr, und grad Spiele und "Sceneprodukte" brauchen diese Befehle. Eine Turbokarte bringt da sicher mehr (und ist in Notfall abschaltbar/entfernbar). Markus |
|||||
|
Markus_Bieler
Nutzer
27.11.2002, 00:38 Uhr [ - Direktlink - ] |
Thema: AMIGA 500 rev.6a 1mb chipram
Brett: Amiga, AmigaOS 4 Das geht nicht. Meines wissens kan man entweder das RAM auf dem motherboard auflöten, dann verliert man eine 512KB-sloterweiterung. oder man erweitert mit der Slotkarte, da muss man nur auf dem Motherboard zwei verbindungen trenne und eine Lötbrücke setzen. (So verliert man auch die UHR auf der 512KB.erweiterung nicht.) |
|||||
|
Markus_Bieler
Nutzer
14.11.2002, 22:11 Uhr [ - Direktlink - ] |
Thema: IBrowseabstürze auf amiga-news.de?
Brett: Amiga, AmigaOS 4 Den Cache von Zeit zu Zeit löschen. Ich hab dafür eine eigene Partition, die einfach frisch formatiert wird. Der nachteil, es gehen auch die Cookies verloren. Man könnte sie auch vorher rauskopiere, aber das ist mir zu mühsam. IBrowse vermurkst sich wenn der Cache zuviele Einträge hat. (Achja IB2.2 + OS3.9.2 auf A4000T/PPC/PIV) Markus |
|||||
|
Markus_Bieler
Nutzer
03.11.2002, 22:13 Uhr [ - Direktlink - ] |
Thema: kann mir denn niemand helfen???
Brett: Amiga, AmigaOS 4 Versuch mal den Eintrag: scsi_device_name=elsat.device Markus |
|||||
|
Markus_Bieler
Nutzer
03.11.2002, 21:02 Uhr [ - Direktlink - ] |
Thema: kann mir denn niemand helfen???
Brett: Amiga, AmigaOS 4 - Läuft die HD überhaupt an? - Das CD32 mit einer Erweiterung (ausser dem FMV-Modul) braucht zwingend ein stärkeres Netzteil. - Was steht in der Aneltiung zum Promodul betreffend HD? - Wie gross ist die HD? C= hat mal eine Liste der HDs herausgegeben, die im A1200 gehen. Markus |
|||||
|
Markus_Bieler
Nutzer
25.10.2002, 01:51 Uhr [ - Direktlink - ] |
Thema: Software Tycoon
Brett: Amiga, AmigaOS 4 Ich kenn zwar das Spiel nicht, aber mir stürzt AHI auch des öfteren ab. Egal welche version.  [ Dieser Beitrag wurde von Markus_Bieler am 25.10.2002 editiert. ] |
|||||
|
Markus_Bieler
Nutzer
21.10.2002, 22:42 Uhr [ - Direktlink - ] |
Thema: Idee für Umfrage gesucht
Brett: Forum und Interna Mich würde interssieren wieviele Amigabenutzer noch eine Zorro II oder III Graphikkarte kaufen würden. Ich wäre jedenfalls dabei. Mein A2000 ist nicht so recht zufrieden mit seiner A2410 und hätte gerne nochmals eine PIV oder ähnliches, aber neu und nicht occ. Markus |
|||||
|
Markus_Bieler
Nutzer
21.10.2002, 22:34 Uhr [ - Direktlink - ] |
Thema: Suche Kicro-Professoor...
Brett: Amiga, AmigaOS 4 Mac Laden aufsuchen und nach defekten alten Geräten zum ausschlachten fragen. |
|||||
|
Markus_Bieler
Nutzer
21.10.2002, 22:22 Uhr [ - Direktlink - ] |
Thema: Externe Floppy
Brett: Amiga, AmigaOS 4 Also Leute. :-) Es ist ein Original Amiga 4000 Tower (egal ob von C= oder Amiga technologies) Da ist die Zusazplatine drin, mit dem herausgefühtren SCSI-Anschluss. Und auf deren anderen Seite (schaut richtung Harddiskschächte) sind schon die Lötpunkte vorgeshen für entweder direkt einen Anschluss anzulöten (macht aber keinen Sinn, da in das Gehausehineinschauend. Wer hat das wohl geplant ?) und gleich daneben sind noch Lötpunkte für eben einen Postenstecker. Diesen habe ich bestückt und aus einem alten externen Kabel einen Anschluss hintenhinaus gemacht. Es war somit mal Vorgehsehen für den Tower auch einen externen Anschluss zu bieten, der wurde aber aus Kosten Gründen (IMHO) weggelassen. Wer mit dem Lötkolben gut umghen kann, der weis jetzt wies geht. Ist meines Wissens auch eine Anleitung dazu im Aminet. Markus. (Der mit dem A4KT ) |
|||||
|
Markus_Bieler
Nutzer
13.10.2002, 22:45 Uhr [ - Direktlink - ] |
Thema: Amiga-Daten von PC auf Amiga
Brett: Amiga, AmigaOS 4 Hallo Ralph, Versuchs mal mit messydos. Findest du im aminet. Damit kann man unter Kick 1.3 auch PCdisks (720KB) auf dem amiga lesen. Sonst mit Twinexpress (via Nullmodemkabel) versuchen. Ebenfalls im aminet. Der PC kann ohne spezielle Erweiterungskarte keine Amigadisks lesen und schreiben. MfG Markus |
|||||
|
Markus_Bieler
Nutzer
13.10.2002, 18:33 Uhr [ - Direktlink - ] |
Thema: Brauche PicassoII+ Treiber !
Brett: Amiga, AmigaOS 4 Village-Tronic Treiber Markus:bounce: |
|||||
|
Markus_Bieler
Nutzer
13.10.2002, 17:31 Uhr [ - Direktlink - ] |
Thema: Server Ausfall?
Brett: Forum und Interna Bei uns an der UNI hat die Putzfrau/kolone im Serverraum nichts zu suchen. Da putzt der Master himself und sonst kommt da niemand rein. |
|||||
|
Markus_Bieler
Nutzer
13.10.2002, 17:16 Uhr [ - Direktlink - ] |
Thema: Externe Floppy
Brett: Amiga, AmigaOS 4 Zitat: Meiner auch :-). Die Lötpunkte sind ja so schön da, musste ja nur noch Pfostensteckerleiste drauf. |
|||||
|
||||||
|
|
Impressum |
Datenschutzerklärung |
Netiquette |
Werbung |
Kontakt
Copyright © 1998-2024 by amiga-news.de - alle Rechte vorbehalten. |
|
der hat nämlich keinen externen Floppy anschluss.....