Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: technium on April 04, 2006, 02:54:38 PM
-
I brought a 2nd hand amiga tower off ebay awhile ago and it worked when I first tried it and then I changed the screen resolution and restarted and now I get nothing but a white screen with the flat screen monitor connected to one port or "no Signal" if I connect the monitor to the other port.
I know its got one of those scan doubler things but I just cant get any display at all apart from this white screen. Any help?
thanks
Colin
-
Welcome to Amiga.org!
Connect the Scandoubler SVGA port to the TFT for the following... As a fall back, connect the Amiga to a TV
Reset the Amiga, hold down both mouse buttons for up to 30 secs until an Early Startup Menu appears - select boot with no startup-sequence
at the command prompt 1> type:
rename sys:prefs/env-archive/screenmode.prefs sys:prefs/env-archive/screenmode.old
Then reset the Amiga and go into Workbench. Goto prefs drawer and run Screenmode. Select the previous working graphics card screen then test on the TFT to see if working. If OK save the settings.
-
Is the scandoubler the internal type which clips over some of the chips on the motherboard? Or an external one?
Are you using some other form of graphics card aswell (eg a Zorro card, or a pci card?)
Does it still sound like the computer is booting from the hard-drive?
Try connecting the (yellow) composite out to a composite in on your TV (a standard phono--phono lead should do the trick). See if you get a signal from that. If you can boot into workbench on that you can just reset the screenmode to whatever it was before.
-
ok cant even see what a scan doubler is, the two connections for the monitor (pc monitor btw) is one that goes into a 3dfx graphics card - this is the one that displays "no signal" and the other one is a monitor connector which has a ribbon cable which goes onto the motherboard but theres loads of stuff in here, Ive just removed the graphics card, tv card and network card but theres also a Mediator PCI 1200 SX which lays on top of motherboard which all these cards connect into other than that I cant really see what im looking for :(
-
ah ha, now ive got it booting, I removed all the cards and mediator and nothing happened when turned on, so reseated mediator (no cards) and now im into workbench although resolution is pants so how do I change that?
Next is to try installing each card one at a time.
-
ok reseated the cards one at a time and it all works fine, upto the point I installed the 3dfx card so why would that be?
any advice, been ages since I had a miggy and that was a A1200
thanks
-
ok next update, I can get it to power on with the 3dfx card inserted but with the power cable not plugged into it.
Ive also found wbprefs on the workbench to change resolution but it keeps saying to close all windows but none are open apart from the main workbench one, so need some advice on that, also whats a suitable resolution for 15" flat panel pc monitor?
thanks if your still reading.
-
Background (in my limited understanding):
The amiga's native RGB monitor output is at 15.5kHz. PC monitor frequencies are generally somewhere between 30 and 100kHz.
Original amiga monitors accepted video input at the frequeny the amiga produced - 15.5KHz. Later 'multiscan' monitors accepted frequencies between around 15.5 and 50 KHz, allowing both PC and amiga to share the same monitor. Modern PC monitors are generally some range between 30 and 100 kHz, so 'original' amiga screenmodes will not be displayed on them.
The amiga is capable of producing screenmodes at 30khz (-ish), but it takes its toll on processing (and, bizarrely the serial port baud rate).
Step in the scandoubler, stage left: the scandoubler takes the amiga's native 15.5kHz signal and doubles the scanrate to 31kHz with no extra overhead on the amiga's chipset.
You may know all this already, so apologies if you feel patronised.
To change screen settings:
Go into your workbench drive, prefs drawer, double-click screenmode. The graphics card you're using in your mediator is a voodoo (3, 4 or 5 - it makes little difference at this point).
You want to choose one if the screenmodes which start with VOODOO, eg VOODOO:1024x768:32-bit - will give you 32 bit (aka truecolour) 1024x768 resolution through the mediator/voodoo card. I've found 24-bit (aka high colour) works quite a bit faster, and the colour difference is not really noticable.
If you choose a screenmode labelled with just the numbers (eg 640x320) this will display through the amiga AGA chipset (it will output the video signal through the 23-pin RGB connector next to the composite out port. If you have a scandoubler attached it should output these 'native' AGA screenmodes through the scandoubler port aswell at twice the frequency, so normal 15.5KHz screenmodes will come out as 31KHz.
There may be other monitor modes available aswell (eg starting with DBLPAL, PAL, NTSC or DBLNTSC): PAL, NTSC you may be familiar with; DBLPAL DBLNTSC are the ~31kHz screenmodes produced by the amiga chipset (as discussed above) - note these will NOT be doubled to 62kHz by the scandoubler - they will just be passed through. they will still exact a heavy toll on your chipset though.
Hope that helps, and is not too inaccurate.
-
When you boot the Amiga it will try to initialise the 3Dfx card in the Mediator. If it is not there, then it will not use it, and the Amiga's display will be used. That's what is happening now. When you connect the 3Dfx card to the Mediator it displays through that. From the sounds of it, you have selected a screemode that either your 3Dfx card or your TFT screen are unable to display. Follow Amigakit's instructions in the second post of this thread to reset your display settings back to their defaults. Then boot up with the 3Dfx card connected and select the resolution you were using before when it worked.
--
moto
-
Thanks for the info, Ive just loaded up workbench, then prefs, then screenmode but I dont have much there.
I have the following under display mode
1280x256
320x256
640x256
plus each one has a interlaced option.
Then mode propertied which is screen size and stuff and then colours is a scroll bar but at maximum its only on 256 then the option to test, save, use or cancel and thats it.
How come I dont have the voodoo ones like you suggest :(
-
Sounds like the Voodoo install is screwed - there should be loads of screenmodes. Have a look at the Mediator install guide on the CD. It will tell you how to install it properly. Once this is done all the screenmodes should be available in ScreenMode prefs.
--
moto
-
what cd are we talking about, the only one I got is the os cd and thats it, I dont have no install disks for mediator or 3dfx card :(
Are they downloadable from the net and if so would a pc made cd be readable on this amiga?
-
You can't download them unfortunately. You have to get them from Elbox. They come on a yellow cd with "MMCD" in red writing on it. The person you bought the Amiga from might have it.
--
moto
-
that was ages ago :( what does mmcd stand for?
Ive just looked in the prefs folder and I have one called "Picasso96Mode" and when I open it it has settings for "voodoo Village-31" where you can choose 1024x7638 etc etc and under modes you can have
256colours 31khz 74Hz
HiColour 71khz 85Hz
truecolour 30khz 36hz
truealpha 71khz 85 hz
So could this be the right place?
-
MMCD stands for MultiMedia CD and it comes with the Mediator.
You've got a Voodoo screenmode in P96Prefs which is good, so you may not need the CD after all. If you click the button to test the screenmode, can you see the testcard on the monitor connected to the Voodoo?
--
moto
-
Well maybe were getting somewhere then, but......
The test button on every selection is greyed out, only save, and when I hit save it says I need to reboot and then when I reboot I can only see the monitor under the normal monitor connection and if I connect the monitor to the 3dfx card I just get "no signal" so have to reconnect monitor to other port and viola I have the workbench, so for some reason still no signal from card :(
Sorry for all this hassle mate
-
Don't apologise, we're all here to help each other :-)
Sounds like the screenmode you have selected uses a frequency or a resolution which is out of your monitor's range. Try to find out the specs of your monitor. This will be in the manual if you have it, or maybe on a sticker on the back of the monitor. Then make sure the resolution and frequency of the screenmode in P96Mode are within the limitations of your monitor.
--
moto
-
Well im getting more and more frustrated with this thing, ive checked the two monitors (pc) I have in the house and they are both 50/60Hz so I guess its not supported :(
Theres loads of icons in the monitors folder in the devs folder, what are they for and how do you select them? Also how come the video card cant support the monitor im using yet the amiga port can??
-
actually somethings happened doh!!!
I found the installer for the picasso 96 in another folder just marked "stuff" anyway I uninstalled the drivers for it and now I get "no signal" in the standard port and "video out of range" on the 3dfx card so somethings happened, anyway now I cant get into workbench :( but I do get the boot options when I hold the two mouse buttons down!!!
-
Ive just tried what was mentioned above
rename sys:prefs/env-archive/screenmode.prefs sys:prefs/env-archive/screenmode.old
but get error that couldnt rename as object not found
:(
-
Actually ive got it all wrong now!!
the amiga port for the monitor now displays "video out of range" and the gfx card still says "no signal" ive tried the delete thing and rename thing but no joy :(
I never remember my miggy A1200 being this hard.
-
well ive renamed the screenmode.prefs, rebooted but video input still out of range, deleted screenmode.prefs rebooted but video input still out of range so it must be picking up the resolution from somewhere else as in the directory mentioned the screenmode.prefs is now gone so where??
I will be going to bed soon but will check back in abit and if no response will check tomorrow.
thanks again for all your help, im hopeing we can resolve this, thanks and goodnight
-
Hi Technium,
Will try and be around a bit today to help.
Don't uninstall or delete anything else just yet!
Firstly, you said you can get to the boot options screen.
Please do that, press the "Boot with no startup sequence" button to get to the command prompt.
Type "c/ed s/startup-sequence" and press enter.
This should list the script which is executed by the amiga as it boots up. You can edit it here - but for now don't delete anything, don't alter anything.
Ignore any lines which start with a ";" and copy the rest into your next post.
There is probably something in there which is causing an error, preventing your workbench from booting up properly. We can find out what that is, disable it, and get into your workbench to begin repairs. :-)
-
thanks mate, I feel like calling samaritans, its getting me so down lol
ok here goes
If Exists C:IDEFix
C:IDEFix
EndIf
C:SetPatch QUIET
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21
c:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/sys
C:Copy >NIL: ENVARCC: RAM:ENV ALL NOREQ
Resident >NIL C:Assign PURE
Redident >NIL C;Execute PURE
Assign >NIL ENV RAM:ENV
Assign >NIL: T: RAM:T
And thats all she wrote :), I had to type this by hand as cant copy and paste from my miggy to my pc.
thanks again
-
No responses today :( guess your all busy, well thanks anyway, im off to bed, will check back tomorrow just in case.
thanks again
-
No responses today :( guess your all busy, well thanks anyway, im off to bed, will check back tomorrow just in case.
thanks again
-
Hi Technium,
Looks ok to start, but that's just the start of the file. Using the cursor keys scroll down the screen - there's be a whole other load of lines after those.
Also, open s/user-startup and list the lines in that.
Finally, exit the 'ed' program (the text editor) to get back to the command prompt.
Type "sys:wbstartup"
Press enter
Type "dir"
Press enter
List the files which are shown. Ignore any which end in .info (these are just the icon files, not important at the moment)
I realise it's a pain in the arse and a lot of typing, but hopefully we'll find the root of the problem from this.
Regards
Rich
-
thanks Boot_WB for the reply.
Im at work at the moment but will try what you suggest when I get back home, never realised there was more text so will try later for you, sorry about that :)
Typing is not too bad, I'll be just glad when this is sorted as I used to love my amiga.
cheers
back later today.
-
ok heres the 2nd half of the startup sequence
ASSIGN >NIL: ENV: RAM:ENV
ASSIGN >NIL: T: RAM: T
ASSIGN >NIL: CLIPS: RAM: Clipboards
ASSIGN >NIL: REXX: S:
ASSIGN >NIL: PRINTERS: DEVS:Printers
ASSIGN >NIL: KEYMAPS: DEVS:Keymaps
ASSIGN >NIL: LOCALE: SYS:Locale
ASSIGN >NIL: LIBS: SYS:Classes ADD
ASSIGN >NIL: HELP: LOCALE:Help DEFER
BindDivers
C:Mount >NIL: DEVS: DOSDrivers/~(#?.info)
C:LoadMonDrvs
;IF exit DEVS:Monitors
; IF exit DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
; EndIF
; C:List >NIL: DEVS:Monitors/~(#?.infoIVGAOnly) TO T:M LFORMAT "DEVS:Monitor
; Execute T:M
; C:Delete >NIL: T:M
; EndIF
SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart
C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip
Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStar
SYS:System/REXXMast >NIL:
IF EXIST S:User-Startup
Execute S:User-Startup
EndIF
Resident Execute REMOVE
Resident Assign REMOVE
C:LoadWB
EndCli>NIL:
and thats all the statup sequence.
-
OK heres the USER STARTUP - Ive not done caps, if its important let me know but its easier to type without putting in capitals - here goes
;begin vinced
; remove the ; default console handler con:
; entfernen sie das ;die standard Konsole con: verwenden woollen.
;setvnc quiet mount override as con:
;remove the ; gadget with new functions from vinced that can be set with prefs tool vinced.
; entfernen sie das ; fahigkeiten von vinced in texteingabefeldern woolen. diese konfigurieren sie
; auch mit dem voreinsteller vinced.
;stringsnip >nil: install
; remove the ; assigns in pattern matching commands.
; entfernen sie das ; unterstutzung der mehrfach assign in dateinamensmustern wunschen.
;truemultiassigned
;end vinced
;begin mixer
path sys:prefs add
;end mixer
;begin genesis
assign amitcp: "workbench:internet/genesis"
;end genesis
;begin picasso96
;end picasso96
and thats all the user startup
ok any ideas from that lot? :)
-
And finally here is the list of the wbstatup directory
AMIDOCK
CLASSACTION
DEFICONS
FEEWHEEL
OXYPATCHER.PREF
RAWBINFO
WHEELDRIVER
And thats the lot.
thanks for looking.
-
Hi Technium,
Try changing the line in the startup sequence
DEVS:Monitors/VGAOnly
to
;DEVS:Monitors/VGAOnly
(don't worry about capitals at the moment)
and reboot.
Hopefully you should now be able to get back into workbench and have it displayed through your scandoubler.
I think the vgaonly monitor driver is preventing your scandoubler from doubling the scan rate, whilst not raising the scan rate enough to display on your monitor.
Hopefully this has worked - IF SO READ ON - IF NOT, THE REST IS IRRELEVENT FOR NOW.
Now - go into Devs/monitors create a new folder called temp - move all the monitor files in the devs/monitors drawer into the new temp drawer.
Once you have done this reinstall picasso96 from your OS3.9 CD (I think it is in the "contributions" drawer).
Pick the option which does it as a first installation.
Choose Cybervision643d as the graphics card.
When the installer has finished start the Picasso96 installer again.
Choose 'update an existing installation'
A few screens later a list of installation options appears. Deselect all the options except 'update monitor type' (or something similar - I think it is the third one from the bottom).
Go through the installation - choose the highest frequency supported by your monitor.
When THAT has finished go into devs/monitors.
Select the CVision3d monitor file (or whatever it is called).
Holding down the right mouse button select Icon/information from the menu at the top of the screen.
Click on the ICON tab - In the big box called tooltypes change the entry "card=cvision3d" to "card=voodoo" (it may be 'driver' or something rather than 'card' - I'm doing this from memory)
Click 'save' button.
Rename the 'cvision3d' monitor file to 'voodoo'.
Double-click the new 'voodoo' file icon.
Now - go into prefs & double-click P96mode
Holding down the right mouse button select the 'boards' menu. There should be an entry labelled 'Board0:voodoo' (or something similar) - select it and release the right mouse button.
If the only entry is 'BOARDS:NONE PRESENT' your voodoo card has not been detected, and we'll need to look at why that is - if this is the case the rest of this post is irrelevent.
Click on SAVE (or save settings or whatever).
P96 mode will tell you it needs to reboot - fine, let it reboot.
When workbench reloads go into prefs:screenmodes
You should now see voodoo screenmodes in the list (I use voodoo:1024x768:24-bit should do the job).
Click the 'TEST' button. It displays the monitor output through the VOODOO card for 10 seconds - so you have that long to change the monitor cable from your scandoubler socket to the voodoo socket to see if it is working :-).
Once you have a screenmode which you are sure works through the VOODOO click SAVE, exit, reboot (just to be sure the screen initialises ok on bootup).
NOTE: even with the voodoo working you won't be able to see the boot menu using your voodoo card - you'll still need to plug your monitor into the scandoubler.
When this is all done OK let us know - any problems, you know where we are :-)
-
were on about the startup sequence right, not user startup? well ive checked the startup sequence and its in there so made the change you said and put the ; infront but its made no difference :(
thanks again mate
have to goto bed now, up early for work but if you want me to do something next let me know and I will do it tomorrow when I return.
cheers
Colin
-
Hi Colin,
Goddamit! Amiga.org keeps logging me out - every time I think I've posted a reply I have to re-write the damn thing because it hasn't posted!
Anyway, for now I think the best thing you can do is connect the amiga to the TV to get the software side sorted out.
There are two ways to do this:
1 via the 'composite out' (yellow) port using a phono-phono lead to connect it to an AV port on your tv
2 using the RF modulator (reddish-brown) port (next to the power connector) using a phono-coaxial lead to connect to your TV aerial port and 'tuning in' to the amiga signal.
Obviously no 1 is easiest, but requires your TV has a 'composite in' port.
Once you have done this you should be able to boot into workbench, then follow the instructions in my previous post to reinstall Picasso96 and set up your voodoo screenmode.
Don't know why the scandoubler socket is coming up 'out of range' on your monitor - I have read that some monitors have trouble with low-resolution screenmodes, so this may be why.
By the way - what accelerator card do you have installed?
-
ok back again, back to square 1 again.
I plug an aerial from my old A1200 to go from back of computer in the rf modulator brown connection and tuned in the tower and stored channel, but I had a floppy in there so actually tuned it into a game...anyway took out floppy, rebooted and loaded workbench well I assume it was as the signal when all funny like it wasnt quite tuned in so I tried re tuning it but nothing just kept getting same signal so turned off and booted holding mouse buttons and screen comes up clear as day but as soon as you try to boot to wb the screen signal goes funny so why would that be, its obviously must be something to do with the wb resolution maybe, perhaps not, i dunno just clutching at straws now :(
anyway im here should you want me to try hitting it with hammer or something :)
-
Hi Technium, I'm going to be with my Amiga today for a couple of hours (we live 60 miles apart at the moment :-( ), so I'll do some experimenting then.
Will post later this afternoon.
-
ok thanks Boot_wb, in your own time mate, im not going anywhere its all set up so im just gratefull for you help.
cheers
Colin
-
Hello Technium,
Let me try and help you . . .
Your problem seems to be easy.
For sure, there's some monitor driver being activated in the startup, that's out of the range of your monitor/TV, and that's not being processed by your Scandoubler as well. There are some weird resolutions on the Amiga world :-)
Well, just boot with no startup-sequence.
Once in the AmigaDOS screen, typethe following lines, followed by an enter:
cd devs:monitors
makedir temp
copy #?.#? temp
delete #?.#?
dir
Just confirm if the "temp" folder is the only file showed by the dir command.
If there are more files, please copy them one by one to the same temp folder, and after that, delete them.
Now reboot your Amiga, preferably running on your TV.
The Workbench screen "should" appears.
If it's true, follow the instructions given by Boot_WB, for installing the Picasso system again.
By the way, let us now what's in that devs:monitors/temp folder :-)
Regards.
-
Wuhu that works, now into workbench, so onto what boot_wb said, back soon
-
ok back
Reinstalled picasso96 as suggested and that went fine, then did the update as suggested and that went fine, then when I right click on cybervision3d icon and goto info then icon tab I had the following
BOARDTYPE=Voodoo - Changed from whatever it was to voodoo like suggested
SETTINGSFILE=SYS:DEVS:Picasso96Settings
(BORDERBLANK=YES)
(BIGSPRITE=YES)
(SOFTSPRITE=YES)
IGNOREMASK=YES
(DISPLAYCHAIN=YES)
Then I renamed the icon from cybervision3d to VooDoo and then when I double clicked it nothing happens so I goto workbench menu and choose "show last message" and all I get is "attempting to load voodoo" but nothing actually happens when you double click on the icon.
so we are getting somewhere.......sort of.
thanks again for all your help guys
-
@mugo - the exact solution I'd just come to too :-)
@Colin - Re: nothing actually happens when you double click the icon
don't worry about, that is normal and fine - double-clicking just activates the driver - you then need to go into p96mode, do the changes there, then activate the screenmode. Just carry on following the instructions on my long post.
Glad you're finally getting somewhere mate.
-
ok here goes -
I went into prefs then picasso96mode and double clicked and got another screen with settings and resulutions and stuff as mentioned at the beginning of this thread somewhere, but when I right click I have the following
PROJECT which has OPEN, SAVE, SAVE AS, ABOUT & QUIT
SETTINGS which has BATCH CHANGE IDS
MODE which has PRINT MODE
ATTATCH SETTINGS TO which has NO BOARD
So I guess that means its not detecting the p96?
-
ATTATCH SETTINGS TO which has NO BOARD
So I guess that means its not detecting the p96?
Not exactly. It means that the P96 is not detecting your Voodoo card.
Just open a shell window (right Amiga key + E, the type newshell), and type:
pciinfo
Please copy the output here, so i can see if there's something wrong. I had problems in the past, and it was caused by a bad contact between the Voodoo board and the Mediator. Just pulling the Voodoo card out, and plugging it back on did the trick. But the other boards can have the same effect as well.
I would suggest you to leave only the Voodoo board attached by now.
Now as a side note, to your own sanity, contact Elbox.
Tell them you bought a second hand Amiga with a Mediator board, inform them the serial number (it's on a stick on the board), and ask how you can receive the update files for the drivers.
Tell them that you don't have the MMCD as well. That the old user didn't supply you one. And see what they tell you.
Without these files, you can be stuck in a case like this.
-
Boot_WB wrote:
@mugo - the exact solution I'd just come to too :-)
:-)
It's easy to come up with the more complex solutions, and neglect the simpler ones :-)
I don't know how it took so long, to someone give this simple suggestion . . .
Anyway, i hope we can help our friend Colin ! This kind of problem is a pain in the arse ! :boohoo:
-
ok cant do amiga keys as I have a tower with pc keyboard.
did what you said but loads of text flashed up, I guess thats for the different cards in the mediator pci thing.
I cant copy and paste as im typing this on my pc and trying to fix the amiga but if you want me to tyr and type it all up let me know unless you want me to look for something specific and I can tell you?
Also would it be simpler for you guys if I just reinstalled the OS or would that make not make any diffence?
thanks again guys
Colin
-
On a PC keyboard, the Windows keys map to the Amiga keys.
Reinstalling the OS would probably have been easier initially, but at this stage you might as well carry on as you're nearly there.
I had problems getting the board to show in P96Mode now. Can't quite remember how I fixed it now though. First step is to check the card is being detected.
In the shell type in pciinfo, and a list of all the detected cards will be returned. One of them should have Voodoo in the DeviceName. Does that show up?
--
moto
-
Hi Colin, I wouldn't reinstall the OS - without the Multimedia CD you won't be able to install the necessary files to get your mediator up and running.
To reset you should be able to use CTRL+ the two windows keys on your PC keyboard.
In the pciinfo you're looking for an entry for 3dfx.
Another thing to try: look in the libs/picasso96 folder. Is there a file called voodoo.card (or something similar)? If not, then I fear uninstalling picasso96 has deleted your P96 voodoo driver.
Unfortunately the voodoo.card driver is not downloadable form the elbox website - you do need the Multimedia CD form this point.
On the off chance, the previous owner MAY have left a backup on the hard drive somewhere, you could try FIND (in the WINDOW menu on workbench) and look for voodoo.card and/or MediatorUP and/or MMCD.
Hopefully you will find one of these on the hard drive somewhere.
-
I've got the MMCD. Where are you located Colin?
--
moto
-
Hi
I have two files in the libs folder called Picasso96APlibary and a folder called picasso96, in the folder is several folders which are
rtg.library
emulation.library
cvision3d.card
s3vage.chip
fastlayers.library
in the work harddisk partion is 2 folders which look like gooduns :)
they are
Medconfig13 which contains Medconfig and a folder called tvprefs which has loads of files like ATIWonder etc
the other folder of note is called Picasso96install which has the following -
setup install type icon
folders called, documentation, picasso96 and drivers
just found another folder called picasso96 which contains the following-
these are folders
acpro
debug
p96speed
shapeshifter
xipaint
and the following icons
p96_printerpatch.doc
picasso96_english.guide
p96_printerpatch
another folder in work I found was called p96speed which contained the following files
p96speed
p96speedguide
translators.readme
-
Im located in Portland in Dorset mate.
-
in the shell pciinfo pci device 4 is listed as device name voodoo5
is there anything you want me to tell you from this?
-
Sounds like uninstalling P96 has removed the voodoo drivers. You will need the MMCD to reinstall it. The CD also has all the instructions on correctly configuring the Mediator, Voodoo and P96.
The output from pciinfo means that the card is physically being seen on the PCI bus, which is a Good Thing :-)
PM me your address and I can send you the MMCD.
--
moto
-
HI, yes it appears the driver file (voodoo.card) has been deleted. P-mail me your address, I believe I have a spare MMCD from a broken mediator which I can mail to you. Regards
-
I said it first :-P
--
moto
-
thanks both of you, ive pm'ed you Boot_WB as you said yours is spare so just makes it easier but truely many thanks Motorollin for the offer, I dont wnat you thinking im ignoring you or anything.
Really I never knew generosity like this existed on forums, sure people give up their time to help but posting stuff aswell!!
thanks again, WE will eventually have this tower running.
-
I understand, you love Boot_WB more than me :boohoo:
:lol:
At least you can use the Amiga on your telly until you get the Mediator working. What software has it got installed on it?
--
moto
-
Noooooo, dont say that lol, you make me feel guilty now :)
I dont think theres much on it, so that will be my next step as my old a1200 used to have great stuff like dopus, quarterback, snoopdos etc but I have got loads of software up in the attic that came with it, 100's of disc sold as blanks so I guess they are dodgy copies and about 100 boxed games and utilities etc but ive been out the scene so long I just wanted to get back in......oh the good old days of playing scorched tanks, or canon fodder, galaga duluxe and sensible soccer etc etc they dont make games like that anymore!!
Anything your after I could check to see if I have it.
-
Just wait til you start loading up those old games again. You're gonna have soooo much fun :-)
--
moto
-
I remember rise of the robots, damn thing had 13 disks, you ended up with wrist ache from keep changing disks! lol
-
Oh, *that's* why your wrists ached :roflmao:
I think you can get Rise Of The Robots on CD now to save all that swapping. Or if you've got the disks, you could install it to your hard drive. I wonder what Amiga game had the most amount of disks!
--
moto
-
Hello guys,
Good to see that the problem with technium's Amiga has been detected.
I'm positive that your problem now is a matter of the Mediator drivers being reinstalled.
Just to warn you again, and i'm sorry for insist in this matter, i think you should write Elbox a message, asking them to change the registration of your Mediator from the previous owner, to yourself. This way you can receive the updates for the drivers and other Mediator files.
These updates are very important to keep your system running healthy.
I don't know what version is the MMCD that Boot_Wb will send you, but i'm quite sure it doesn't contains the latest drivers. Your system will work with the drivers on the CD, but i would update them.
Good luck !
-
:(
Back sorry for delay, had family troubles, anyway im back......
Ive got the MMCD from boot_wb but I still cant seem to get anywhere, I really just dont know what im doing and getting quickly confused :(
I still get "no signal" when flat panel monitor is plugged into the voodoo card but I get a display when plugged into amiga serial but the display size is wrong :(
any ideas?
-
ok after following the read me on the mmcd ive managed to get it to find the voodoo card in the board settings in the picasso96 mode in Sys:prefs but still having problems with screen size. Also if I use the picasso card connection I seem to now get a test card on display but hey at least its now showing something.
so whats next?
-
Hi Technium,
Sorry to hear about the family troubles. Glad you got the disk ok.
Since you can get the testcard to display when your monitor is attached to the voodoo card this means you are one step form the end of your long journey. :-)
When you have gone into prefs/screenmode and selected one of the voodoo screenmodes, you hit 'test' to make it output to the testcard to the monitor.
There should be many screen sizes listed, eg 1024x768, 800x600, all starting with "VOODOO:". Once you are happy that the testcard is the right size for your monitor you have two options:
1 Hit 'use' - this will use the selected screenmode until you reboot. I'd suggest doing this first just to make doubly sure everything is ok. Your workbench should then be displayed on the monitor attached to your voodoo card.
2 hit 'save' - the workbench will then use this setting every time you reboot (unless something goes wrong during bootup, in which case you can always use the composite port again to find out what has gone wrong).